Category: Project Principal Contractors

The Missing Piece in Your Client Payment Infrastructure

It is a conversation that plays out in bank branches and compliance departments around the world. A project contractor — let us call him David — approaches his bank about accepting card payments from clients. He wants to offer his clients the convenience of paying their project deposits by credit or debit card. The bank asks about his business model, his project volumes, his average transaction size, and his chargeback history. David explains that he is a project contractor who takes deposits of $5,000-25,000 from clients at the start of each engagement, with typical project values of $50,000-250,000.

The bank's response, after due consideration, is a polite but firm no. The risk profile does not fit their merchant acquiring criteria. They wish him the best of luck.

David is not alone. Project-based businesses — contractors, consultants, trade operators, and service principals — face a persistent and often unexplained difficulty in obtaining card acceptance capabilities from traditional banks and payment processors. The problem is not that their businesses are illegitimate or high-risk in the traditional sense. The problem is that their business model does not fit the risk parameters that card processors use to evaluate merchant applications.

Why Banks Are Reluctant to Provide Merchant Accounts to Project-Based Operators

To understand why banks say no, it is necessary to understand how merchant acquiring works and how the risk model differs from other forms of banking.

When a bank or card processor provides a merchant account, they are essentially extending credit. When a client pays by card, the merchant receives the funds before the cardholder's bank has finalised the transaction. If the cardholder disputes the charge — claiming the service was not delivered, was defective, or was unauthorised — the card processor must refund the cardholder. If the merchant cannot repay the disputed amount — because they have already spent the money, because their business has failed, or because they have disappeared — the card processor bears the loss.

This risk is particularly acute for project-based businesses for several reasons.

Extended delivery periods. Card chargeback rules typically allow cardholders to dispute a charge within 120 days of the expected delivery date. For a project that takes six months to complete, the chargeback window extends well beyond the initial payment date. If a client pays a deposit by card and then disputes the charge three months later — claiming the project has not been delivered — the card processor may be liable for the refund, even if the project is on track and the contractor has already spent the deposit on materials and subcontractors.

High average transaction values. Project deposits tend to be significantly larger than typical card transactions. A retail merchant might process hundreds of transactions per day with an average value of $50-100. A project contractor might process a handful of transactions per month with an average value of $10,000-25,000. The potential loss from a single chargeback is correspondingly larger, and the card processor's risk exposure is concentrated rather than diversified.

Irregular transaction patterns. Card processors monitor transaction patterns for signs of fraud or financial distress. A merchant who processes no transactions for weeks and then suddenly processes a $25,000 payment looks anomalous — even if the pattern is entirely consistent with a project-based business. Anomalous patterns trigger fraud alerts, account reviews, and sometimes account closures.

Industry classification challenges. Merchant accounts are classified by industry code, and some codes carry higher risk weightings than others. Project contractors often fall into ambiguous or high-risk categories — construction, professional services, consulting — that trigger enhanced scrutiny. The bank's underwriting team may not have the expertise to evaluate the specific risk profile of a project-based business and may default to a conservative decision.

Cross-border complexity. When the contractor's clients are in different countries from the contractor's bank account, the card processing risk increases. Cross-border card transactions carry higher fraud rates, higher chargeback rates, and higher processing costs. They also create currency conversion issues — the deposit may be in one currency while the merchant account settles in another — that add complexity to the risk assessment.

The Card Acceptance Gap for Client Deposits

The practical consequence of banks' reluctance to provide merchant accounts to project-based businesses is a significant gap in the payment infrastructure available to these operators. Most businesses can accept bank transfers — but bank transfers require the client to initiate the payment manually, which creates friction and delay. Many clients, particularly corporate clients, prefer to pay by card for the convenience, the cash flow advantages, and the consumer protection that card payments provide.

The card acceptance gap is particularly painful at the deposit stage. A deposit is the signal that the project is going ahead — the client's commitment to the engagement. When the client wants to pay the deposit by card and the contractor cannot accept cards, the friction can delay the start of the project or, in some cases, cause the client to choose a competitor who can.

For the contractor, the inability to accept card deposits also means a longer cash conversion cycle. A card payment is typically settled within one to three business days. A bank transfer, particularly an international one, may take three to five business days — and longer if compliance reviews are triggered. The difference may seem small in isolation, but over the course of a year with multiple projects, it adds up to a meaningful impact on working capital.

International Card Processing Fees

Even when a project-based business manages to obtain a merchant account, the cost of international card processing can be prohibitive. Standard card processing fees for domestic transactions typically range from 1.5 per cent to 2.5 per cent of the transaction value. For international transactions — where the cardholder's bank is in a different country from the merchant's — the fees increase significantly, often to 3-5 per cent or more.

For a project deposit of $15,000, an international card processing fee of 4 per cent represents $600 — a meaningful cost that either reduces the contractor's margin or must be passed on to the client. Many contractors choose to pass the cost on as a "card surcharge," but this is increasingly restricted by card network rules and local regulations. In some jurisdictions, surcharging is prohibited entirely.

The cost structure of international card processing also includes additional components beyond the basic processing fee. Cross-border fees, levied by the card networks, typically add 0.8-1.2 per cent. Currency conversion fees, if the deposit is in a different currency from the merchant's settlement account, add another 1-3 per cent. The combined effect can push the total cost of accepting an international card payment to 5-8 per cent of the transaction value.

For a business with thin project margins — 10-15 per cent is common in many contracting sectors — the card processing cost can consume a significant portion of the profit. This creates a difficult trade-off: offer clients the convenience of card payments and accept the cost, or insist on bank transfers and accept the friction.

The Infrastructure Requirements

Beyond the cost, the infrastructure requirements for card acceptance present additional challenges for small cross-border businesses. A traditional merchant account setup requires several components: a merchant account with an acquiring bank; a payment gateway to process online transactions; a card terminal or virtual terminal for telephone and in-person transactions; PCI-DSS compliance — the Payment Card Industry Data Security Standard — which requires specific security measures for handling card data; and integration with the business's accounting and reconciliation systems.

Each of these components has its own setup costs, monthly fees, and compliance requirements. For a small business processing a modest number of card transactions, the fixed costs of maintaining this infrastructure can exceed the transaction costs.

PCI-DSS compliance, in particular, is a significant burden for small businesses. The standard requires specific technical and organisational measures to protect cardholder data, including network security, access controls, encryption, and regular vulnerability assessments. Non-compliance can result in fines, increased processing fees, or loss of card acceptance privileges. For a business without dedicated IT and compliance staff, maintaining PCI-DSS compliance can be a persistent challenge.

Alternative Deposit Collection Methods

Given the difficulties of traditional card acceptance, project-based businesses have developed alternative methods for collecting deposits. Each has its own advantages and limitations.

Bank transfers remain the most common method for project deposits. They are secure, well-understood, and do not require merchant account infrastructure. However, they create friction for the client and can be slow, particularly for international transfers. They also do not provide the same level of payment confirmation as card transactions — a transfer may be initiated but not settled for several days.

Payment links — generated by platforms that specialise in business-to-business payments — offer a middle ground between bank transfers and card acceptance. The contractor generates a link and sends it to the client, who can pay by card or bank transfer through the platform's interface. The contractor does not need a traditional merchant account; the platform handles the card processing. However, the fees can be high, and the contractor may have limited control over the client experience.

Digital wallets and payment apps are increasingly popular for consumer payments but have limited adoption in the business-to-business context, particularly for high-value transactions. The transaction limits imposed by most wallet providers may be insufficient for project deposits.

Escrow services provide a structured approach to deposit collection that protects both the contractor and the client. Funds are held in escrow and released according to pre-agreed milestones. While this provides security, it adds complexity and cost, and may not be appropriate for smaller projects.

Embedded Card Acceptance as Part of an Integrated Workspace

An emerging solution to the card acceptance gap is embedded card acceptance — card processing capabilities that are built into a broader financial platform rather than provided as a standalone service. This model, which is a feature of some managed business workspace offerings, allows project-based operators to accept card payments without establishing a separate merchant account or maintaining PCI-DSS compliance independently.

In the embedded model, the workspace provider holds the merchant account and handles the card processing infrastructure. The operator generates payment links or invoices that include card payment options, and the client pays through the workspace's card processing system. The funds are settled directly into the operator's account within the workspace, with the card processing fees deducted transparently.

The advantages of this approach are significant. The operator does not need to apply for a merchant account, undergo underwriting, or maintain PCI-DSS compliance. The card processing infrastructure is provided as part of the workspace, reducing setup time and ongoing management. And the integration with the workspace's banking, FX, and reporting capabilities means that card payments are automatically reconciled and reflected in the operator's financial records.

The embedded approach is not without limitations. The operator is dependent on the workspace provider's card processing arrangements, which may not offer the most competitive rates for all transaction types. The operator may have limited ability to customise the payment experience. And the availability of embedded card acceptance may be restricted to certain jurisdictions or card networks.

The Strategic Value of Accepting Card Deposits

Despite the challenges, the strategic value of card acceptance for project-based businesses should not be underestimated. Clients increasingly expect to be able to pay by card — it is faster, more convenient, and provides a level of protection that bank transfers do not. A contractor who can say "yes, we accept cards" when a client asks about deposit payment has a competitive advantage over one who cannot.

Card acceptance also accelerates the sales cycle. When a client can pay a deposit immediately — at the end of a meeting, by following a payment link, or through an online portal — the project starts sooner and the contractor gets paid faster. This is not a trivial benefit: in project-based businesses, the time between winning a contract and receiving the first payment can be weeks, during which the contractor is incurring costs without revenue.

Finally, card acceptance signals professionalism and legitimacy. It suggests that the contractor has the infrastructure and the standing to operate a merchant account — or at least to partner with a platform that does. In a market where clients are choosing between contractors they do not know well, this signal can be decisive.

The card acceptance gap for project-based businesses is real, and it is not going to be closed by traditional merchant acquiring. The risk model does not fit, and banks are not going to change their underwriting criteria to accommodate project-based operators. But the gap is being closed by alternative approaches — payment links, embedded card acceptance, and integrated workspace solutions — that provide the capability without the traditional overhead. For project-based businesses that have been turned down for merchant accounts, these alternatives offer a path to accepting card deposits and the competitive advantages that come with them. The question is not whether to accept cards, but how to find the right infrastructure to make it possible.