Getting started
Guides
Evaluate a corridor before you commit to a provider
The mistake is checking coverage first. Entity eligibility kills more integrations than coverage does, so check who can onboard you before you check where they can pay.
- 1.Set your entity jurisdiction — this is where your company is incorporated, not where your users are.
- 2.Set the destination country and currency, then the rail (local transfer behaves very differently from SWIFT).
- 3.Read the unavailable results first: the reason tells you whether the block is structural or paperwork.
- 4.Record your KYB documents once; “supported” becomes “supported for you”.
- 5.Monitor the corridor so a coverage change reaches you before your integration does.
Read a Railor verdict properly
A verdict is a claim about published information, with a timestamp. Treat confidence and freshness as part of the answer.
- 1.Supported means every dimension of your query has a supporting source.
- 2.Additional requirements means one dimension is conditional — the reason names it.
- 3.Unavailable always carries a reason and, where it exists, what would change it.
- 4.Unknown means Railor found no reliable source. It is not a soft no.
- 5.Check last-verified: a 0.95 confidence checked six months ago is not the same claim as one checked this morning.