You can replace a cardholder's Primary Account Number (PAN) with a secure, network-issued token that can be used to process payments.

TabaPay supports processing of both device and ecommerce/Card on File (COF) network tokens passed from third party providers. Submit the token, ECI, and TAVV cryptogram directly through the Create Transaction API with no decryption or additional processing required on your end.

Unlike raw card data, network tokens are bound to a specific device or merchant and include a cryptogram that changes with every transaction, which reduces fraud exposure.

How It Works

Prerequisites

When receiving a network token payload from a token service provider, such as Cybersource, or directly from Visa or Mastercard, the payload will include:

• Token (replaces the PAN)
• Expiration date
• ECI (Electronic Commerce Indicator)
• TAVV (Token Authentication Verification Value) / Cryptogram

1. Create Transaction

Submit the token payload to TabaPay using the Create Transaction API . Use the mobilePay object to pass the token, ECI, and cryptogram (TAVV) for processing.

Request

For request body parameter field descriptions, refer to Create Transaction API.

Note: The following transactionID in the request is a non-TabaPay Transaction Identifier in Hex format.

{
    "accounts": {
        "sourceAccount": {
            "card": {
                "mobilePay": {
                    "accountNumber": "4111111111111111",
                    "expirationDate": "202703",
                    "cryptogram": "BwABApFSYyd4AAAAAAAaaaaaaaaa",
                    "transactionID": "A29290E6370FBDC55A6CFFD1B63B325E4B32A1CE758F8AA9CCC7A421B3891814",
                    "eciIndicator": "5",
                    "network": "Visa",
                    "type": "Debit"
                }
            },
            "owner": {
                "name": {
                    "first": "Test",
                    "last": "Name"
                }
            }
        },
        "destinationAccountID": "{{settlementAccountID}}"
    },
    "referenceID": "1kdev0730a25",
    "type": "pull",
    "amount": "1.00"
}

Response

{
    "SC": 200,
    "EC": "0",
    "transactionID": "ALo_P5REQUNGd4Z5qPUuiQ",
    "network": "Visa",
    "networkRC": "00",
    "networkID": "521217131007",
    "status": "COMPLETED",
    "approvalCode": "131007",
    "additional": {
        "par": "V0010013022073812195104907179"
    },
    "card": {
        "last4": "1111",
        "expirationDate": "202708",
        "nameFI": "Bank TabaPay"
    }
}

Recommended Data to Capture

Where available, capture the following data from your token service provider to enhance analytics and improve the customer experience:

• Payment Account Reference (PAR): Use as a non-financial identifier for the underlying PAN across all analytics, controls, and card behavior tracking.
• Last 4: Use for customer identification and receipt purposes.
• Card Art: Use issuer-provided metadata including the card art URL, dimensions, and orientation for use in receipts, messages, and email communications.