Tesouro exposes four payment rails. Pick the rail by use case: internal sweep, same-day settlement, real-time receipt, or cross-bank push. Each has different speed, availability, limits, and reversibility characteristics.Documentation Index
Fetch the complete documentation index at: https://docs.tesouro.com/llms.txt
Use this file to discover all available pages before exploring further.
Rail comparison
| Rail | Speed | Direction | Availability | Max per transfer |
|---|---|---|---|---|
| Internal | Instant | Internal only | 24/7 | No service cap |
| ACH | One to three business days | Send and receive | Business days | Set by bank |
| RTP | Seconds, irrevocable | Send and receive | 24/7/365 | $10M (TCH) |
| FedNow | Seconds, irrevocable | Send and receive | 24/7/365 | $10M (Fed) |
Prerequisites
| Prerequisite | Notes |
|---|---|
| Internal account | An open, funded deposit account opened through the onboarding flow. |
| External account | A pre-linked external account (see Linked accounts) for ACH. |
| Authentication | A bearer token with embedded:transfer:write. ACH, RTP, and FedNow additionally need their per-rail scope. |
| Org rail config | The caller’s organization must have the rail enabled (managed in the Profile service). A disabled rail returns 403. |
Next steps
- Linked accounts — how external accounts get into Tesouro before ACH push/pull will work.
- Authentication — scope wiring and token issuance.