Authenticate with your Increase API key and confirm your account has Real-Time Payments (RTP) enabled
Submit a credit transfer via POST /real_time_payments_transfers with amount up to 1000000000 cents (the TCH RTP per-transfer limit is $10,000,000, raised effective 2025-02-09)
Poll GET /real_time_payments_transfers/{id} or handle the real_time_payments_transfer.completed webhook to confirm settlement
On rejection, inspect the rejection.reason field — TCH rejection codes include ACCOUNT_CLOSED, INVALID_CREDITOR_ACCOUNT_NUMBER, and LIMIT_EXCEEDED
For LIMIT_EXCEEDED, verify the transfer amount does not exceed $10,000,000 per transaction; for account-based rejections, surface the reason to the user and do not automatically retry
Implement idempotency by reusing the same idempotency key on retries for transient failures only
Known gotchas
The TCH RTP per-transfer cap is $10,000,000 (raised 2025-02-09) — NOT $1,000,000; submitting above $10M will result in a LIMIT_EXCEEDED rejection
RTP is final and irrevocable once settled — there is no recall mechanism; always validate account and routing numbers before submission
Increase sandbox RTP transfers settle synchronously in test mode but may behave differently in production depending on the receiving bank's RTP participation
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