RTP (Real-Time Payments, operated by The Clearing House) settles in seconds and is available continuously. Once accepted by the receiving bank, an RTP transfer is irrevocable — there is no reversal, no return, no recall mechanism.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.
POST /embedded-banking/v1/money-movements/rtp
The request shape is the common shape; RTP does not take a type or SEC code. The service caps RTP at $10,000,000 per transfer (the current TCH network limit).
RTP delivery depends on the receiving institution participating in the RTP network. If a non-participating receiver is detected at submission time, the request fails synchronously with a 4xx and no transfer record is created. Rejections that happen after Tesouro has accepted the transfer are not currently surfaced as a status change — plan to monitor for non-arrival on the receiver side, and fall back to FedNow or ACH on a synchronous failure.
Required scope:
embedded:transfer:write and payment_rail:rtp.