Bank account verification for stablecoin payouts depends on the rail. The UK and euro-area schemes now match the payee's name against the account, Pix and UPI show the name before the payment, and ACH and Fedwire have no name check at all. On those two, and on SPEI, where we found none, the check is yours to add, with a verification API or a simpler rule: pay out only to an account the user has already paid in from. In the US, Certos and LSEG check an account without a bank login and Plaid and Stripe verify it through one, while SurePay and iPiD sell name checks elsewhere.
It matters because an off-ramp receives stablecoins, which can't be pulled back, and pays the proceeds to a bank account the user names. If that account isn't the user's, the payout may not come back either: Stripe's payout docs warn that funds sent to the wrong bank account might not be recoverable.
Account Checks by Payout Rail
These are the rails stablecoin card issuers list for payouts, and our comparison of stablecoin virtual accounts shows which issuer offers each. For each rail, here is whether the scheme checks the payee's name before money moves, and what else you can use:
| Rail | Market | Name Check Before Payment | Other Checks |
|---|---|---|---|
| RailACH | MarketUS | Name Check Before PaymentNone | Other ChecksBank login, micro-deposits, database checks |
| RailFedwire | MarketUS | Name Check Before PaymentNone | Other ChecksAs for ACH; a wire is final once processed |
| RailSEPA and SEPA Instant | MarketEurope | Name Check Before PaymentVerification of Payee (VoP): euro area since 9 Oct 2025, non-euro EU by 9 Jul 2027 | Other ChecksBank login (Tink, TrueLayer); name checks (SurePay, iPiD) |
| RailFaster Payments | MarketUK | Name Check Before PaymentConfirmation of Payee (CoP) | Other ChecksBank login (TrueLayer); name checks (SurePay, iPiD) |
| RailPix | MarketBrazil | Name Check Before PaymentKey lookup shows the name, part of the CPF, and the bank | Other ChecksNames on new or changed keys checked against tax records since 1 Jul 2025 |
| RailUPI and IMPS | MarketIndia | Name Check Before PaymentName shown before transfer; NEFT and RTGS too since Apr 2025 | Other ChecksPenny drop APIs (Cashfree, RazorpayX) |
| RailSPEI | MarketMexico | Name Check Before PaymentNone we could confirm | Other ChecksCLABE control digit (format only) |
| RailFAST and MEPS | MarketSingapore | Name Check Before PaymentPayNow shows the registered name; account-number FAST treats the name as reference only | Other ChecksCross-border name checks (iPiD) |
| RailSWIFT | MarketCross-border | Name Check Before PaymentNone; Swift Payment Pre-validation between participating banks | Other ChecksiPiD; LSEG Global Account Verification |
The euro-area check comes from the Instant Payments Regulation, which requires payment providers to offer payee verification on euro credit transfers.
A scheme check only helps if someone reads the result. CoP and VoP return a match, a close match with the name the bank holds, no match, or no answer, and a close match or no match on a first payout is the moment to stop and ask the user.
Which Checks Ramps and Issuers Run
CoP and VoP are run by the payer's payment provider, which on a stablecoin payout is usually your ramp or issuer. Their developer docs differ on what they check and when:
| Provider | What It Checks Before a Payout | When It Runs |
|---|---|---|
Provider  Bridge | What It Checks Before a PayoutVoP on EUR IBAN and UK accounts: match, close match with the bank's name, no match, or error. US accounts can be linked through Plaid Link | When It RunsWhen the platform calls the verify endpoint |
| ProviderStripe Global Payouts | What It Checks Before a PayoutCoP on GBP payouts from a UK financial account to a UK account; a payout without a match waits for your confirmation | When It RunsAutomatically, when the payout is created |
Provider MoonPay Enterprise | What It Checks Before a PayoutEach payout account is registered first, and registration can fail on an invalid IBAN or routing number or a mismatched recipient name. Accounts are marked first- or third-party | When It RunsAt registration; the docs say there's no separate recipient verification step |
Provider Wirex | What It Checks Before a PayoutSeparate permissions for payouts to the user's own accounts and to third parties. On SEPA and ACH, a recipient whose name equals the user's verified name counts as first party | When It RunsAt the payout estimate, against the saved recipient's name |
Provider StraitsX | What It Checks Before a PayoutFirst-party payouts go only to a verified account: verified by a deposit from it, by bank account proof within one working day (Singapore accounts), or by a match with the KYC name (SWIFT accounts) | When It RunsWhen the user deposits from the account, or when the platform adds it by API |
Provider Rain, Interlace | What It Checks Before a PayoutNot described in docs we could access | When It RunsAsk them |
StraitsX's deposit route works on any rail: pay out only to an account the user has already paid in from. TrueLayer's Verified Payouts do the same over Faster Payments and SEPA Instant, and a ramp that gives each user a virtual bank account sees which accounts send money in. A recipient name matched against your own KYC record shows whose account the user says it is; only the bank's data shows whose it is.
Where the docs are silent, as with Rain (ACH, Fedwire, and SPEI) and Interlace (ACH, SEPA, and SWIFT), ask three things per corridor. Does the provider run the scheme check, does it return the result to you, and does it hold a payout that doesn't match? For the providers and rails in each region, see our payout comparisons for the US, Europe, Asia, Latin America, Africa, and the Middle East.
How Each Verification Method Works
Five methods cover the gaps, and only some of them tell you who owns the account:
| Method | What It Confirms | User Effort | Speed | Where It Works |
|---|---|---|---|---|
| MethodBank login (open banking) | What It ConfirmsAccount details from the bank; owner name with an ownership product | User EffortLogs in to their bank | SpeedSeconds | Where It WorksUS (aggregators); UK and EU (PSD2) |
| MethodMicro-deposits | What It ConfirmsThe user can see the account | User EffortEnters a code or amounts | Speed1-2 business days; seconds over RTP or FedNow | Where It WorksUS |
| MethodDatabase or network check | What It ConfirmsOpen or closed status; ownership match | User EffortNone | SpeedReal time | Where It WorksUS |
| MethodScheme name check or penny drop | What It ConfirmsThe name matches the account, or the bank returns it | User EffortNone | SpeedSeconds | Where It WorksUK, SEPA, Brazil, India |
| MethodFormat validation | What It ConfirmsThe number is well formed | User EffortNone | SpeedInstant | Where It WorksEverywhere |
- Bank login. The friction is the cost: some users won't share a banking login.
- Database checks. Coverage depends on which banks contribute data.
- Scheme name checks. Only authorised payment service providers can join CoP, directly or through aggregators such as Banfico, iPiD, and SurePay. A platform that isn't one relies on its payout provider or buys name checks from SurePay or iPiD. In India, payout APIs use penny drop: a small credit, usually ₹1, whose response carries the holder's name.
- Format validation. IBAN check digits, routing number checks, and UK modulus checking catch typos, but a fraudster's real IBAN passes.
Verification APIs for the Gaps
| Provider | Method | Markets | Returns | Best For |
|---|---|---|---|---|
| ProviderPlaid | MethodBank login, micro-deposits, database | MarketsLogin: US, Canada, UK, Europe; other flows US | ReturnsAccount numbers; ownership with Identity Match | Best ForEvery US fallback in one integration |
| ProviderStripe Financial Connections | MethodBank login, micro-deposit fallback | MarketsUS and Canadian accounts | ReturnsAccount details; owner names and addresses, except for micro-deposit accounts | Best ForPlatforms already on Stripe for ACH or payouts |
| ProviderCertos (Early Warning) | MethodBank-contributed data | MarketsUS | ReturnsOpen, closed, or overdrawn; ownership | Best ForUS payouts where a bank login would cost conversions |
| ProviderLSEG Risk Intelligence (formerly GIACT) | MethodAccount data checks | MarketsUS; cross-border in markets LSEG doesn't list | ReturnsValid, open, and ACH-ready; ownership | Best ForNo-login US checks plus some cross-border coverage |
| ProviderTrueLayer | MethodBank login; CoP in the UK | MarketsUK and EU | ReturnsName match; match to the deposit account | Best ForPaying withdrawals back to the account that funded the user |
| ProviderTink (Visa) | MethodBank login | MarketsEurope | ReturnsOwner against account number or IBAN | Best ForProof of ownership at onboarding |
| ProviderSurePay | MethodScheme name check (CoP, VoP) | MarketsUK and EU | ReturnsMatch, close match, or no match | Best ForName checks for platforms that aren't payment providers |
| ProvideriPiD | MethodCross-border payee verification | MarketsMany countries | ReturnsName and account match | Best ForPayouts to many countries; ask for match rates per corridor |
| ProviderCashfree | MethodPenny drop, pennyless, UPI | MarketsIndia | ReturnsStatus, holder name, match score | Best ForPayouts to Indian bank accounts or UPI IDs |
Of these, only Stripe (per verification, on its pricing page) and Cashfree (₹3 per check, pay-as-you-go) publish prices.
Nacha Rules for ACH Account Validation
Nacha's rules reach both sides of an ACH ramp. If users fund on-ramps by ACH debit, the WEB debit rule, in force since 19 March 2021, requires the originator to validate the account on first use and whenever the account number changes. The minimum is that the account is open and can accept ACH entries; ownership isn't required. Nacha doesn't mandate a method: prenotes, micro-transactions, validation services, and API-based tools can all qualify, and micro-deposits must carry the description ACCTVERIFY.
Payouts are ACH credits, and the 2026 fraud-monitoring rules cover them. Since 20 March 2026, all ODFIs, and non-consumer originators, third-party service providers, and third-party senders that originated 6 million or more ACH entries in 2023, have needed risk-based processes to identify entries that are unauthorised or authorised under false pretences. Receiving banks that took in 10 million or more entries in 2023 have had to monitor incoming credits the same way. Everyone else followed in Phase 2 on 19 June 2026, a federal holiday, so Nacha expects compliance by Monday 22 June.
How to Verify a Payout Account
In the US, run a no-login check (Certos or LSEG) on every new payout account, and add a bank login (Plaid or Stripe) where you need proof of ownership, such as before a first large off-ramp. Whoever originates your ACH payouts now needs a fraud-monitoring process, and checking where the money goes is the obvious start. In the UK and EU, get the CoP or VoP result back from your provider, and buy name checks from SurePay or iPiD if it can't give you one. Elsewhere, combine the local checks in the rail table (Pix key lookups, penny drop in India, PayNow names in Singapore) with iPiD or LSEG.