Connect to TCH RTP through a participating bank or middleware provider (e.g. a sponsor bank's API or a fintech like Modern Treasury) since direct TCH access requires being a member financial institution
Construct a credit transfer message conforming to the ISO 20022 pacs.008 schema, including debtor agent BIC, creditor agent routing number, creditor account, amount, currency (USD), and end-to-end ID
Submit the payment message to your sponsor bank's RTP submission endpoint; RTP operates 24/7/365 including weekends and holidays
Expect a synchronous or near-real-time acknowledgment (pacs.002 positive or negative) within seconds; a positive confirmation means funds are irrevocably settled
Handle negative acknowledgment (reject) by inspecting the status reason code in the pacs.002 response and either correcting the payment data or notifying the sender
Known gotchas
RTP transaction limit is $10M per transfer as of mid-2026; amounts above this must be split or sent via wire
RTP is credit-push only — there is no debit or pull capability on the RTP network; the sender's bank must initiate
Not all US financial institutions are RTP-enabled receivers; confirm the beneficiary's bank participates before attempting, or provide a fallback payment rail
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp