Key takeaways
- A checkout gateway takes a payment. A platform needs deposits credited to accounts and withdrawals paid out on request.
- A deposit runs in five steps: deposit address, payment, detection and screening, conversion and credit. A withdrawal goes out only once your platform releases it.
- Holding the platform balance in a dollar stablecoin stops a deposit moving in value once it has been converted.
- Your platform decides every withdrawal, by its own rules or by a person; the processor executes it, converting into an asset you do not hold where needed.
- The rules are dated and public: the FATF Travel Rule, FINTRAC's travel rule guidance from 1 June 2021, MiCA's stablecoin titles from 30 June 2024 and the US GENIUS Act from 18 July 2025.
- Before you sign, check registration, withdrawal control, who holds the liquidity and whether every movement can be reconciled.
Crypto and stablecoin payments for a platform have to do more than take a payment. Your users deposit crypto into an account, hold a balance with you and withdraw it later, so the processing behind it must credit each deposit to the right account, convert it into a stablecoin where you want a stable unit, and pay out the withdrawals you approve. Stablecoin payments for platforms work the same way: the platform balance sits in dollar-pegged tokens, and conversion happens on the way in and on the way out.
Most crypto gateways were built for shops, where one customer pays one invoice. That leaves the harder half of the job, money going back out, to your team.
What are crypto and stablecoin payments for a platform?
Definition: crypto payments for a platform are the deposits and withdrawals that let users fund an account in crypto, keep a balance and take it out again, with each movement tied to a verified user and recorded in a ledger the platform can reconcile.
A stablecoin is a token built to hold a steady value against a currency, usually the US dollar. USDC is described by its issuer as backed by cash and cash-equivalent assets and redeemable 1:1 for US dollars (USDC issuer). USDT, issued by Tether, is pegged 1:1 to the US dollar according to its issuer (Tether). For a platform, the useful property is that a balance held in a dollar stablecoin tracks the dollar instead of the wider crypto market.
How is platform processing different from a checkout gateway?
A checkout gateway is built around an order. A platform is built around an account that persists.
| Requirement | Checkout gateway | Platform processing |
|---|---|---|
| Main job | Take one payment for an order | Run deposits and withdrawals for an account |
| Who receives the money | The merchant | The user's account on your platform, and later the user |
| Money out | Refunds, occasionally | Withdrawals every day, approved by the platform |
| Identity | Often light for small payments | Needed for the account and for money moving in and out |
| Records | One invoice per payment | A ledger per user, reconciled with platform balances |
| Integration | Plugin or hosted payment page | API and webhooks, or an interface embedded in your product |
If your users hold a balance with you, the right-hand column is your specification.
How does a crypto deposit work on a platform?
- Your platform requests a deposit address. It is generated for one user and linked to a stable customer ID, so every deposit maps to the right account.
- The user sends crypto from a wallet they already use, in a supported asset on a supported network.
- The transaction is detected and screened. It is picked up on chain and checked for risk, and the user's verification status is checked too.
- It converts where needed. A deposit that is not already a dollar stablecoin is converted into one. A supported stablecoin can stay as it arrives.
- Your platform credits the user once the funds are secured and the checks pass.
Crediting any earlier, before the checks pass and the funds are secured, leaves your platform carrying a payment that may not complete.
How do withdrawals work?
A user asks to withdraw inside your platform, and your team or your rules approve or decline it, because only you know the account and any open disputes. An approved request goes to the processor as an instruction. The processor converts the amount from your stablecoin balance into the asset the user asked for, where needed, and sends it to the wallet address they supplied.
So you don't need to hold every asset your users might want. If you hold dollar stablecoins and a user wants a different supported asset, the conversion happens at the point of withdrawal.
Managing the balance: how should a platform keep its stablecoin float steady?
A platform's stablecoin balance is mostly money it owes back to users, so it works like a float. Most treasury guides are written for companies investing their own balance sheet in crypto; a platform holding user deposits wants as little price exposure as possible and tight control over outflows. Four habits cover most of it.
- Hold one stable unit. Users usually see their balance in dollars. Holding the matching funds in a volatile asset lets the two drift apart; a dollar stablecoin keeps what you hold and what you owe in the same unit.
- Size liquidity from your own history. Hold total user balances plus a buffer for your busiest withdrawal days, and review the figure at least monthly.
- Separate requesting from approving. The person who requests a payout should not be the only one who can approve it, and larger payouts deserve a second approver.
- Record every movement. One record per deposit, conversion or withdrawal, with the user reference, assets and amounts in and out, any fee, the transaction hash and the time.
Stablecoins carry issuer and network risk, so read each issuer's own disclosures, such as the USDC issuer's and Tether's, before you choose which tokens to hold.
What does a deposit and withdrawal look like in numbers?
Illustrative example. The figures are invented to show the flow. They leave out fees, conversion spreads and network costs, and they are not Cessor pricing.
A platform starts the day holding 50,000 in dollar stablecoins.
| Event | What happens | Platform balance (USD stablecoins) |
|---|---|---|
| Start of day | Opening balance | 50,000 |
| User A deposits 500 USDC | Screened, kept as it is, user credited with 500 | 50,500 |
| User B deposits crypto worth $1,200 at conversion | Screened, converted into 1,200 of dollar stablecoins, user credited | 51,700 |
| User C asks to withdraw $800 in a different supported asset | Platform approves; 800 of stablecoins is converted and sent to User C's wallet | 50,900 |
User B's deposit stopped moving in value once converted. User C was paid in an asset the platform never held. The platform made one decision all day, the withdrawal approval.
Which rules apply to crypto and stablecoin payments?
Rules depend on where the provider and platform are registered, so treat this as orientation, not legal advice.
The Travel Rule. The Financial Action Task Force's October 2021 guidance applies Recommendation 16 to virtual asset transfers: providers must collect and pass on sender and recipient information (FATF).
Canada. FINTRAC's travel rule guidance for electronic funds and virtual currency transfers took effect on 1 June 2021. Money services businesses must include the sender's and recipient's name, address and account or reference number (FINTRAC). Businesses dealing in virtual currencies must register with FINTRAC as a money services business before they operate in Canada (FINTRAC).
EU: MiCA. Regulation (EU) 2023/1114 was adopted on 31 May 2023. Its titles on asset-referenced and e-money tokens, which capture stablecoins, have applied since 30 June 2024, and the rest since 30 December 2024 (Article 149, EUR-Lex).
US: the GENIUS Act. S. 1582 was signed into law on 18 July 2025 as Public Law 119-27 and provides for the regulation of payment stablecoins (GovInfo).
Your platform keeps its own obligations whatever your provider does.
Should you build, stitch providers together or use one processor?
| Setup | What you run | What it suits | What to watch |
|---|---|---|---|
| Build it | Wallets, monitoring, conversion, ledger, identity | Teams with payments engineers and a reason to own every layer | Staffing, security and registration burden |
| Stitch providers together | Separate providers for deposits, identity, conversion and withdrawals | Platforms that already have some pieces | Separate accounts and support paths your team keeps in step |
| One processor | Your interface and rules; the processor runs deposits, conversion and withdrawals | Platforms wanting one integration for money in and out | Who handles user support, and the support terms |
If unsure, ask who handles a delayed withdrawal at 2am under each setup.
What should you ask a provider before you sign?
Use this checklist in a vendor review.
| Check | Evidence to ask for | Passes when | Warning sign |
|---|---|---|---|
| Registration | Legal entity, registration number and the register it appears on | You can look it up on the regulator's public register | "Fully regulated" with no entity or number |
| Screening before credit | A description of the deposit flow | Your platform is told to credit only after checks pass | Credit first, review later |
| Withdrawal control | Integration docs or a demo | No withdrawal leaves without your instruction or your rules | The provider can release funds without your instruction |
| Asset coverage | A written list of assets and networks for your platform | It covers what your users hold and want to withdraw | "Most assets" with no list |
| Identity | A written split of KYC responsibilities | Who runs checks, who pays and who keeps the evidence is clear | "We handle all compliance" |
| Travel Rule | Their process for transfers to and from other providers | They describe how sender and recipient data is collected and sent | No answer, or "it doesn't apply to us" |
| Liquidity | Contract terms on funding balances and withdrawals | It is clear who holds the funds that cover user balances | Vague promises to cover shortfalls |
| Records | A sample ledger export | Every movement has a user, network reference and amounts | Only daily totals |
How does Cessor handle this?
Cessor is a crypto payment processor for platforms. Your platform integrates once and your team sees every payment in and out, with balances and reporting, in one dashboard.
- Receive takes deposits in the crypto your users already hold. Cessor runs the deposit steps above, watches the network and tells your platform when a payment is detected, pending and completed, so you credit the user once it has completed.
- Convert turns Bitcoin and Ethereum into USD stablecoins as each payment completes. USDC and USDT land as they are, and each conversion is recorded beside the payment that caused it.
- Send pays withdrawals straight to the wallet a user names, from your USD stablecoins. Roles and limits decide who can send payouts, and up to how much.
Supported assets are agreed with each platform, so talk to Cessor about yours. You can check Cessor's FINTRAC registration on the public register.
Cessor is not the right fit in every case:
- You want a provider to fund withdrawals. Your platform provides the liquidity; Cessor manages the movement around it and doesn't front withdrawals.
- You want someone else to decide who is paid. Withdrawal rules and approvals stay with your platform.
- You need card payments, bank transfers, or only a checkout button for one-off orders. Cessor handles crypto, and a checkout gateway is simpler for single orders.
- You want to run your own wallets and own every layer. Building it yourself may suit you better.
What to do next
- See how Cessor accepts crypto payments, sends payouts and converts them to stablecoins, and what your team sees in the dashboard.
- Browse more Resources, or talk to Cessor about the assets your users hold.
Frequently asked questions
What is the difference between a crypto payment gateway and crypto payment processing for platforms?
A gateway takes a payment for an order and passes it to the merchant. Platform processing runs deposits and withdrawals for accounts that persist, with each movement tied to a verified user and recorded in a ledger. If your users keep a balance with you and withdraw later, you need platform processing.
How long does a crypto deposit take to credit?
It depends on the network the user pays on and how many confirmations it needs. The deposit is screened and converted once it has arrived, and the user is credited after the checks pass. Because confirmation times vary by network, be wary of any single figure quoted for every asset.
Can we keep our own interface?
Yes. Many platforms keep their own account screens and send deposit and withdrawal instructions to a processor through an API. You then usually run your own KYC provider and stay first-line support.
Does a crypto processor take over our compliance obligations?
No. A processor runs its own obligations, such as screening transactions and handling Travel Rule data for the transfers it makes. Your platform keeps the obligations that come with its own product and users. Ask any provider for a written split of responsibilities, and take legal advice for your jurisdiction. This page is general information, not legal advice.
Is Cessor a bank?
No. Cessor is a crypto payment processor for platforms. Pay Cessor Ltd, doing business as Cessor, is registered with FINTRAC as a money services business, and registration is not an endorsement of our services by FINTRAC or any other authority. Cessor is not a bank, and funds or digital assets held with it are not deposits and are not insured by the Canada Deposit Insurance Corporation or any other deposit insurance scheme.