Confirm your sponsor bank's RTP gateway supports the RemittanceInformation element in the CreditTransfer message (ISO 20022 pacs.008 via TCH)
Populate the Strd remittance block with RfrdDocInf (invoice number, type CINV, date) and RfrdDocAmt (DuePyblAmt, RmtdAmt) for each invoice being paid
For multi-invoice payments include multiple RfrdDocInf entries within the same CdtTrfTxInf up to the character limit imposed by the TCH network (check current structured remittance size cap)
Submit the enriched pacs.008 and store the UETR (Unique End-to-End Transaction Reference) returned by the network for tracking
On the receiving side, parse the Strd remittance block from the inbound pacs.008 notification to auto-apply cash against open invoices
Fall back to Ustrd (unstructured) remittance if the receiver's bank strips structured data — detect stripping by comparing sent vs received remittance fields
Known gotchas
TCH RTP has a per-transaction dollar limit that is periodically reviewed; do not hardcode the limit — check your sponsor bank's current cap at integration time
Not all receiving banks pass the full structured remittance through to their customers; test end-to-end with a real receiving bank before relying on Strd parsing in production
UETR is generated by TCH, not by you; it may differ from your internal EndToEndId — store both for reconciliation
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