Distinguish and handle RTP credit transfer versus RTP Request for Payment message types in a TCH RTP integration

Steps

1. Understand the two primary RTP message flows: the credit push (pacs.008 Customer Credit Transfer) moves funds from sender to receiver instantly; the Request for Payment (pain.013) asks the payer to authorize a credit push — no funds move until the payer approves
2. For credit push: construct a pacs.008 message with required fields (creditor account, debtor account, amount, end-to-end ID) and submit via your RTP-connected bank's API; expect a pacs.002 acknowledgment within seconds
3. For RFP: send a pain.013 to the debtor's routing/account; the debtor's FI presents it to the account holder; if accepted, a pacs.008 flows back to you automatically; if declined, you receive a pain.014
4. Handle pacs.002 negative acknowledgments (rejection codes) for the credit push: map rejection reason codes to user-facing messages and implement retry logic only for transient errors (e.g., system unavailable), not for hard rejects (e.g., invalid account)
5. Reconcile by end-to-end ID: both credit transfers and RFP responses carry the same end-to-end identification you assigned; use it as the idempotency and matching key in your ledger