Changelog

Changelog 12/27/24

  • The TabaPay Portal Transaction List and Transaction Details page has been updated to include the originating (Sender) currency and the Beneficiarycurrency. Previously only the beneficiary currency was displayed. Refer to the Amount column in the following example:

    ExampleAmountStatus
    New12.99 CAD --> (est) 9.58 USDCompleted
    Old9.58Completed
    • Note: The actual Transactions List will display more columns listed in Create Transaction Response Body.

  • Update Account v1 and Update Account v2 descriptions have been updated to reflect the following path parameters: https://{<<FQDN>>}/{Version}/clients/{<<glossary:ClientID>>}/accounts/{<<glossary:Account ID>>}

    • Use v1 to replace all fields.
    • Use v2 update any one or more fields (e.g. Owner, Address, Phone, Exp. date), excluding card account numbers.

  • Visa Mandates

    • Effective 1 January 2025, the Digital Commerce Services Fee (DCSF), or (VDCF) will be based on authorized transactions rather than clearing and settlement.
    • Effective 25 May 2025, Visa will update the system integrity fee program authorization retry logic to
      improve authorization processing and optimize the consumer experience through more transaction approvals.
      • Authorization retry evaluation criteria will be updated to include the cardholder-initiated transaction (CIT) versus merchant-initiated transaction (MIT) identifier.
      • The number of retries permitted after a Category 2, 3, or 4 response code decline will increase from 15 retries in 30 days to 20 retries in 30 days (Visa Rules ID#: 0030640)

  • As a reminder, TabaPay will maintain its current freeze dates from December 23 to January 1.

    • Note: Only small changes to existing sub-clients or the creation of new sub-clients permitted.

Changelog 11/27/24

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

  • Two new Visa Authorization Response Codes have been listed on the Network Response Codes page to increase transparency during authorization. These response codes will be effective April 11, 2025.

    These updates are to encourage good business practices, reduce fraud, improve authorization approval rates, reduce operational costs, and enhance satisfaction across the payments ecosystem. TabaPay Clients can use the new information to correct issues and optimize the resubmission of authorization requests

    Reponse CodeDetailCategoryRe-attempt Allowed
    5CTransaction not supported/blocked by issuer2Yes
    9GBlocked by cardholder/contact cardholder2Yes

Changelog 10/31/24

  • 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.

Changelog 9/30/24

Status CodeError MessageAction
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:

Changelog 8/29/24

Changelog 7/29/24

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.

↗️
22. Cross-Border OCT
Open Recipe

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

Changelog 5/14/24

Changelog 4/15/24

  • 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.

Changelog 3/15/24

  • 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.

Questions? Contact Sales or make a post