FRTech, Ingenico/ Worldline have apprised us that , for Amex, the currencies below were removed from our configuration as they’re no longer supported. I would like to recover this small set of recurring donors by porting them to Adyen and resuming the recurring billing there. This is also a discovery opportunity to trial a migration before we seek to migrate all of the 165k recurring donors from Ingenico to Adyen which is on the roadmap and is a much more sensitive endeavor.
Here is the migration process from Adyen. As you will see there is an action on us to ensure we can bill to a different provider for these migrated tokens. Can we support that the recurring charge be performed at two different processors and what of the shopper reference how will we handle that?
I have sent the format to Ingenico for their reaction as to whether they can align with the format and will advise further here. In the meantime, if they can, can we support this migration?
From Adyen:
Before we begin the import process, you'll want to ensure the following steps have been taken:
Adjust your technical processes so tokenization and recurring charge processes can be performed at two different payment service providers (PSP).
Decide on an internal shopper reference to use as the Adyen shopperReference.
Adyen uses a reference to the shopper rather than the payment details for tokenization.
Contact your current PSP and check if you can use the internal shopper reference you have chosen. If not, choose one of their IDs to link with your Adyen shopperReference.
Check their preferred method of transferring files to Adyen.
If they can export the data in the required format, you can contact us to begin the process. We will create a custom PGP key which will speed up your card import process. For more information on required formats, see recurring payments details and referral lists.
Otherwise, ask your old provider to encrypt the file format with the Adyen PGP key so that Adyen can perform custom manipulation of the file format afterwards.
The files containing the data to be imported should be formatted as follows:
Create a file in CSV (Comma Separated Values) format as per RFC 4180, in accordance with the following requirements:
The first line contains the names of the fields. You do not have to use all field names and you do not have to use them in the same order as listed on this page.
Each subsequent line contains the fields for a single recurring contract. In other words: Each recurring contract is on a separate line.
If a field doesn't apply to the recurring contract that the line describes, specifying a value is skipped.
Field names and values are case-sensitive.
Multi-line fields are not allowed.
The maximum file length is 1,000,000 lines.
Save the file in UTF-8 format (to support non-western characters).
Encrypt the file using the PGP public key provided to you by either our Support Team, or your Adyen contact.
For more information, see our PGP encryption documentation.
Send the file to Adyen.
You can find an example input file, as well as a list of the input file fields, in our "Import payment details for recurring payments" documentation. For a general overview of the import process, you can look over our "Import data from another payment provider" documentation.
