• The Recipes section has been updated to include the following examples in cURL, Python and JavaScript:
  • The Processor Tokens section has been updated to include TabaPay integration with Multiple Processors, or migrating from another processor over to TabaPay.
  • 📣 Status Code 422 and Error Code Updates: Coming Soon
    A future date will be published for both Sandbox and Production.\
    • Status Code (SC) 422 will be updated to include a Bank Identification Number (BIN) to identify the financial institution of the associated upstream transaction error.
    • As a reminder, Internal Error Codes should not be used for any client error handling. EC values are intended solely for TabaPay’s internal use and will be subject to change in the future.
      EC values will be updated to include dynamic values, and the length will of EC values will be increasing in Sandbox and Production. EC values will continue to only be used internally.

Status Code

Error Message

Action

422 Unprocessable Entity

"EM":"Destination Disabled: XXXXXX" ,
"EM":"Source Disabled: XXXXXX"

Query Card to check if push or pull is enabled for the correlating BIN listed in the example XXXXX

Note: Previously the error message did not include the BIN XXXXX.

  • More Recipes have been updated to include the following in cURL, Python, and JavaScript requests and JSON response:

Required Fields

📘

Effective October 18, 2024

Fields corresponding.dateOfBirth and corresponding.sourceOfFundswill be required starting October 18, 2024/

  • corresponding.dateOfBirth - REQUIRED - Date of birth with the format: YYYYMMDD. Sender must be at least 18 years old.
  • corresponding.sourceOfFunds- REQUIRED - Sender Source of Funds. Valid Values Include:
    • Debit Card
    • PrePaid Card
    • Credit Card
    • Cash
    • Deposit Account
    • Credit Account
    • Mobile Money Account

Recommended Fields

  • corresponding.networkID - Unique ID for each transaction identifying the network from the preceeding Account Funding Transaction (AFT), or pull transaction.
    • We strongly recommend clients prepare now to send this field by October 18, 2024.
  • corresponding.nationality - Sender Nationality using country codes.
  • corresponding.countryOfBirth - Sender of country of birth using country codes.
  • corresponding.email - Sender email (max of 40 characters)
  • corresponding.occupation - Sender occupation.
  • destinationAccount.owner.email- Recipient or beneficiary email.

Refer to the recipe below as a cross-border OCTexample of these fields.


  • Create Transaction has been updated to include pullOptions.expirationDate for Real-Time Payment (RTP) Request for Payment (RFP).

  • Manage Users is now live in the TabaPay Portal for all clients and approved users.
    Note: You must have administrative permissions to be able to use manage users.
  • Single sign-on (SSO) is now available the TabaPay Portal. SSO helps simplify the login process, enhance the user experience, increase security, and reduce password fatigue.