Going direct to an acquirer, or a payments partner: which fits a UK platform?

It arrives the moment a platform learns that its payments partner runs on an acquirer's infrastructure, as Synapto does through our regulated acquiring partner. The next question from a CTO or a finance director is reasonable: if the rails are the acquirer's, why not contract with the acquirer directly and keep the margin a partner would earn?

The answer is not that you cannot. Some platforms should. The answer is that the rails are one part of launching payments inside a software product, and the acquirer's part stops where most of the work begins. This guide sets out what each route gives you, what each asks of your team, and how to tell which one you are. Checked November 2026.

An acquirer that serves platforms gives you the payment infrastructure: the acquiring licence, the connection to the card schemes and bank rails, an onboarding and verification service for your customers, settlement, payouts, and the documentation and test environment your developers need. You get an account manager for your contract. Synapto runs on one such acquirer, our regulated acquiring partner, so the technical capability on each route is the same.

What going direct asks for is set by the acquirer's commercial model. Acquirers that serve platforms usually look for a large existing payment volume before they will contract directly, and often a processing commitment up front: a volume you agree to deliver, with the pricing set against it. A platform with that volume and a team ready to use the rails is a good direct customer. A platform earlier in its payments journey often does not get past the first conversation, or gets terms that assume a volume it does not yet have.

Then the work on top is yours. Someone has to decide what the payment product inside your software looks like, which payment methods it offers and how it handles refunds and disputes. Someone has to set the price your customers pay, and explain it. Someone has to plan the launch to your existing customers, write the explanation, send the invitations and follow up. And someone has to answer the payment questions that come back, every day, from the customers who moved. On the direct route, that someone is your team.

A payments partner sits between the acquirer and your product and does the work the acquirer does not. In Synapto's case that is four things, on our regulated acquiring partner's infrastructure, at competitive rates.

1. The payment products, built with you. Onboarding, payment methods, pricing, payouts and reporting, set up for your platform and your customers. Your developer builds the integration into your software, with our documentation, a test environment and a payments engineer answering questions. We write down who does what before anyone builds anything.
2. The offer and the launch. We work out with you what your customers will buy, why they would choose it and how to price it, then plan how to bring new and existing customers onto your payments: the explanation in your brand, the invitations and the follow-up.
3. A named person on both sides. An account manager for your team, and the same team for your customers' payment questions, refunds and disputes. Your support team is not learning payments on the job.
4. Terms sized to the volume you have today. We put the commercials in writing before you commit: your buy rate, the price you set above it, and the margin paid to you monthly. Each of your customers is settled in full, in GBP, to its own account. Our regulated acquiring partner holds the licences and the funds throughout; Synapto never holds anyone's money.

None of this is free, and it is honest to say so. A partner earns a margin on the payments it helps you launch. The comparison a finance director should make is between that margin and the cost of the payments team, the delay and the missed adoption that come with doing the same work in-house.

What each route gives a UK platform, under the headings a buying committee uses. Checked November 2026; the direct column describes acquirers that serve platforms generically.

Three situations, and in each we will say so on the first call.

• Very large payment volume. If the volume already running through or beside your product is large enough that an acquirer will contract with you on its own terms, and you are comfortable with the processing commitment that comes with it, the margin a partner earns is a real number against your own cost of doing the work.
• An in-house payments team. If you already employ people whose job is to design, price, launch and support payments, you have what a partner provides. Direct lets you use the rails without paying twice.
• Customers outside the UK, or multi-currency settlement. Synapto settles in GBP on UK rails, and that focus is the point of us. A platform whose customers need settlement in several currencies should go to a global acquirer directly, or to a partner built for that.

1. Size your payment volume honestly. Ask an acquirer what it would contract for. If the answer is a volume you do not have, or a commitment you would not sign, the direct route is not open to you yet.
2. Count the team. List who, by name, would design the product, set the price, run the launch and answer the support queue. If the list is your CTO and your support lead, that is the cost of going direct.
3. Price the delay. Every month before launch is a month your customers' payments earn for someone else. Set that against the margin a partner would earn.
4. Check the settlement you need. GBP on UK rails, or several currencies. This one decides it on its own.

For most UK platforms with real payment volume and no payments team, the honest comparison is not partner against acquirer. It is partner against building a payments team, on the same rails either way.