This guide is intended for merchants currently operating with Fabrick’s Open Payments and looking to migrate to other PSPs (Payment Service Providers).
Its purpose is to provide clear guidance on file formats and data-sharing methods.

What is a card token?

A card token is a unique identifier that replaces the PAN (Primary Account Number)—the number printed on a payment card.
Tokenization enables transactions to be carried out without using the actual PAN, enhancing protection against fraud and data theft.

For more details, see the Fabrick article:
What is Tokenization and its key role in international payments

What are recurring payments?

Recurring payments are transactions made on a regular basis (e.g., monthly subscriptions, installments), without requiring the customer to re-enter card data each time.
In MIT (Merchant Initiated Transactions), the merchant initiates the payment autonomously, based on prior customer authentication.

See also the official Axerve documentation:
MIT Recurring Payments – Fabrick Docs Payment Orchestra

Migration objective

To provide all necessary data so the new PSP can continue managing existing recurring payments, allowing the merchant to maintain operational continuity and freedom of choice.

Sample files provided

File format

• CSV format with UTF-8 encoding

• All rows must contain the same number of columns

PayPal Token Migration

Sample header and row 1:

TOKENVALUE;CREATEDATE;DELETED;DELETEDATE;REFERENCEID;AGREEMENTDESC
PPPXOEXXXXX8CBO3;1/17/2017 9:04 AM;0;;B-0C311XXXXXX344154M;edicola#maxxxxxxino22@gmail.com

Field definitions:

• TOKENVALUE → PayPal token ID

• CREATEDATE → Token creation date

• DELETED → Binary value (0 or 1)

• DELETEDATE → Token deletion date, may be empty

• REFERENCEID → Transaction reference within the PayPal ecosystem

• AGREEMENTDESC → Textual description of the agreement between merchant and customer (often includes user references, e.g., email)

Card Token Migration

Sample header and row 1:

IDTOKEN;IDSHOP;TOKENVALUE;TOKENTYPE;CARDNUMBER;EXPIRYMONTH;EXPIRYYEAR;CREATEDATE;DELETED;DELETEDATE;WITHAUTHORIZATION;WITHCVV;THREEDLEVEL;ONLYMASKEDPAN;IDGROUP;LASTABUUPDATEDATE
325XX397;160817;52MUOMYXXXEY4375;STD;522694XXXXX74375;09;26;4/2/2022 7:41 AM;0;;1;1;2;0;1864;

Field definitions:

• IDTOKEN → Unique Fabrick token ID for the card

• IDSHOP → Fabrick store ID where the token was created

• TOKENVALUE → Actual token replacing the card PAN

• TOKENTYPE → Type of token

• CARDNUMBER → PAN (card number)

• EXPIRYMONTH → Expiration month (MM)

• EXPIRYYEAR → Expiration year (YY)

• CREATEDATE → In format YYYY-MM-DD HH:MM:SS

• DELETED → 1 or 0

• DELETEDATE → Deletion date in YYYY-MM-DD HH:MM:SS format

• WITHAUTHORIZATION → Binary value

• WITHCVV → Y or N

• THREEDLEVEL → 3DS authentication level

• ONLYMASKEDPAN → 1 or 0

• IDGROUP → Fabrick group ID (if the token is part of a group)

• LASTABUUPDATEDATE → Last update date from the Automatic Billing Updater (YYYY-MM-DD HH:MM:SS)

Recurring Transaction Chain Migration

Sample header and row 1:

ID;IDSHOP;IDTOKEN;AUTH_DATA;AUTH_METHOD;AUTH_TIMESTAMP;ACS_TRANS_ID;BANKTRANSACTIONID;GLOBALPAYID;XID;FIRST_PAYMENT_ID;GATEWAY_FIRST;IDTRANSACTION_FIRST;IDCREDITCARDTRANSACTION_FIRST;RECOVERY;CREATED_DATE;RECURRING_TYPE;LAST_NEXT_DATE
234345;160817;9856927;;;;;-100;0;;f01c4eec-xxxx-4f29-b9e2-ea458286648b;I;689047016;1340432970;0;10/6/2022 2:04 PM;01;

Field definitions:

• ID → Chain identifier within Fabrick

• IDSHOP → Fabrick store ID

• IDTOKEN → Token ID in Fabrick

• AUTH_DATA → Authentication data (optional)

• AUTH_METHOD → Authentication method (optional)

• AUTH_TIMESTAMP → Authentication timestamp (optional)

• ACS_TRANS_ID → 3DS transaction ID from the user's Access Control Server (bank)

• BANKTRANSACTIONID → Transaction ID tied to the store code

• GLOBALPAYID → Universally unique transaction ID in Fabrick

• XID → GUID-type unique chain value

• FIRST_PAYMENT_ID → ID of the first payment of the chain for that store code

• GATEWAY_FIRST → Initial transaction entry point

• IDTRANSACTION_FIRST → Unique transaction ID that generated the chain

• IDCREDITCARDTRANSACTION_FIRST → Similar to the previous, specific to credit card transactions

• RECOVERY → true/false/Y/N or empty

• CREATED_DATE → In format YYYY-MM-DD HH:MM:SS

• RECURRING_TYPE → 01 or 03

• LAST_NEXT_DATE → Date of last Merchant Initiated Transaction in the chain (optional)

Security and file delivery

The CSV file must be encrypted using the public key provided by the destination PSP, which will also supply the sFTP server address and credentials required for Fabrick to upload the files directly.

Connection details include:

• Server name

• Port

• Username

Expected timeline

Once the information outlined in the “Security and File Delivery” section is received, Fabrick will deliver the data to the new PSP as quickly as possible.
Depending on the volume and type of data to be exported, the process may take from a few days to several weeks.

Contacts

For assistance with data preparation or secure file setup, please contact the Fabrick technical support team.

Fabrick Open Payments Support Portal