Getting started with TabaPay

“The Road goes ever on and on
Down from the door where it began.
Now far ahead the Road has gone,
And I must follow, if I can" - Bilbo Baggins, The Hobbit

TabaPay's Unified API

Our mission at TabaPay is to enable instant access of funds for all.

You can use our Unified API by simply calling the Create Transaction endpoint. A multitude of configurable parameters give you the flexibility you need to create a payment processing experience that is right for you. You can push or pull funds, accept various payment methods, as well as offer support for cross-border or domestic transactions.

For example, pull $100:

{
   "accounts": {
         "sourceAccountID": "zxc4123412341234123412",
         "destinationAccountID": "1234123412341234abc412"
    },
    "referenceID": "abc123",
    "type": "pull",
    "amount": "100.00"
}

Or push $50:

{
   "accounts": {
         "sourceAccountID": "zxc4123412341234123412",
         "destinationAccountID": "1234123412341234abc412"
    },
    "referenceID": "zxcv456",
    "type": "push",
    "amount": "50.00"
}

Complementary APIs

All our other APIs are built to support our Unified API. Here is a quick preview:

  • Card APIs for AVS, check eligibility for push/pull, retrieve BIN attributes
  • Bank APIs to retrieve the attributes of a bank such as RTP eligibility.
  • Account APIs to store and manage cards with TabaPay. The output of this API is a TabaPay Token (account ID) that can be used in lieu of a payment instrument in our unified API
  • Transaction APIs that corresponds to our Unified API
  • 3D Secure APIs that allows you to perform 3DS. For a full guide, click here
  • FX Rate APIs that allows you to retrieve real-time FX Rates from the card networks to be used in tandem with an international push or pull transaction
  • Sub-client APIs that allow you to automatically onboard sub-clients, set their fees, configuration, etc.

Integrating with TabaPay

TabaPay Web Service (API) is organized around REST. It uses standard HTTPS response codes, authentication, and verbs, and requests and responses are formatted using standard JSON.

Steps to integrate with TabaPay

1. Talk to Us - Email [email protected] to get started with access to our APIs. Our APIs are not publicly available

We will require your IP address(es) to be whitelisted in order to provide access to our secure sandbox environment.

2. Authentication - TabaPay API uses API keys to authenticate requests.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas.

3. Headers - All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

HTTP Headers must be formatted as follows:
Authorization: Bearer
Content-type: application/json

4. IP Whitelisting - Before you begin, please ensure you provide us with the IP Addresses you want us to whitelist. Our Firewalls will block all non-whitelisted IP Addresses.

What about PCI compliance?

Please look at our PCI "How to..." guide for all of the information your need regarding PCI compliance.

Configurations for Value Added Services

Before you proceed with your launch plan, please email [email protected] to ensure you have configured value added services required for your business case. Whether it is enabling 3DS or Apple Pay, Google Pay, or ensuring you have turned ON TabaPay Shield Controls to eliminate fraud, L2 and L3 interchange benefits, it will be important for you to let us know so we can enable them for you.

👍

Configurations can be on your side or ours

In order to fully ensure all your features are enabled for your business case, various configurations on our side or yours have to be set. Please let us know via [email protected] in case you need any help.

API Formatting Rules

Refer Data for detailed formatting rules.

❗️

Please follow formatting rules

To avoid unnecessary API errors, please refer to our desired formatting rules

TabaPay APIs can accept any UTF-8 character; however, to be safe for other processes that may be using this data, we recommend the use of only the Base64 URL-Safe Character Set. We will also explicitly restrict the use of these characters:

, Comma (used in csv files)
" Double Quotes (used in csv files)
~. Tilde
^. Caret
| Pipe
We do recommend the use of only the Base64 URL-Safe Character Set.

Network codes

When using the Create Transaction API, you will receive a network code in your response. In the example below, a networkRCcode of 00means the transaction was approved or completed successfully. Note that not all networks may return this Network Response Code.

{
  "SC": 200,
  "EC": "0",
  "transactionID": "TabaPay_TransactionID_",
  "network": "Visa",
  "networkRC": "00",
  "status": "COMPLETED",
  "approvalCode": "000000"
}

For more potential response codes, please visit our guides:

  1. ISO Response Codes
  2. Accel Response Codes
  3. RTP Response Codes