Every cross-border merchant eventually hears the story. A seller wakes up, opens the payment dashboard, and finds the account balance locked. No warning, no clear reason, only a banner saying the account is "under review." Support replies with a template. Weeks pass. Meanwhile the supplier invoice is due, ads are still running, and payroll does not wait. Account freezes are one of the most common failure points in online payments, and they hit small merchants hardest because small merchants have the least bargaining power and the thinnest cash buffers.
Non-custodial payment gateways exist largely because of this problem. Instead of holding your money and settling it later, a non-custodial gateway routes each payment directly to a wallet or account that you control, and provides software around it: invoices, order matching, callbacks, and reconciliation. That architectural difference removes an entire category of freeze risk. But it does not remove all risk, and pretending otherwise would be dishonest. This article walks through how the two fund flows differ, where freezes actually happen, what a non-custodial setup does and does not protect against, and the habits that reduce the residual risk.
Two Fund Flows, Two Risk Profiles
Everything follows from one question: between the moment your customer pays and the moment you can spend the money, who is holding it?
The custodial flow
In a custodial model, the customer's payment lands in an account controlled by the payment company. Card processors pool funds in merchant accounts; wallet providers hold balances in omnibus accounts; crypto processors receive coins into their own wallets. Your dashboard shows a number, but that number is an IOU, a claim on the company, not money in your possession. Settlement to your bank or wallet happens later: T+1, T+3, T+7, or longer depending on the channel and your risk profile. During that entire window, the funds sit inside someone else's legal and technical perimeter.
The non-custodial flow
In a non-custodial model, the gateway does not take possession of the funds. A crypto payment goes from the customer's wallet to your wallet on-chain; the gateway watches the transaction, confirms it, and fires a callback to your store. There is no pooled balance, no settlement window, and no IOU. The gateway's role is coordination, not custody. If the gateway's servers went offline tomorrow, the money already in your wallet stays in your wallet.
Where Freezes Actually Happen
"Frozen funds" is a loose term that covers several distinct mechanisms, and they happen at different points in the flow:
- Processor-level holds. A custodial provider flags your account for a review: a spike in volume, a dispute ratio crossing a threshold, a document expiring, a product category it decides it no longer likes. Payouts pause while the review runs, and reviews run on the provider's schedule, not yours.
- Rolling reserves. Many card processors withhold a percentage of every batch for 90 to 180 days as chargeback insurance. This is contractual, not a surprise freeze, but the cash-flow effect is identical.
- Scheme and acquirer pressure. Card networks can push acquirers to hold funds or terminate merchants in high-dispute programs, and the acquirer passes that pressure down to you.
- Bank-level freezes. Even after money reaches your bank account, the bank can freeze it under its own compliance obligations or a court order.
- Off-ramp freezes. If you receive crypto and later convert it on a centralized exchange, the exchange is itself a custodian and can restrict your account during a review.
The pattern to notice: a freeze requires a custodian. Whoever holds the money has both the technical ability and, usually, the legal obligation to stop it from moving.
Freeze Points, Side by Side
| Stage | Custodial gateway | Non-custodial gateway |
|---|---|---|
| Payment in transit | Held in the processor's accounts | Moves directly on-chain or between your own accounts |
| Settlement window | T+1 to T+7 or longer; payouts can be paused | No settlement window for crypto receipts; funds are already yours |
| Stored balance | Balance is an IOU on the provider | No balance stored with the provider |
| Provider failure or policy change | Funds can be locked with the account | Already-received funds are unaffected |
| Conversion to fiat | Handled inside the provider; subject to its review | Done on an external off-ramp; that off-ramp has its own custody risk |
| Bank after withdrawal | Bank rules apply | Bank rules apply identically |
The table shows the real picture: a non-custodial design removes the provider from the list of parties that can freeze your funds. It does not remove every party.
What Non-Custodial Does Not Protect Against
Honesty matters here, because overpromising is how merchants get hurt.
Issuer-level controls
Major centralized stablecoins are issued by companies that operate under regulation, and those issuers maintain the technical ability to freeze specific addresses at the smart-contract level, typically in response to law-enforcement orders or sanctions screening. This is rare and targeted at illicit activity rather than ordinary merchants, but it is a real property of the asset. A gateway's custody model has no influence over it. Decentralized assets like BTC or ETH do not have this switch, which is one reason some merchants spread receipts across more than one asset.
Off-ramps and banks
The moment you convert crypto to fiat through a centralized exchange, or receive card settlements into a bank account, you are back inside a custodial perimeter. Exchanges run the same kind of compliance reviews that processors do, and banks answer to their own regulators. Non-custodial collection shortens the time your money sits in third-party hands; it does not exempt the endpoints of the flow from the rules those endpoints live under.
Your own obligations
Tax reporting, sanctions awareness for high-risk jurisdictions, refund commitments, and honest fulfillment all remain yours. A non-custodial gateway changes who holds the money, not what the law expects from you. Merchants who treat "non-custodial" as "unaccountable" tend to meet the bank-level freeze described above.
Habits That Reduce the Residual Risk
With the provider removed from the middle, the remaining risk concentrates at the edges. A few practical habits keep those edges small:
- Separate collection from storage. Receive customer payments into a dedicated wallet, then sweep funds to a deeper-storage wallet on a schedule. A compromise or dispute at one layer does not touch everything.
- Do not let fiat balances pile up off-ramp. If you convert through an exchange, convert in batches and withdraw; treat any custodial balance as temporary by design.
- Keep order records exportable. Invoices, shipping proofs, and callback logs are your evidence if a bank or off-ramp ever asks where the money came from.
- Run more than one channel. Cards through a processor plus crypto through a non-custodial gateway means no single review can stop all of your revenue at once.
- Understand each channel's terms before volume grows. Reserve percentages, settlement days, and review triggers are published or negotiable; check the official site for current rates and terms before you commit.
Conclusion
A custodial payment gateway can freeze your funds because freezing is a power that comes with custody: whoever holds the money can stop it. A non-custodial gateway does not hold the money, so the freeze button simply is not there. That removes the most common and least predictable freeze point in cross-border selling. What remains are the edges: issuer-level controls on centralized stablecoins, compliance reviews at off-ramps and banks, and your own legal obligations. Design for those edges with wallet separation, disciplined off-ramping, and clean records, and the phrase "my account is under review" stops being an existential threat to your business.
If you are evaluating a non-custodial setup for your store, the integration documentation covers wallet configuration, callbacks, and testing, and you can create an account to inspect the fund flow yourself before moving real volume. For a broader setup path, see our first cross-border payment walkthrough.