Most payout complaints are routing problems described as trust problems. The firm sends the payment, the client sees nothing, and the space between those two facts fills with an assumption of bad faith. Understanding the chain is what lets a support team say something true instead of something reassuring.
The chain a wire actually travels
A cross-border wire rarely goes from bank to bank. It travels through correspondent relationships, and where the sending and receiving banks have no direct link, one or more intermediary banks sit in the middle. Each one applies its own screening and its own compliance policy, and each one can hold or return the payment for reasons the sending firm never sees.
That is why the destination country matters more than the amount. Where a currency's correspondent access is thin, payments queue behind fewer institutions and every one of them is applying enhanced scrutiny. De-risking removed those links from entire regions, and the visible symptom is payouts to certain countries taking days longer than identical payouts elsewhere. The difference between SEPA and SWIFT is mostly a difference in how many parties touch the money.
The five things that actually stop a payment
Name mismatch is the most common and the most avoidable. The beneficiary name on the instruction must match the name on the account. Transliterated names, married names, middle names present in one system and absent in the other, and company names abbreviated by the sender all produce returns days later. Screening a payout against the verified identity documents at the point of request removes most of these before they leave.
Sanctions screening is the second. Screening engines match on names and produce false positives at a rate that surprises people, particularly for common names in certain languages. A hit is not an accusation, it is a queue, and clearing it means a human comparing dates of birth and countries against a list entry. Screening runs at the firm, at its bank and at every intermediary, so the same payment can be stopped three times for the same reason.
Source of funds documentation is the third. Banks ask the paying firm to evidence why a payment is being made, and firms without a clean trail from deposit to trading activity to withdrawal struggle to answer quickly. Third party payments are the fourth: paying anyone other than the account holder is refused as a matter of policy at most institutions and is a genuine money laundering typology, not a formality.
The fifth is the firm's own hold. AML checks triggered by a withdrawal pattern are legitimate, but they land on the client as silence. Explaining why a hold exists before it is applied is the difference between a compliance step and a public accusation.
Payment rules, sanctions obligations and reporting duties differ by jurisdiction and change frequently. This describes mechanisms only. Firms must take their own legal and compliance advice on the rails and countries they use.
Rails behave differently by country
Domestic instant rails are fast, cheap and closed. Many are only available to institutions established locally, which is why a firm banked in one region cannot simply plug into another region's instant scheme without a local partner or a virtual account arrangement. Virtual IBANs solve part of this by giving the firm accounts that look local to the receiving side, though the underlying institution and its policies still decide what clears.
Card payouts, where supported, run on separate scheme rules from card payments and carry their own eligibility and limits. Crypto payouts avoid correspondent banking entirely and replace it with a different set of constraints: travel rule information requirements on transfers between service providers, exchange level screening on the receiving side, and the local legal position on whether the client can convert at all. Crypto withdrawal holds are usually imposed by the receiving exchange, not the sender.
What a firm can control
The controllable parts are narrow and they matter. Collect and verify beneficiary details once, at onboarding, in the exact form the receiving bank will see. Screen at the point the request is made rather than at the point the batch is sent, so a hit is resolved while the client is still engaged. Publish a realistic processing window per rail and per region instead of one global number the firm misses for half its client base. Tell the client which stage the payment is at, including when it has left the firm and is with the banking chain.
That last one is the cheapest fix available. A payout queue with visible stages, an audit trail and a status the support team can read out converts most complaints into questions. Comparing the rails before promising a timeline is the other half. Firms that promise three days on every rail because one rail can do three days will miss the promise for everyone on the others, and the reputational cost lands on the brand rather than on the intermediary bank that caused it.
"Clients think we are sitting on their money. Nine times out of ten it is parked at an intermediary bank neither of us chose, waiting for a document neither of us can supply."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Cross-border wires pass through intermediary banks that screen independently, so delays usually happen outside both the firm and the client's bank.
- Beneficiary name mismatches, sanctions screening hits, source of funds questions and third party payments cause most returns.
- Domestic instant rails are generally restricted to locally established institutions, and crypto swaps banking friction for travel rule and exchange side checks.
- Verify beneficiary details at onboarding, screen when the request is made, and publish a realistic window per rail and per region.
Frequently Asked Questions
Why does a withdrawal take longer to some countries than others?
Because the number of correspondent banking links available for that currency and country differs. Where those links are thin, payments route through more intermediaries, each applying its own screening and compliance checks, which adds days that neither the sending firm nor the client can see.
What is the most common reason a payout is returned?
A mismatch between the beneficiary name on the payment instruction and the name registered on the receiving account. Transliteration, middle names and abbreviated company names all cause it, and the return usually arrives days after the payment left.
Do crypto payouts avoid these problems?
They avoid correspondent banking and replace it with different checks. Transfers between regulated service providers carry travel rule information requirements, receiving exchanges run their own screening and may hold funds, and the client's local rules determine whether they can convert to their own currency at all.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.