Overview

This document covers the functionalities and constraints of the Tokenized Card-on-File (TCoF)enablement for the Paynetics Acquiring product. It provides comprehensive information on how to integrate and operate it.

Product Description

Overview: This document provides a comprehensive guide for integrating Tokenized Card-on-File (TCoF) into the Paynetics Acquiring product. It covers functional details, integration requirements, transaction flows, and compliance with Visa mandates.

TCoF enables merchants to store customer card details securely for future transactions, with proper indicators to comply with Visa regulations.

Scope:

• Tokenized Card-on-File (TCoF) with Visa

• Secure Customer Authentication (SCA) compliance.

Out of Scope:

• Non-card-based digital wallets.

• PayPal or alternative e-wallet services.

Visa Tokenized Card-on-File (TCoF) allows merchants, PSPs and commerce platforms to tokenize PANs (Primary Account Numbers) entered by consumers or existing PANs held on file, replacing each PAN with a unique token (subject to issuer participation). These tokens can be used for e‑commerce and in-app transactions in the same way as PANs.

Currency and country coverage

The supported settlement currencies are EUR, GBP, and BGN. Important note is that the currencies that you will choose. The processing currencies are all currencies supported by Paynetics.

The supported countries are EU27, Iceland, Liechtenstein, Norway, or the UK.

Merchant Onboarding

There are no additional onboarding requirements for merchants using SCOF and Network Tokenization beyond the standard Paynetics onboarding process:

1. Automated Merchant Onboarding – Merchants can onboard through the Paynetics onboarding API.

2. Manual Onboarding – For cases where automation is not feasible, manual setup is required. Merchants need to submit onboarding documents via a secure shared portal and notify Paynetics at underwriting@paynetics.digital.

Once approved, merchants can start accepting TCoFand Tokenized payments.

Note: Paynetics does not manage cardholder TCoF enrollment; this is handled by Visa.

Onboarding via API

The recommended way of onboarding merchants is via API. For more information on the process

During application processing, we may contact you or the merchant to request more information.

Manual onboarding

To onboard merchants manually we will provide you with dedicated access to a secure shared storage where you must upload the filled in merchant application form together with the required documents. You must notify us by email to underwriting@paynetics.digital for your from to be reviewed.

Please be aware that manual onboarding has limited capacity, and it’s not recommended. Paynetics can only process 10-15 applications a month under the manual flow.

Fees set-up

The fees setup follows the current procedure with no specifics.

Payouts

The payouts follow the current procedure with no specifics.

Reporting and reconciliation

You can track all transactions via API real-time. In the end of the day, we will be sending you a reconciliation report with all transactions from the previous day via SFTP.

Profit share

We will be adding your share of the profit in the acquiring monthly commission report file. The file is sent up to the 10^th day of the moth. Upon your approval of the commission file, you must send us an invoice. The invoice will be duly paid as per our contractual agreement terms.

Technical Integration

One we have signed agreement for acquiring services you will be provided with access to your Sandbox instance where you can carry on the integration. Once you have integrated the solution, you will run a set of tests validated by Paynetics and you will be ready to move to production. Migrating to production is a matter of receiving and configuring a new API key and changing the API root path.

Execute Click to Pay payment

The execute a use the POST /v1/purchase or POST/v1/pre-authorization endpoint. No difference in the request parameters sent in the Purchase and Pre-authorization. The Pre-authorization request must always be followed up by capture request POST/v1/capture, otherwise the transaction will not be cleared.

Specific Request Parameters 

Request:

Example Request

{
    "reference": "dsds",
    "merchant": "7cb0db766c86cdda3939871adfece952",
    "amount": 1,
    "currency": "EUR",
    "card_number": "4111111111111111",
    "card_expiration_month": "11",
    "card_expiration_year": "25",
    "pos_entry_mode": "10",
    "recurring_type": "3",
    "cardholder_name": "XXXXXX",
    "wallet_payment": {
        "digital_payment_cryptogram": "stringstringstringstringstri",
    }
}

Response:

Example Response

{
  "code": 0,
  "data": {
    "card_number": "411111XXXXXX1111",
    "processing_code": "000000",
    "amount": 1,
    "stan": "180801",
    "local_time": "145916",
    "local_date": "0813",
    "auth_code": "361156",
    "response_code": "00",
    "card_acceptor_terminal_id": "16P17777",
    "card_acceptor_identification_code": "1602071111",
    "currency": "978",
    "transaction": "9310bc2b-171b-47f7-8d2b-d97cdfa546d1",
    "cvv_status": " 06",
    "ccti_id": "80",
    "transaction_stamp": "0000007761232611201A",
    "card": "39da5b38-15f3-4371-8a9b-09f138437b4e",
    "original_network_response_code": "00"
  }
}

3D secured transactions

Mastercard: Required for CIT; Optional for MIT.

3D Secure Request Parameters 

Request:

{
    "reference": "dsds",
    "merchant": "7cb0db766c86cdda3939871adfece952",
    "amount": 1,
    "currency": "EUR",
    "card_number": "4111111111111111",
    "card_expiration_month": "11",
    "card_expiration_year": "25",
    "pos_entry_mode": "10",
    "recurring_type": "3",
    "cardholder_name": "XXXXXX",
    "cavv": "AJkCCReZIncEQFcQBZkiAAAAAAA=",
    "eci": "05",
    "version": 2,
    "directory_transaction_id": "7b03c772-dba0-4818-872e-849d63a5a659",
    "wallet_payment": {
        "digital_payment_cryptogram": " stringstringstringstringstri",
        "remote_commerce_acceptor_identifier": "string"
    }
}

Response:

Example Response

{
  "code": 0,
  "data": {
    "card_number": "411111XXXXXX1111",
    "processing_code": "000000",
    "amount": 1,
    "stan": "180801",
    "local_time": "145916",
    "local_date": "0813",
    "auth_code": "361156",
    "response_code": "00",
    "card_acceptor_terminal_id": "16P17777",
    "card_acceptor_identification_code": "1602071111",
    "currency": "978",
    "transaction": "9310bc2b-171b-47f7-8d2b-d97cdfa546d1",
    "cvv_status": "06",
    "ccti_id": "80",
    "transaction_stamp": "0000007761232611201A",
    "card": "39da5b38-15f3-4371-8a9b-09f138437b4e",
    "original_network_response_code": "00"
  }
}

Note: The integration guide is applicable to all merchants integrated with Paynetics Acquiring API. The guide is not applicable to merchants integrated with ACI Gateway.