For software platforms
What your customers get from your payments. And who they call when something goes wrong.
When you put payments inside your product, every payment problem becomes your problem in your customer's mind, whoever actually caused it. That is the real objection to embedding, and it is a fair one. This page sets out what your customers get, and what happens when something goes wrong.
Your support queue is the honest test.
Every embedded payments pitch talks about revenue share. Almost none of them talk about what lands in your inbox afterwards, which is the thing that actually decides whether the arrangement was worth it.
A customer whose collection failed does not ring the payments company. They ring the software they logged into that morning, because that is the brand they have a relationship with. If the answer is "that is our payments partner, here is a different number", you have taken on the reputational cost of payments without the means to fix anything. So the question to ask any provider is not what the rate is. It is who picks up, how fast, and whether they can see the transaction.
Their experience
Payments inside the product they already use
The payment happens where the work happens: the invoice they raised, the booking they took, the plan they set up. No second login, no separate portal to reconcile against, no tab where your product ends and somebody else's begins.
Which matters commercially as well as cosmetically. A customer who has to visit another provider's dashboard to understand their own money has been given a reason to shop around, by you.
- Payment taken inside your product, against the record it belongs to
- No second login and no separate reconciliation
- Your branding on the flow where it fits
- Card, wallets and Direct Debit on one account, with pay by bank coming soon
- One statement covering every channel they use
When it breaks
Payment support from us, with their setup in view
Each of your customers has an account manager here who can open the actual transaction and explain what happened. Not a queue, not a ticket number, and not a script that ends in "contact your platform".
That is the part you are really buying. The revenue line is arithmetic; whether your support burden goes up or down is the thing that decides how you feel about this in eighteen months.
- An account manager your customers can phone, not a ticket queue
- Boarding, verification and identity checks done by us
- Disputes, chargebacks and indemnity claims handled here
- Failed collections flagged with the reason, not just a status
- Your support queue stays about software
Their money
Their money sits with a regulated institution, not with you.
Between a payment and its payout, each customer's takings sit in a balance in their own name with our regulated acquiring partner. Payout goes to the bank account they nominate the next working day.
You set your price and never hold anyone's money, which is the answer your legal team will ask for first and the reason your regulatory position does not change.
- A balance in each customer's name, with a regulated institution
- Payout to the account they nominate
- Settled in full, with payment fees billed once a month
- Checks before they go live, against their real trade
- We will walk your legal team through where every line sits
The honest part
What your customers gain, and what they give up.
A customer moving onto your embedded payments does gain: one place for the money, one statement, a person to ring, and pricing agreed across all your customers rather than negotiated alone.
What they give up is the freedom to shop the rate every year without touching your product, and the familiarity of whatever they use today. For a customer who has just signed a good deal elsewhere, the honest answer is to wait for their renewal. Telling them that is what makes the recommendation worth anything the rest of the time.
- Pricing agreed across all your customers, in writing
- One provider instead of two or three
- A person who answers, by name
- But: switching costs them effort, and a good existing deal is worth keeping
- So we will say when the answer is not yet
What platforms ask on their customers' behalf
Usually. Where the answer is no, we would rather say so before they have taken money than after. Sole traders and young companies are often the hardest for payment providers to onboard, and doing that properly is a big part of what we do.
That it is one account instead of several, one statement they can actually audit, an account manager rather than a queue, and pricing agreed across all your customers. And that if they have just signed a good deal elsewhere, waiting for renewal is the sensible answer. A pitch that admits that is the one your customers believe.
Yes. The flow lives inside your product and carries your branding. What we will not hide is who holds the money: our regulated acquiring partner, which your customers are told plainly at onboarding.
Their balance and payout history are theirs. If they leave your product they are offboarded cleanly and paid out in full. That is deliberate: a customer who can leave without their money being held was never locked in.
A thirty-minute payments review
Bring the objection your customers would actually raise. We will answer it, including where the honest answer is that embedding is not right for your customers yet.