• 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 Code	Detail	Category	Re-attempt Allowed
  5C	Transaction not supported/blocked by issuer	2	Yes
  9G	Blocked by cardholder/contact cardholder	2	Yes

• 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.
  • New: Stripe Tokens + TabaPay Tokens - You can now use both Stripe and TabaPay together as your payment processors.
  • Existing: Cybersource, Galileo, Helix by Q2, Plaid, Unit - Combine any of the third party processors with TabaPay.
  • Migration of Token Vaults - Fully move over from any of the listed third party processors 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.

• The Browser SDK is now available to accept card payments from your customers using the Dynamic iFrame , a low-code customizable payment experience right on your website. For a reference of all customization options, refer to the Browswer SDK Reference.
• Auth & Capture is out of beta and now available for select uses cases to authorize payments with the intent to complete the payment within a given timeframe (e.g. 24 hours).
• The Create Transaction API has been updated to include the Bank Identification Number (BIN) in the API response when there is a Status Code: 422 - Unprocessable Entity.
  Clients should follow the recommended action, Query Card based on the given error message. Refer to Error Handling for general practices in resolving status code errors.

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:

• Create Transaction has been updated to include the following fields for Merchant Initiated Transactions (MIT). For examples, refer to the MIT Recipes listed in the updates below.
  • pullOptions.recurringData.initial
  • pullOptions.recurringData.initiator
  • pullOptions.recurringData.type
  • pullOptions.recurringData.id
  • pullOptions.recurringData.networkID
• Enriched TabaPay Shield Attributes has been updated to include descriptions on the following attributes:
  • Network Identifier
  • CAVV Results Code
  • UCAF Downgrade Indicator
  • ACI Code
  • Payment Account Reference
  • ECI Response
  • Merchant Advice Code
• The following Recipes have been updated to include the following in cURL, Python, and JavaScript requests and JSON response:
  • B2C Push Transaction
  • MasterCard CIT
  • Mastercard MIT
  • Visa CIT
  • Visa MIT
  • CIT with Accounts
  • MIT with Accounts

• Create Transaction has been updated to include the following required and recommended fields on all Cross-border Original Credit Transactions (OCTs), or international push to card transactions:

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

• Updated Recipes to include the following in cURL, Python, and JavaScript requests and response:
  • ACH API Push Transaction
  • Person to Person (P2P) Pull Transaction
  • P2P Push Transaction
  • Account to Account (A2A) Pull Transaction
  • A2A Push Transaction

• The API Reference has been updated to include request and responses Pull with Enriched TabaPay Shield Attributes for both Visa and MasterCard (MC).

• Partial Authorization has been updated for payment acceptance (pull) to include client permissions. To request Partial Auth, contact TabaPay Support.
• API Reference has been updated to include an Expand All button to immediately view all objects. Select Expand All and you can search, or quick find (CTRL + F / CMD + F) a specific field. We welcome feedback at https://developers.tabapay.com/discuss.
• Recipes have been updated to include new TabaPay API code snippets in Python, JavaScript, and cURL. To request any new examples, comment at https://developers.tabapay.com/discuss, or email [email protected].
  • Query Card
  • Create Pull Transaction using RSA Token
  • Create Pull Transaction using iFrame Token
  • Create Pull Transaction with Card Info
  • Create Pull Transaction Using Accounts

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

• ACH (Automated Clearing House) is now available for payment acceptance (pull) and payouts (push) via the Create Transaction API.
• ANI (Account Name Inquiry) is now live via the Query Card API.
• Reports has been updated to now include refreshed FX daily rates for Visa and Mastercard.