RTP Edge Cases
RTP edge cases can occur when a connection failure or timeout interrupts communication between TabaPay, The Clearing House (TCH), and participating financial institutions. The following scenarios explain what occurs at each point in the payment flow, whether funds move, and any required reconciliation or follow-up action.
Real-Time Payments (RTP) can return an UNKNOWN transaction status when TabaPay does not receive a definitive response during transaction processing. An UNKNOWN status does not confirm whether the payment succeeded or failed.
Network or bank connection timeouts can cause an UNKNOWN result.
UNKNOWN Is Not a Failed TransactionAn
UNKNOWNstatus may result from a network timeout and does not confirm that the original payment failed. Reconcile the original transaction to confirm its final outcome.
Why an RTP Transaction Can Be UNKNOWN
An RTP payment passes between TabaPay, The Clearing House (TCH), and participating financial institutions. A connection failure or timeout can prevent one participant from receiving a response even when another participant processed the message.
The following scenarios describe where these failures can occur.
The following scenarios outline edge cases for RTP to consider during your RTP integration.
1. Receive pacs.008: Bank Connection Failure/Timeout with Bank
1. No Response from Bank Steps
- TCH sends pacs.008
- TabaPay validates the pacs.008 file
- TabaPay sends the bank request with the reformatted pacs.008
- No response from the sponsor bank
- TabaPay rejects pacs.008 and stores transaction as UNKNOWN
- TCH receives the pacs.002
- TabaPay reconciles the RTP transaction next business day
TabaPay Receives No Response from Bank
| Bank Response | TabaPay Response | Did TCH move money | Action Item |
|---|---|---|---|
| Accepted | Rejected | No | Bank to reconcile off of TabaPay's next day Report |
| Rejected | Rejected | No |
Receive pacs.008: TCH Connection Failure/Timeout with TCH
2. No TCH Receipt of pacs.002 Steps
- TCH sends pacs.008
- TabaPay validates the pacs.008 file
- TabaPay sends the bank request with the reformatted pacs.008
- Bank receives request and sends response
- TabaPay formats bank's response to pac.002
- TCH may or may not have received pacs.002
- TabaPay reconciles the RTP transaction next business day
TCH Receipt of pacs.002 is Unknown
If TCH does not receive a pacs.002, money will NOT move
If TCH does receive a pacs.002, money will move according to the status
| Bank Response | TabaPay Response | pacs.002 Received | Action Item |
|---|---|---|---|
| Accepted | Accepted | Yes | None |
| No | Bank is short amount, must debit the customer account that received funds | ||
| Rejected | Rejected | Yes | None |
| No |
Send pacs.008: TCH Connection Failure/Timeout
3. Outbound pacs.008 UNKNOWN Steps
- Client sends RTP request
- TabaPay receives the request and sends the pacs.008 file
- TCH receives pacs.008
- TCH attempts to send pacs.002—connection failure
- TabaPay does not receive pacs.002, stores the transaction as
UNKNOWN, and Sends to client - Client receives
UNKNOWNresponse - TabaPay reconciles RTP transaction next business day
8a. If no reversal is needed, then no action needed
8b. If Reversal is needed, TabaPay sends camt.056 file - TCH receives camt.056 and sends pacs.008
- TabaPay validates the pacs.008 and sends reformatted pacs.008
- Bank receives the pacs.008
Outbound pacs.008 Status is Unknown
If TCH does not receive a pacs.002 money will NOT move
If TCH does receive a pacs.002, money will move according to status
| TCH Response to pacs.008 | Did Bank move money? | Action Item |
|---|---|---|
| Accepted | Yes | None |
| No | TCH has moved money, Bank to move money from customer to TCH | |
| Rejected | Yes | TabaPay will issue a camt.056 to TCH, and pacs.008 is sent to Bank |
| No | None |
Updated 6 days ago