A client sends USDT to fund an account. The support ticket arrives eleven minutes later: the money left their exchange but the trading account still shows nothing. Three things could be true. The transfer is waiting for confirmations. It went to the address the firm published for a different chain. Or it arrived correctly and nobody has told the ledger which client it belongs to. Only the third one is a software problem, and it is the one a payment processor exists to remove.
What the processor adds on top of a wallet
A wallet address receives coins and tells you nothing about who sent them. A processor turns that into a payment. It issues a unique deposit address or a time-limited invoice for each attempted payment, so an inbound transaction can be attributed to a client without a human reading a blockchain explorer. It watches for the confirmation threshold appropriate to the chain. It quotes a rate and holds it for a defined window. It screens the sending address before crediting. It settles to the firm in whatever the firm asked for, and it produces a reconciliation feed the finance team can tie to the ledger.
Remove those layers and you have not saved money, you have hired someone to do them by hand at three in the morning. That is the calculation every firm makes when it decides whether a processor's percentage is worth paying.
Custody is the fork in the road
Two models dominate. In the custodial model, the processor holds the coins, converts them and pays the firm in fiat or in a stablecoin balance on a settlement cycle. In the non-custodial model, funds move directly to addresses the firm controls, and the processor provides the address generation, monitoring and reporting without ever holding the assets.
The choice is a risk trade, not a preference. Custodial settlement gives you counterparty exposure to the processor and a settlement delay, and takes away the operational burden of key management. Non-custodial keeps the assets under your control and hands you every question about wallet security, key backup and who can sign a withdrawal. It also changes the regulatory picture, because a firm holding client crypto is a different animal from one whose processor converts at the door. Anything touching virtual asset service provider registration should be a conversation with counsel before it is a conversation with a vendor.
The volatility window, and who pays for it
Between the moment a client is shown an amount to send and the moment the transaction confirms, the price can move. Someone absorbs that. Processors handle it in one of three ways: a locked quote for a short window, after which the payment is repriced or rejected; a spread wide enough to cover normal movement; or no lock at all, with the firm crediting whatever the conversion produced.
This is why stablecoin deposits dominate in practice. A dollar-referenced token has a much smaller window problem than bitcoin, which is a large part of why firms steer clients toward stablecoins even when they accept a broader list. Firms that credit trading accounts in real time need the window to be short, because a client who deposits and immediately opens a position has created an exposure before the conversion has even settled.
Crypto deposits are irreversible. That removes chargeback risk and replaces it with a harder operational rule: a credit posted to the wrong account, or to an account that later fails verification, cannot be pulled back by pressing a button. Get the attribution right at the door.
Chains, memos and the support queue
Most crypto support tickets are not fraud. They are the same four operational failures, repeated. A client sends a token on a chain the firm does not monitor, because the same ticker exists on several networks and the difference between them is invisible in a wallet's send screen. A client omits the destination tag or memo on a chain that requires one, so the funds land in an omnibus address with no attribution. A client sends from an exchange's hot wallet, so the sending address belongs to the exchange and not to the client. Or a client sends less than the amount quoted and expects full credit.
Each of these is preventable in the deposit interface rather than in the ticket queue. Show the network name in large type next to the address, refuse to display an address until the client has picked the network explicitly, warn on memo-required chains, and state the minimum. The differences between the same stablecoin on different networks are worth spelling out for clients, because the cost of learning them by accident falls on both sides.
The compliance that arrives with the coins
Crypto deposits do not exempt a firm from anything. Sanctions and address screening apply on the way in, and blockchain analytics vendors score inbound addresses for exposure to mixers, sanctioned entities and known theft. A firm needs a documented policy for what happens when a deposit scores badly, including whether funds are frozen, returned to the originating address, or held pending review, and who signs that decision off.
The travel rule adds originator and beneficiary information requirements to transfers between regulated providers, which is why some processors ask for data that feels excessive relative to the size of the payment. Third-party deposits are the other recurring problem: a transfer from an address that demonstrably is not the client's breaks the same principle as a card in someone else's name, and the anti-money-laundering framework a firm operates under does not soften because the rail changed.
Choosing one, and wiring it in
The questions worth asking a processor are unglamorous. Which chains and tokens, with which confirmation thresholds. Settlement currency, cycle and any rolling reserve. What the total cost is once conversion spread is added to the headline percentage. Whether withdrawals to clients are supported on the same rail, because deposit-only support leaves you solving payouts twice. What the API sends on a partial payment, an overpayment and a late confirmation, since those webhooks decide how much manual work your back office inherits.
On the firm's side, crypto should be one funding method among several inside the same ledger, with the same verification gates and the same audit trail. That is how we built the payment layer in the Broker CRM: the rail changes, the approval workflow does not. A firm that treats crypto as a separate universe with its own spreadsheet ends up with two versions of the truth, and reconciles them the hard way.
"Nobody loses money on crypto deposits because of the price of bitcoin. They lose it because a payment was credited to the wrong account and the transaction cannot be reversed."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- A processor's real product is attribution, rate locking, screening and reconciliation; the wallet part is the easy half.
- Custodial settlement trades counterparty exposure for convenience; non-custodial hands you the keys and every question that comes with them.
- Most crypto tickets are wrong-chain, missing-memo, exchange-wallet or underpaid deposits, and the deposit screen prevents them better than support can.
- Irreversibility removes chargebacks and raises the cost of a mistake, so verification and attribution have to happen before the credit posts.
Frequently Asked Questions
What does a crypto payment processor do that a wallet does not?
A wallet receives coins. A processor issues a unique address or invoice per payment so deposits can be matched to a client automatically, watches the chain for confirmations, locks a conversion rate for a defined window, screens the sending address, settles to the firm in the currency it asked for, and provides a reconciliation feed and refund path. Without those layers, matching on-chain funds to accounts becomes manual work.
Do crypto deposits remove chargeback risk?
On-chain transfers cannot be reversed by the sender, so the card chargeback mechanism does not exist. Other risks replace it: funds arriving from a sanctioned or high-risk address, third-party deposits that break know-your-customer rules, and disputes handled by the firm directly because no scheme sits in the middle to arbitrate them.
Does accepting crypto require a licence?
It depends on the jurisdiction and on who holds the coins. A firm that takes custody of client crypto or exchanges it may fall under a virtual asset service provider regime, while a firm whose processor converts at the door and settles fiat may sit differently. The analysis belongs to the firm's own lawyers, because the same commercial arrangement is treated differently in different regimes.