Stablecoin Payment IntegrationTake and send stablecoins, inside the business you already run.
The rails have run for five years, with real merchants and real money.
Every payment on this page settles through a crypto payment gateway built and operated by our team, in production with real merchants and real users since before stablecoin payments were a product category. The numbers below are what that record looks like.
- 5+ years
- Live payments under on-chain finality
- 0
- Failed payments
- 50+ merchants
- 4M+ transactions processed
Crypto payment and wallet infrastructure, built and operated by our team
CPAY: crypto payments and wallets, five years in production
- Merchants integrate checkout and charge flows through the API; payments, refunds and internal transfers run in one system
- Payment flows were designed so that no completed payment needs a manual correction
- No emergency intervention in a completed payment has been needed since launch
- Acceptance: hosted checkout and API
- Payouts and mass payouts
- Recurring billing and subscriptions
- Payroll and contractor payments
Four places in your business can change. Nothing else does.
Stablecoins come in and go out through the same doors every payment method uses, plus one more: a balance your users can hold. We connect the ones you need and leave the rest of your system alone.
Acceptance
A hosted payment page, or the API inside your own checkout. For the verticals card processors decline, this is the way in: the customer pays from their own wallet, you see an order that turns paid.
Payouts and settlements
Pay affiliates, sellers, traders and contractors from one balance, singly or in bulk, with an approval step on your side and a report finance can file. Invoice counterparties and get paid against it.
{ "id": "pay_10482",
"amount": "120.00", "asset": "USDT",
"fee": "0.60", "net": "119.40",
"reference": "ORDER-10482" }Reconciliation and treasury
Every confirmed payment is written to your ERP or ledger as one row: amount, fee, net and your reference. Incoming addresses are screened. Balances across networks can be converted into one treasury asset by rule.
User balances
A stablecoin balance for every user of your platform, behind the login they already have. Deposits from outside, transfers between users inside, withdrawals out.
- USDT and USDC, in and out
- Hosted checkout or your own, through the API
- One row per payment in the ERP you already trust
- A balance per user, if your platform needs one
- 0.5% per payment; nothing monthly
What finance sees the next morning. Money in, money out, swaps.
Payments, deposits, withdrawals, payouts and swaps all land in the same ledger. Most rows are routine. The integration is judged by the ones that are not.
Paid in full, short, late, or on the wrong network.
Most payments and deposits arrive exactly as expected while the office is closed. The other three cases are where support tickets come from, unless they are handled by rule.
What the integration does
- Matches amount and network, waits for your confirmations, marks the order paid or credits the balance
- Short: records what arrived and applies your rule, a tolerance, a top-up request or a refund
- Late: keeps the funds linked to the original order and flags fulfil or refund
- Wrong network: leaves the balance unchanged and opens a recovery case with the facts filled in
You decide Confirmations per network, the tolerance for short payments, which networks you accept at all
A demo, one call, one integration, then it runs
The first payment lands in staging before anything goes live. Both teams see what the integration really is before it is accepted.
- Demo and technical call
Free. You see the gateway working; we look at where money enters and leaves your business, which records we write to and who holds the balance. You leave with a one-page integration map and a fixed price.
- Integration
Acceptance, payouts, webhooks, ledger, the cases above. The first payment is accepted in staging against criteria both sides signed; then it goes live.
- Live
0.5% per payment, nothing monthly. We run the rails, the monitoring and the people who answer when something looks wrong.
What it costs
Stablecoin Payment Integration
What moves the price
- Hosted checkout, or the API in your own
- Acceptance only, or payouts and settlements too
- Which of your systems we write to
- Whether your users need balances of their own
What it costs
Stablecoin Payment Integration
What moves the price
- Hosted checkout, or the API in your own
- Acceptance only, or payouts and settlements too
- Which of your systems we write to
- Whether your users need balances of their own
Who holds the balance, and where our part ends
Scope is measured in networks, rails and custody. Use the hosted checkout page or put the API inside your own; either way, the money question is decided first.
Custodial
Payments settle into an account we operate for you; you withdraw when you want. Simplest to run, and usually a licence question for you.
Non-custodial
Payments settle to wallets whose keys you hold. Nobody else can move the money, and recovery is a design you get right before launch.
Both are offered. We settle the choice on the call, because moving between them later is a project of its own.
Where our part ends
- Nothing to host
- Our page, your logo
- Fastest route in
- Inside your checkout
- Your design, your flow
- Webhooks to your system
Stablecoin payment questions, answered
What finance and product teams ask before taking stablecoins. If yours is not here, ask on the call.
Stripe already takes USDC. Why would I need this?
What is stablecoin payment integration?
Which stablecoins and networks are supported?
Do I end up with stablecoins or with money in the bank?
Can my users hold a stablecoin balance on my platform?
Who holds the money?
What happens with a short, late or wrong-network payment?
How do refunds work?
What does the 0.5% cover, and what else do I pay?
When is this the wrong choice?
How long does it take?
Tell us where the money comes in and goes out
Your business, the payment methods you have today and the system that records them. If stablecoins are the wrong shape for it, we will say so on the first call.