Skip to main content
Every fiat rail Rain moves money over settles through a local payment scheme. Use this page to know, before you create a quote or a payment route, whether an amount is in range, how fast funds will land, and by when a transfer must be submitted to settle the same day. These are the limits Rain enforces.

​
Reading the tables

  • Rail is the value you pass as destination.rail when creating a quote or payment route (source.rail for onramps).
  • Scheme is the local payment network the payout clears through (the provider-side rail). It explains the timing below; you always pass the Rail value, never the scheme.
  • Use cases describe who sends and who receives: B2B business → business, B2C business → individual, C2B individual → business, C2C individual → individual. All means every pairing is supported. The pairing is derived from the sending customer’s profile and the destination account’s beneficiary type — a payout outside the listed pairings is rejected at quote time.
  • Min / Max are per transfer in the local fiat currency: the source currency for onramps, the destination currency for offramps. “No cap” means Rain imposes no per-transfer maximum; your organization’s own limits still apply.
  • Expected settlement for onramps is measured from when the sender submits the fiat payment; for offramps, from when the crypto deposit is confirmed. Where it depends on size, the threshold is shown in the currency the scheme measures it in.
  • Cutoff is the time by which a transfer must be submitted to settle within the stated window, shown with the fixed UTC offset the scheme publishes (not adjusted for daylight saving — e.g. 23:59 (GMT+0) is 23:59 UTC year-round); “24/7” means the scheme processes around the clock with no cutoff.

​
Onramps

Fiat → crypto through an onramp payment route, including MXN onramps over SPEI. Limits and timing apply to each incoming fiat deposit.

​
Offramps

Crypto → fiat, one-time through Offramps with Transfers (quote + transfer), or persistently through an offramp payment route for USD (ach, wire) and MXN (mx_spei). Limits and timing apply to each payout, whichever way it was created. ¹ Transfers of 40,000 BRL or more per transaction, or totaling 40,000 BRL or more per month, may be subject to additional review before settlement. ² NEFT clears in half-hourly batches rather than in real time; for an instant INR payout use in_imps. ³ co_mobile_wallet limits and timing depend on the beneficiary’s wallet:
A quote whose amount falls outside the corridor’s limits fails with invalid_amount. Settlement and cutoff times are set by the local scheme and can change; treat them as expectations, not guarantees.

​
Available upon request

These corridors can be enabled for your organization by your Rain representative; the rail value to use is shared during enablement. ³ JPY is also capped at 3,000,000 per day, 3,000,000 per month and 8,000,000 per year. See Payment Account Details for the bank fields each rail requires when creating the destination payment account.