This page is no longer supported. Please refer to the current guide for up-to-date information.

Solidgate allows you to import your existing customer data into your Solidgate account, ensuring a seamless transition. This includes securely migrating payment information from your current payment provider to Solidgate. As a result, you can continue charging your customers without any interruptions or the need for them to provide their payment details again.

TABLE OF CONTENTS

Required parameters for card data migration

To proceed with card data migration Solidgate would need to receive such information:

  • Full card number
  • Card Expiration Date
  • Cardholder Name.
  • Customer Email.
  • Card_scheme_transaction_id (parameter is obligatory to be able to process reccurring payments as Card on File)
  • Additional obligatory data in case of local processing.


Also, it is possible to add to the file data like customer_account_id from the previous provider, in case such data will help with matching created tokens with the customers.


As a result, you will receive the file from Solidgate with such data:

  • Customer Email.
  • Solidgate's Card Token.
  • Masked Card Number.
  • Passed Additional Parameters.


The functionality of payment data migration supports various scenarios, as outlined below:


Merchant store user's card details:

If a merchant store card details and wish to transfer payments from another provider to Solidgate, it is possible to perform a charge without requiring the CVV. This can be done under the following conditions: 

  • When card details (PAN, expiration date) are stored in the merchant database, and the first payment with a CVV card was processed by another provider. To ensure a smooth transition and maintain a high conversion rate, the merchant must provide the parameter "scheme_transaction_id" with this method. The payment will be processed as Card on File (COF). 
  • If a merchant does not have a "scheme_transaction_id" it is still possible to process payments, but these will be categorized as MOTO (Mail Order Telephone Order), resulting in a lower conversion rate. 
  • If a merchant is making a payment using PAN and expiration date and process it as a Customer Initiated Payment (CIT), meaning the user is present during the payment, the "scheme_transaction_id" is not obligatory.


Card data stored with another acquirer:

If a merchant is processing payments through a different acquirer who stores card details, the merchant can securely transfer all the card data to Solidgate.


In return, a merchant will receive card tokens that enable the merchant to charge users or create subscriptions.


Please note that it is highly recommended to have "scheme_transaction_id" when transferring data from another acquirer, so the approval rate for transferred data and such transactions will be higher.


Data transfer process

To successfully complete the data transfer process, follow these four steps:


1. Complete your Solidgate integration if you haven't done so already.

2. Notify Solidgate that you are planning to transfer payment data

3. Request your current processor to transfer your data to Solidgate

4. Update your integration to finalize the migration.


Once you integrated Solidgate and prepared to process payments, please contact us so that we can securely assist you with the data transfer process.


After initiating the data transfer request with your previous processor, please inform Solidgate. 


The preferred way to import your customer payment details depends on the provider/acquirer. It can be done via SFTP server or in another secured way.


Once the process of data import is done, Solidgate will generate tokens, enabling you to process payments seamlessly. However, please note that subscriptions cannot be imported and will need to be recreated separately.


The time required for your previous processor to transfer the final data to Solidgate can range from a few days to several weeks. Therefore, it is essential to consider this transition period in your migration plan.


If any issues arise with the data we receive, we will communicate them to you and work with your previous processor to rectify them.


Once Solidgate imports your data, the platform will generate card tokens. We will provide you with a file containing the card tokens and user information (e.g., email) for matching purposes from your end.


Working with subscriptions:

If you currently utilize subscriptions or a similar recurring billing system with your current processor, transitioning to Solidgate requires two additional steps:


1. Create subscription products within your Solidgate account, maintaining the same pricing and billing intervals as your current processor.

2. After receiving card tokens, recreate the subscription for each customer in Solidgate using the provided information. Unfortunately, we do not have data regarding subscription start/end dates or pricing, so this step must be performed by you.


By following these instructions, you can smoothly migrate your customer data and subscriptions to Solidgate, ensuring uninterrupted payment processing.