RTP - Outbound or Send
RTP Outbound Payment Flow - Successful

Example RTP Outbound Flow
Note: Step 3 is found in following the Funds Movement diagram.
Funds Movement

- TabaPay receives an outbound credit transfer request through the TabaPay API from the Merchant.
Note: Sponsor bank can request merchants must digitally sign every transaction request with the credentials provided by Sponsor Bank when the merchant opened their account. This secure digital signature provides non repudiation for Sponsor Bank to debit the merchant account.
- TabaPay places the inbound credit transfer request to the Sponsor Bank
- Sponsor Bank moves funds from Merchant Prefunded Account to the Sponsor Bank-RTP Account. To successfully perform the transfer, the Merchant Prefunded Account must have sufficient funds.
Insufficient Funds at the Merchant Prefunded Account: If a Merchant RTP Account (Merchant Prefunded Account) has insufficient funds, then Sponsor Bank rejects the outbound credit transfer request
TCH Declines: In the case of declined credit transfers at TCH, then the Sponsor Bank transfer from the Merchant Prefunded Account to the Sponsor Bank-RTP account must be reversed.
- The Sponsor Bank responds back to TabaPay that the transaction is authorized by the Sponsor Bank
Note: In the event of an exception, Sponsor Bank responds back to TabaPay that transaction is not authorized by Sponsor Bank.
- TabaPay sends request to TCH-RTP for a Credit Transfer.
- TCH responds to the Credit Transfer with accepted (ACTC) or rejected (RJCT).
Rejected Credit Transfer (RJCT): In the event of a rejected credit transfer or rejected (RJCT), the funds that originally moved from the Merchant RTP Account to the Sponsor Bank-RTP account must be reversed (back to the Merchant RTP Account at Sponsor Bank).
- TabaPay responds back to the merchant with a response from TCH.
Connection Issue: In the event of a connection issue with TCH, TabaPay will relay UNKNOWN to the merchant and settle the transaction next day.
RTP Outbound Payment Flow - Reversals
The flow diagram for an outbound payment flow remains the same. The status from Create Transaction should be COMPLETED
.
If a reversal is requested to you, you will receive a request, and you can use the Delete RTP Transaction API with the ?response
Query Parameter.
Note: If you are using the TabaPay Unified API to request a refund, you can use the Delete RTP Transaction API request with ?request
Query Parameter.
Sponsor Bank Obligations
As a Sponsor Bank, you have certain obligations and capabilities when managing funds in your merchant accounts.
Account Balances
Authorize each outbound credit transfer ONLY if sufficient funds are available in the Merchant Prefund Account.
- Move each authorized outbound credit transfer from the Merchant Prefund Account. Do not authorize a payment if the Merchant Prefund Account has insufficient balance prior to debiting the account. Without the Sponsor Bank's successful authorization, the credit transfer is not originated by TabaPay.
TabaPay maintains a maximum daily limit a merchant may originate. Total Sponsor Bank daily limit is governed by the total funds in the TCH-Sponsor Bank Fed account. This account must be maintained for smooth a payments flow and cannot go negative.
Managing Merchants
You can lock (or unlock) a merchant on the TabaPay system.
You can opt for merchants to digitally sign the transaction request with secure credentials provided by a Sponsor Bank (when the merchant opened their account at the Sponsor Bank). This secure digital signature would provide a non-repudiation for the Sponsor Bank to debit the merchant account.
Sponsor Bank Integration with TabaPay
To begin your integration, contact [email protected].
Changes to Enable Bank Statement for RTP Transactions
Please refer RTP Bank Statement.
Updated 13 days ago