Per-transaction cap
The largest single payment your account will accept. The most common cause of a surprise decline on a large order.
Large invoices
High-Ticket Payment Processing for Large B2B Invoices
A declined six-figure payment is almost never a problem with the customer's card. It is a limit somebody set on your account years ago and nobody revisited.
The short answer
High-ticket payment processing is the acceptance of unusually large individual transactions, which in a B2B context typically means invoices from five figures upward. The constraints are not technical but risk-based: merchant accounts carry per-transaction caps, daily and monthly velocity limits, and sometimes reserves, all set during underwriting based on your financials, average ticket and processing history.
When a large payment declines, the most common cause is a per-transaction cap set when the account opened and never raised as the business grew. Raising it is an underwriting conversation requiring financials and trading history, which means it needs to happen before the order rather than while a customer waits.
The limits that actually stop payments
Daily and monthly velocity
Total volume ceilings over a period. A busy month can trip these even when no single transaction is unusual.
Average ticket variance
Processing a transaction far above your stated average ticket can trigger a hold or review even when it is within the cap.
Reserves
A held percentage of settlement, released on a schedule. More common on rapid growth, high ticket sizes or customer concentration.
None of these are visible to your customer. They see a decline and draw their own conclusions, which is the real cost.
What underwriting wants before raising your limits
- Two years of financial statements, or as much history as you have.
- Evidence of completed orders at the size you want to accept - invoices, contracts or purchase orders.
- An explanation of customer concentration if a small number of customers make up most of your volume.
- Your refund and dispute history, which matters more at large ticket sizes than at small ones.
Do this before you need it. Raising a cap mid-order, with a customer waiting, is the worst position to negotiate from.
When a card is simply the wrong rail
On an invoice large enough, the question is not whether the card will go through but whether it should.
Percentage-based interchange on a six-figure payment is a very large number. A flat ACH or wire fee on the same invoice is not. Where the customer is willing, moving the largest invoices off cards entirely produces far more saving than any rate optimization could.
- 01
Set a threshold
Above a chosen invoice value, ACH or wire becomes the default and a card is by exception.
- 02
Make the exception easy
Some AP departments genuinely cannot pay any other way. Keep the card path open rather than losing the order.
- 03
Optimize what remains
Large card payments that do go through should carry full Level 3 data, where the basis-point saving is largest in absolute terms.
Where you are today
Four ways operators start with us on Limits set at account opening are the most common reason large B2B payments fail.
New or pre-revenue business
Not processing yet. We map which payment methods your card mix and products can realistically support, what each costs, and what your application file needs before you open.
Plan your payment setupOperating and looking to switch
Already processing but paying too much, funding too slowly, or working around a system that does not fit. Send statements and we return a line-by-line read plus alternatives.
Review my current setupRecently shut down or restricted
Account terminated, frozen, capped or moved to reserve. We help you interpret the notice, pursue held funds, and rebuild with fewer single points of failure.
Get help with a complex accountDeclined during underwriting
Turned down on application. We read the decline reason, identify what was missing or mismatched in the file — licence, ownership, product mix, banking — and rebuild the submission before it goes back out.
Review a declined applicationFrequently asked questions
Why did our large payment decline when the customer has credit available?+
Most often a per-transaction cap or velocity limit on your merchant account rather than anything on the customer's side. Your processor can confirm which, and the decline reason is frequently not passed through to whoever ran the payment.
Can limits be raised?+
Usually, with financials and evidence of trading at that size. It takes days rather than minutes, so it needs doing in advance of the order.
Why would a processor hold a large deposit?+
Risk review triggered by a transaction far above your stated average ticket. Telling your provider in advance about an unusually large order prevents most holds.
Should we split a large invoice across several payments?+
It is sometimes legitimate - genuine milestone or progress billing against separately delivered work. Splitting a single transaction purely to evade a cap is not, and processors identify it quickly.
Related pages and resources
ChecklistMerchant statement audit checklistRun the analysis yourself before you ask anyone for a quote.Read more Comparison tableCommercial card vs ACH decision guideWhich rail is cheaper at which invoice size, and where the answer flips.Read more CalculatorInterchange savings calculatorEnter your monthly card volume, average ticket and current effective rate to see the annual gap.Read more
More on high-ticket processing
Accepting very large invoices: caps, velocity limits, reserves and the underwriting behind them. These pages sit under this guide and link back to it.
Case studyMetal Service Center High-Ticket Acceptance: A Sample ScenarioA metal service center found the answer was not a better card rate but routing its largest invoices to a different rail entirely.Open QuestionWhy won't our card payment go through for a big orderMost often because of a per-transaction cap or velocity limit on your own merchant account rather than anything on the customer's card. These limits are set during underwriting based on your financials, average ticket and processing history, and they do not grow with your business unless somebody asks. The decline reason is frequently not passed through to whoever ran the payment, which is why it looks like a customer problem.Open
Read next
- 1Large invoice declinedMost often because of a per-transaction cap or velocity limit on your own merchant account rather than anything on the customer's card. These limits are set during underwriting based on your financials, average ticket and processing history, and they do not grow with your business unless somebody asks. The decline reason is frequently not passed through to whoever ran the payment, which is why it looks like a customer problem.
- 2Metal Service Center High-Ticket Acceptance: A Sample ScenarioA metal service center found the answer was not a better card rate but routing its largest invoices to a different rail entirely.
Find out what your statements actually say
Send three months of merchant statements and one representative invoice. You get back a line-item breakdown of what is downgrading, what it costs annually, and what could realistically be recovered. No obligation, and the analysis is yours either way.
Interchange qualification depends on your card mix, the data your systems can transmit, your settlement timing, and card-brand rules that change twice a year. Nothing on this page is a quoted rate, a guarantee of savings, or a promise of approval. Figures shown are illustrative ranges drawn from published card-network and industry sources, not an offer. What you would actually save is whatever a review of your own statements shows, which is why we start there.