On the payments rail
Every payout, on the rail that clears it soonest.
One endpoint, 38 markets, 24 currencies. Basis resolves the corridor, prices it before it sends, and posts the movement to the same ledger your close reads from.
Median settlement
Currencies payable
Markets on local rails
The lifecycle
Four states,and a reason for each.
Each state carries the evidence the next one needs, which is why support can answer without opening a ticket with the bank.
01 · Intent
You send one payout intent
Amount, beneficiary and your own reference. No corridor logic on your side — the same call works for a SEPA credit transfer and a Pix key.
Idempotent by key
02 · Routing
We pick the rail that clears soonest
Local scheme wherever you have one, correspondent only where you do not. The fee and the expected arrival come back before the payout leaves.
Priced before it sends
03 · Retry
Failures come back with a reason
Scheme codes are mapped to language your support team can send on. Retry windows are per-code, so a wrong IBAN never burns the attempts a bank outage needs.
14 codes retried on policy
04 · Posting
It lands in the ledger, double-entry
Rail reference, FX timestamp and entity attribution on one record. Finance closes from it and exports the same figures the auditor asks for.
Posted in under a second
Why local rails
The same payout, two ways.
Correspondent banking still moves most cross-border money. This is what changes when the payout goes out on the beneficiary's own scheme instead.
| Per payout |
Correspondent banking
Wire relayed through intermediaries
|
|
|---|---|---|
| Speed | ||
| Median settlement | 0.4s | 2–5 business days |
| Cut-off windows | None | Weekday bank hours |
| Cost | ||
| Fee per payout | From $0.20 | $15–45 wire fee |
| FX spread | 0.35% on mid-market | Undisclosed |
| Full amount arrives Intermediary banks take a lifting fee from money in transit, so the beneficiary receives less than you sent. On a local scheme there is no intermediary to deduct. | Included | Not included |
| Operations | ||
| Failure reason returned | Included | Not included |
| Your reference preserved end to end | Included | Not included |
| Reconciliation | Automatic, nightly | Manual from statements |
What ships with it
Control you can hand to treasury.
Routing you can override
Pin a corridor to a named scheme when treasury policy says so. Basis still prices it, still retries it, still posts it the same way.
Rules per corridor
Retries with a policy
Capped attempts, per-code windows, and a webhook the moment a payout is terminal — so nothing sits in limbo waiting to be noticed.
Terminal state webhook
Evidence, not screenshots
Every attempt keeps its scheme reference and timestamp, exportable in the shape your auditor already asks for.
Nightly export