A business selling at a few hundred euros and a business selling at fifteen thousand look identical on a website and completely different to a payment provider. The second one has fewer transactions, larger amounts and a dispute that can wipe out a month — and every part of the offer it receives follows from that.
High-ticket payments are not harder to arrange. They are arranged differently, and the businesses that struggle are usually the ones trying to run a fifteen-thousand-euro sale through a checkout designed for fifty.
Contents
- Why size changes everything
- Cards are not always the right instrument
- What it costs at this size
- Getting the large payment approved
- Evidence for a sale that ships later
- What the application should say
- Three numbers to agree before the first sale
- In short
Why size changes everything
- One dispute is material. At a small ticket, disputes are a percentage. At a large one, a single case is a bad month, and the provider sees the same arithmetic you do.
- The reserve is felt. Ten per cent of a small ticket is noise; ten per cent of large payments held for a period is working capital.
- Issuers hesitate. Large card payments hit customer limits and trigger the issuing bank’s own caution far more often — the decline is frequently on the customer’s side, not yours.
- Delivery is slower than the payment. Property, equipment, long consulting engagements: money moves in a minute, delivery takes weeks, and the gap is where disputes live.
Which band you land in overall, and why, is set out in our piece on what high-risk, middle-risk and low-risk payments are.
Cards are not always the right instrument
This is the part most high-ticket merchants work out too late. Per-transaction ceilings exist at every provider and are agreed per merchant rather than published as one number — so the practical question is not «will the card go through» but «which instrument fits this amount».
In practice a mixed model wins: card for the deposit or the first instalment, bank transfer for the balance. The customer is already used to it for large purchases, the economics are better, and the dispute exposure drops sharply because a transfer is not chargebackable the way a card payment is. The account side that receives transfers is described under business IBAN.
What it costs at this size
Card acceptance: MDR 3%–5% depending on the type of business plus 0,50 EUR per transaction — at a large ticket the fixed fee disappears and the percentage is everything. Settlement in EUR over SEPA 0,20%, term T+7, rolling reserve 10% for 180 days, refund 50,00 EUR, chargeback 100,00 EUR on top of the returned amount.
Transfers into the company account: SEPA in and out 10 EUR + 0,30%, incoming SWIFT in euro 50 EUR + 0,35%. On a large invoice that is a fraction of what the same amount costs on a card, which is the whole argument for the mixed model. The exact rate is set per merchant and we consider individual solutions for your business.
All published lines sit on the pricing page.
Getting the large payment approved
Warn the customer before they pay. A single sentence — «your bank may need to confirm this amount» — turns a decline into a phone call that succeeds. Most large-ticket declines are the issuer’s caution rather than a refusal.
Split when the customer wants to split. Two payments that succeed beat one that does not, but do not fragment a single sale into many small charges to dodge a limit: that pattern is exactly what monitoring is built to catch.
Take the payment when the customer is warm. A deposit at the moment of decision converts; an invoice sent three days later competes with second thoughts.
Read your declines properly. Soft and hard behave differently and only one of them is worth retrying — the groups are unpacked in our piece on why traditional payment gateways do not work for high-risk businesses.
Evidence for a sale that ships later
When delivery follows the payment by weeks, the dispute defence has to be assembled along the way rather than at the end: the signed agreement, the scope, the milestone acceptances, the correspondence, and a statement descriptor the customer recognises months later. That last one causes more disputes on high-ticket sales than anything else, because a large unfamiliar line on a statement gets reported rather than questioned.
How routing, retries and settlement are put together is described under payment processing.
What the application should say
Say the average ticket plainly, say the maximum you expect, and say what the customer receives and when. A provider that knows a sale is fifteen thousand with six weeks of delivery can price it. A provider that discovers that from the first transaction will pause the account and ask. The rest of the file is standard, and the list is in our merchant approval checklist.
Three numbers to agree before the first sale
All three are ordinary questions, and all three are cheaper to ask now than to discover during a held payment.
- The ceiling for a single transaction. It exists everywhere and is agreed per merchant; know yours before you quote a price above it.
- What happens to the reserve as the ticket grows. The percentage may stay while the amount held changes your cash position entirely.
- How a partial refund is handled. On staged delivery this comes up far more often than a full one, and it is worth knowing the mechanics before a customer asks.
In short
A high average ticket is not a barrier, it is a design constraint. Expect the reserve to matter more than the rate, use cards for the deposit and transfers for the balance, warn customers before large charges, and build dispute evidence as the delivery progresses. Set up the merchant account and the company account together — at this size the two only work as a pair.