Specific considerations for data migrations

The following sections provide additional information only and do not cover the complete set of required data for collecting payments through a given payment processor.

   For a complete overview of required data, please refer to our data quality rules Google Sheet.

Adyen migrations

Target ObjectTarget FieldPSP dataComments
Mandateadph__Token__cTokenSpecific field on Mandate for Adyen tokens

Axerve migrations

Target ObjectTarget FieldPSP dataComments
Mandategffd__Bank_Transaction_Id__cBank Transaction IdSpecific field for Axerve
Mandategffd__MOTO__cMOTO (true /false)Specific field for Axerve
Mandategffd__Eligible_for_Token_Refresh__cEligible for Token Refresh (true /false)Specific field for Axerve
Payment Profilegffd__Target_To_Refresh_Token__cTarget to Refresh TokenSpecific field for Axerve

Buckaroo

For SEPA Direct Debit migrations, special attention is needed in the area of mandate reference handling. There are two ways to manage the Buckaroo prefix.

Target ObjectTarget FieldPSP dataComments
Mandatecpm__Custom_Reference__cPrefix + MandateIf the entire Buckaroo mandate reference, including prefix, is migrated as one value, the value should be added to this field.
Mandatecpm__Prefix__cPrefixIf the prefix is not included in migrated mandate references, add the prefix to this field.

Checkout.com migrations

Target ObjectTarget FieldPSP dataComments
Payment Profileccph__Fingerprint__cFingerprintSpecific field for Checkout.com

GoCardless migrations

Target ObjectTarget FieldPSP dataComments
Contactgcf__GoCardless_Customer_Id__cGoCardless Customer IdNeeded only if you use the Manual Direct Debit component for existing customers
Mandatecpm__Custom_Reference__cGoCardless Mandate IdExample: MD000EHA3S6AT7
Payment ProfileN/AN/AIf you want to use custom notifications with GoCardless Pro, you need to create payment profiles with a Bank Name to get all the required data into Salesforce.

Mollie migrations

Target ObjectTarget FieldPSP dataComments
Contactmoph__Mollie_Customer_Id__cMollie Customer IdSpecific field for Mollie
Mandatecpm__Reference__cMollie Mandate idExample: mdt_4tCvx2TJEz

PayPal migrations

Target ObjectTarget FieldPSP dataComments
Mandatecpm__Custom_Reference__cPayerBilling Agreement ID with PayPal, e.g. B-8G591046VR212925B. This overwrites the Mandate Id.

Redsys migrations

Target ObjectTarget FieldPSP dataComments
Mandatecpm__Reference__cDS_MERCHANT_IDENTIFIERe.g. 01903f9b923895767228066924f23b5892e88fdb

Saferpay migrations

Target ObjectTarget FieldPSP dataComments
Mandatesford__Is_Alias__cCredit card referenceIs Alias must be true for migrated recurring credit card transactions to allow further collections
Mandatecpm__Reference__c(Card) AliasThe authorization token from Saferpay for a recurring payment (not set up through FinDock).

Access PaySuite (SmartDebit) migrations

Target ObjectTarget FieldPSP dataComments
Mandatecpm__Custom_Reference__cPayerBacs reference with SmartDebit, e.g. UCOSHX7. This overwrites the Mandate Id.

Stripe migrations

Target ObjectTarget FieldPSP dataComments
Contactphstr__Stripe_Customer_Id__cStripe Customer IdSpecific field for Stripe, e.g. cus_1234absced
Mandatecpm__Reference__cStripe Customer IdSpecific field for Stripe, e.g. cus_1234absced
Mandatephstr__Payment_Method_Id__cStripe Payment Method IdSpecific field for Stripe, e.g. pm_123sdf3dsf3 or card_123w213sf
Payment Profilephstr__Fingerprint__cFingerprintSpecific field for Stripe

Further Stripe migration requirements

If you are going to use MOTO payments, make sure you migrate the data needed for credit card re-use.

If you are moving SEPA Direct Debit payments to FinDock, you need to get the SEPA mandate Stripe Payment Method Id into FinDock. If the field is not included in reports, it can be queried via the Stripe API.

Worldpay

Target ObjectTarget FieldPSP dataComments
Mandatecpm__External_Customer_Id__cWorldpay Shopper IdSpecific field for PSP payer Id

Vipps

Target ObjectTarget FieldPSP dataComments
Mandatecpm__Custom_Reference__cAgreement IDE.g. agr_123456

FinDock as processor

Autogiro migrations

Before you start migrating existing Autogiro recurring payments to FinDock, please first assess the types of payment collection in use. Autogiro supports two: automatic recurring collection based on a single payment order to initiate collection, and recurring collection based on recurring payment collection instructions. FinDock only supports the latter.

If you have any automatic collection in use, these orders need to be cancelled as part of the FinDock migration. We recommend proceeding in batches, cancelling a small set of orders, migrating those, and restarting collection through FinDock. Once your process is confirmed to work, you should gradually move remaining automated orders to FinDock, for instance, in batches of increasing size.

When it comes to migrating Autogiro data, in addition to the general migration guidance noted above, special handling of custom mandate Id values may be needed. Payer numbers (mandate Ids) in FinDock must be filled with leading zeros to match the expected 16-digit length. If, for example, the payer’s Bankgiro number is migrated and used for the mandate Id, the value needs to be with leading zeroes.

Also, note that you need to use the BBAN record type and page layout for Payment Profile for Autogiro payer bank details. Start by selecting Sweden from the country picklist. This will show you which fields should be populated for Swedish banks accounts.

AvtaleGiro migrations

For mapping details, please see Migrating AvtaleGiro Agreements

Bacs migrations

Target ObjectTarget FieldBacs dataComments
Mandatecpm__Date_Signed__cDateFinDock automatically populates this for new mandates

SEPA migrations

Target ObjectTarget FieldSEPA dataComments
Mandatecpm__Last_Used__cDateNeeds to be populated for recurring, otherwise the next installment generated by FinDock will be first automatically.
Mandatecpm__Prefix__cTextOnly populate if you have a prefix, and no Custom Reference value is used on the record.
Payment Profile(address fields)N/AIf you have UK payers for SEPA, you need to populate the address fields: Street, Housename Or Number, Zipcode, City, and Country.

Was this page helpful?