Every crypto payment gateway sits somewhere on a spectrum: does the money land in their balance first, or does it go straight into your wallet? That single design choice affects fees, operational risk, accounting and how quickly you can spend or convert what customers pay.
This article explains custodial versus non-custodial crypto payments in plain merchant language, then maps the ideas to Cryptomo's balance model and the own-wallet option on the Pro and Business plans. The goal is not ideology, but a practical decision framework for stores, agencies and freelancers.
What "custodial" means for an online store
In a custodial flow, the gateway generates a deposit address it controls. The buyer pays that address. After network confirmation, your merchant balance on the platform increases. Later you withdraw to your exchange or wallet, or keep funds on the platform for payouts and refunds.
Upsides for merchants
- Faster onboarding: no addresses or xpubs to configure per coin
- One balance for multi-coin checkout (BTC, USDT, ETH, SOL and more)
- Easier refunds and payouts, because funds are already on the platform
- A good fit when finance wants one ledger before treasury moves money
Trade-offs
- You rely on the platform's security and withdrawal process until you withdraw
- A per-payment fee may apply (on Cryptomo Starter it is 1% per balance payment, see pricing)
- Withdrawals add a step between "customer paid" and "funds in my wallet"
Custodial here is about where value sits after payment, not whether checkout is hosted. A hosted checkout (QR code, exact amount, countdown) can sit in front of either model.
What "non-custodial" (own-wallet) means
In a non-custodial flow, the gateway still runs the checkout, pricing, rate locks and webhooks, but the on-chain destination is your address, or an address derived from your xpub. Cryptomo never holds that payment as a platform balance.
Upsides
- Funds arrive under keys you control (hardware wallet, multisig, treasury storage)
- 0% fee on own-wallet payments on Cryptomo Pro and Business
- A clean story for teams that already have a crypto treasury policy
Trade-offs
- You must keep addresses and xpubs correct and understand networks (USDT on Ethereum is not the same as USDT on BNB Chain)
- Refunds and mass payouts may need a separate workflow
- Key management mistakes are your risk: a lost seed phrase cannot be recovered by a support ticket
Non-custodial acceptance is different from running your own node. You still want signed webhooks, invoice expiry and underpayment handling; those are product features, not custody.
How Cryptomo maps the two models
Cryptomo lets you start simple and move to own-wallet later without changing plugins.
| Model | How it works | Plan | Fees |
|---|---|---|---|
| Balance (custodial) | Payments credit your Cryptomo balance; withdraw when ready | Starter (free) | 1% per balance payment |
| Own-wallet (non-custodial) | Payments go to your addresses or xpub | Pro ($49/mo) or Business ($99/mo) | 0% on own-wallet and balance payments |
Hosted checkout, payment links, plugins, the REST API and signed webhooks work the same on every plan. Always confirm current numbers on the pricing page before you budget.
Decision framework
Start with the balance model if…
- You are testing demand for crypto and want to measure support load
- You do not yet have a multi-coin treasury process
- Your volume is low and a percentage fee is simpler than a monthly plan
- You want to see all balances in one place before withdrawing
Move to own-wallet (Pro or Business) if…
- 1% of your monthly crypto volume is more than $49 or $99
- Finance or compliance prefers funds never rest with a third party
- You already run hardware wallets, multisig or exchange treasury accounts
- You run many storefronts (10 stores on Pro, 50 on Business)
A quick example: at $10,000 of monthly crypto sales, 1% costs $100, so Pro at $49 already saves money.
The hybrid reality
Many merchants keep a small balance for refunds or payouts while routing most revenue to their own wallets. Design your process around where money should live overnight, not around a slogan.
Security is not only custody
Whichever model you choose, insist on:
- Two-factor authentication on the merchant dashboard
- Signed API requests and signed webhooks (verify the HMAC; never trust an unsigned POST)
- Address locks and careful change control for payout and receiving addresses
- Least-privilege API keys and IP allowlists where possible
Accounting checklist
- Document the model in your finance process: "customer pays → balance" or "customer pays → treasury address".
- Reconcile webhooks to invoices (
paid,paid_over,partially_paid) rather than guessing from block explorers. - Keep networks separate in your books (USDT on Solana is not USDT on Ethereum).
- Test a withdrawal (balance model) or a small own-wallet invoice before announcing "we take crypto".
- Review plan economics every quarter.
This is operational guidance, not tax or legal advice; local rules still apply to your business.
Next step
Not sure? Start on Starter, take a handful of real orders into your balance, measure fees and support tickets, then upgrade when own-wallet payments and multi-store limits match how you sell. Create your free account and read the API docs for invoice statuses.
