Stablecoin payments get pitched with a lot of upside — lower fees, faster settlement, access to customers who’d rather pay in USDC than fight a card decline. Most of that upside is real. But the diligence process for a stablecoin payment vendor should look like the diligence process for any other financial infrastructure vendor: specific questions, not a features list.
Here are the five questions worth asking before signing, framed the way a finance team should actually evaluate them.
1. Who actually holds the funds?
This is the question that matters most and gets answered least clearly. Some providers marketed as “payment gateways” are, functionally, custodial financial businesses — they take possession of stablecoins on your behalf and settle to you on their schedule. That’s not wrong on its own, but it’s a materially different risk category than a provider that never takes custody at all.
Ask directly: at any point between a customer’s wallet and your settlement, does the provider hold the funds? If the answer is yes, you’re underwriting counterparty risk on top of payment risk — account freezes, insolvency exposure, and dependency on a third party’s internal controls. If the answer is genuinely no — funds route from the payer to infrastructure you control, like a merchant-specific vault — that risk category doesn’t exist in the first place. It’s worth getting this in writing, not just in a sales deck.
2. What happens on a dispute or an error?
Cards have chargebacks. Stablecoin transfers are, by design, irreversible on-chain. That’s not automatically bad — it removes an entire category of chargeback fraud — but it does mean the provider’s handling of disputes and errors needs to be concrete, not hand-waved.
Ask what the actual process looks like for: a customer who sent the wrong amount, a payment that needs a manual refund, and a wrong-network transfer. “We’ll look into it” is not a process. A provider whose architecture prevents the common failure modes structurally (routing that can’t send funds to the wrong place, balance checks before a payment is even attempted) has fewer disputes to handle in the first place — which is a better answer than a fast dispute-resolution team patching over frequent mistakes.
3. Can we get clean settlement data out?
A surprising number of evaluations stall here — not on the payment itself, but on what happens after it. Every settlement should leave a record you can export: amount, asset, network, transaction hash, timestamp, and the order or invoice it belongs to. It should be available in real time through an API and a dashboard, not reconstructed from a block explorer weeks later.
The honest position — and the one worth demanding from any vendor — is data clean enough for your own team and advisors to work with, and no vendor-supplied interpretation dressed up as guidance. Ask to see a real export before you sign. If it takes a support ticket to get one, that is your answer.
4. What’s the all-in fee, really?
Headline rates in this space range from effectively 0% (non-custodial, self-hosted options) to 1–2% plus a flat fee (card-adjacent processors). The number that matters is the blended, all-in cost including FX spread, withdrawal fees, and any conversion spread hidden between the customer’s payment and your settlement currency.
Ask for the fee structure in writing, specifically: is anything charged besides the headline merchant fee, and at what point in the flow. A provider charging fees only at settlement, with nothing hidden in the conversion step, is a meaningfully different commercial arrangement than one with a low headline rate and a wide spread buried in the FX conversion.
5. What isn’t solved yet?
Every vendor in this category is honest about roughly nothing they consider a limitation, and confident about everything they consider a strength. The useful diligence question flips that: ask what the provider explicitly does not do yet, and for what’s on their roadmap versus what’s actually shipped today. A vendor willing to draw that line clearly is more trustworthy than one whose entire pitch is unqualified confidence.
The checklist
Does the provider take custody of funds at any point, and can you get that confirmed in writing?
What’s the documented process for disputes, refunds, and wrong-network transfers?
Can you export clean, real-time settlement data — with transaction hashes — without extra reconciliation work?
Is the all-in fee — including any FX or conversion spread — disclosed, not just the headline rate?
Has the provider clearly stated what’s live today versus what’s on the roadmap?
None of these questions are unique to crypto. They’re the same questions a finance team would run on any payments vendor. The only difference with stablecoins is that the answers are newer, the standards are still forming, and it’s worth being more skeptical of vendors who sound too certain.