Getting Started

Token Authentication is a critical step in all pay-in and pay-out solutions offered by Gigadat. Token Authentication is used for all our transactions. These include ETI, RFM, IDP, ETO, RTO, ACH and FPL. This section will cover generating unique payment tokens for our services, and then using that token to initiate a transaction.

Base URL

Generating A Payment Token

There are several unique pieces of information that need to be stored in a transaction during a payment flow such as product lists, customer ID, etc. The Gigadat portal provides you with an endpoint in which you can generate a secure payment token containing all the information you will require for the conclusion of a transaction.

You can create a payment token by sending a POST request to https://interac.express-connect.com/api/payment-token/{campaignId}.

The body of the request should contain a valid JSON object with all mandatory fields that are specified per transaction type. This is an example of the raw JSON body that is expected with your POST request to /api/payment-token:

{
    "amount": "50",
    "currency": "CAD",
    "userId": "123",
    "name": "johndoe",
    "email": "johndoe@email.com",
    "mobile": "4031234567",
    "site": "my-site.com",
    "userIp": "xxx.xxx.xxx.xxx",
    "type": "CPI|ACH|ETO|RTO|KY1|KY2|KY3|KY4|FPL",
    "sandbox": "true|false"
}

Create A Transaction

All payment types can be created by sending a GET request to the following endpoint:

https://interac.express-connect.com/webflow?transactionId={uniqueId}&token={paymentToken}

Know Your Client(KYC) verifications can be initiated by sending a GET request to:

https://interac.express-connect.com/webflow/verify?token={paymentToken}

Available Payment Types

• CPI (Combined Pay-In)
• ETO (eTransfer Outbound)
• RTO (Real-Time Outbound)
• ACH (eCashout)
• KY1 (3-year Credit-file KYC)
• KY2 (ID Document Verification)
• KY3 (Dual-source credit and bank verification)
• KY4 (Bank verification)
• FPL (FastPlay)