Coverage

Where money can come from, and where it can go

We publish the rule rather than a map that would be out of date by the time you read it. The live list is shown at onboarding and again on every payout.

Funding

Rails you can pay in with

  • EURSEPAEuro area · credit transfer
  • GBPFaster PaymentsUnited Kingdom · near instant
  • USDACHUnited States · batch
  • USDFedNowUnited States · instant
  • BRLPixBrazil · instant
  • MXNSPEIMexico · same day
  • COPPSEColombia · same day
  • More railsAdded as approvals land

The rule

How a destination becomes usable

  1. 01

    Approval lands

    A corridor only opens once the approvals behind it — ours and our partners' — are in place for that jurisdiction.

  2. 02

    It joins the list

    The authorised list is what the product reads. Nothing outside it can be selected as a destination.

  3. 03

    You see it at payout

    When you build a payout, the destinations offered are the ones authorised at that moment — not a cached copy.

  4. 04

    Screening still applies

    Being in an authorised jurisdiction is necessary, not sufficient. Recipient screening runs on every payout.

Limits

What we will refuse

Unauthorised destinations
If a jurisdiction is not on the authorised list, the payout cannot be created. Not delayed — not creatable.
Screening hits
A recipient or destination flagged by sanctions screening stops the payout, and the case is reviewed by a person.
Unverified accounts
An account that has not completed identity checks cannot move money, in or out.
Mismatched details
Where the scheme supports name checking, a mismatch between the account name and the recipient stops the transfer.

None of this is negotiable per customer. A control that can be waived on request is not a control.

Check your corridor

Tell us where you collect and where you pay out, and we will tell you what is open today.

Ask us