We understand migrating your customers to a new payments platform is time consuming. Your customers have to ‘opt-in’ and sign new mandates.


To make the above process much easier for you and your customers, Zomentum Payments offers Bulk mandate migration functionality. Using this Zomentum will migrate the mandates from your existing payment provider to Zomentum Payments.


Supported Regions & Payment Methods

United States (US):

  • Credit/Debit Cards
  • ACH Direct Debit

United Kingdom (UK):

  • Credit/Debit Cards


Here is how it works:

  1. Email support@zomentum.com for an encryption key 
  2. Provide the encryption key to your existing payment provider and request them to encrypt the data w.r.t mandates in a csv file (format as per RFC 4180)
  3. Share the csv file with the Zomentum team at support@zomentum.com


Input file format

The files containing the data to be imported should be formatted as follows:

  1. 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.
  2. Save the file in UTF-8 format (to support non-western characters)


The following is an example input file with four recurring contracts:

MerchantAccount,ShopperEmail,ShopperReference,RecurringContract,EchoData,OwnerName,ExpiryMonth,ExpiryYear,ExpiryYYMM,ExpiryMMYY,ExpiryMMYYYY,ExpiryYYYYMM,CardNumber,Iban,CountryCode,BankLocation,BankName,BankLocationId,BankAccountNumber,BillingAgreementId,PayerId,BillingStreet,BillingCity,BillingState,BillingPostalCode,BillingCountry
TestMerchant,mark1test@adyen.com,mark1,RECURRING,MasterCard Bijenkorf NL,D.N. Mater,8,2018,,,,,5100081112223332,,,,,,,,,,,,,
TestMerchant,mark30test@adyen.com,mark30,"RECURRING,ONECLICK,PAYOUT",,P.Pal,,,,,,,,,,,,,,B-2308952346426,AK5HCWWRUV2KL,,,,,
TestMerchant,mark75test@adyen.com,mark78,RECURRING,,B.Dalby,,,,,,,,NO6012341234561,NO,,,,,,,,,,,
TestMerchant,mark2test@adyen.com,mark2,RECURRING,,B.Dalby,,,,,,,,,US,,,121000358,123456789,,,123 Test Street,San Francisco,CA,94000,US


Input file fields

The fields for recurring contracts are:


FieldRequiredDescription
ShopperReferenceYesAn ID that refers uniquely to the shopper. For example, a customer ID in a shopping cart system. Minimum length: three characters.



Apart from the above fields, the CSV file can have fields for:

  1. Card Data
  2. ACH  


Card fields

When specifying card data, you need to provide:

  1. Card number.
  2. Expiry date: month and year of expiry. You can use either a combination of fields (ExpiryMonth and ExpiryYear), or a single field to specify both month and year: ExpiryMMYY, ExpiryMMYYYY, ExpiryYYMM or ExpiryYYYYMM.

Data
Required
Description
CardNumber   
YesThe card number.
Expiry date    
Yes

Either a single field or a combination of fields is required. Choose from the following fields.

  • ExpiryMMYY: The month and year of expiry, written as a 4-digit string. For example, 0618 for June 2018.
  • ExpiryMMYYYY:The month and year of expiry, written as a 6-digit string. For example, 062018 for June 2018.
  • ExpiryYYMM: The year and month of expiry, written as a 4-digit string. For example, 1806 for June 2018.
  • ExpiryYYYYMMThe year and month of expiry, written as a 6-digit string. For example, 201806 for June 2018.
  • ExpiryMonthThe month of expiry, written as a 1 or 2-digit string. For example, 6 or 06 for June. Use in combination with ExpiryYear.
  • ExpiryYearThe year of expiry, written as a 4-digit string. For example, 2018. Use this in combination with ExpiryMonth.

networkTxReference

(for Visa


YesThe Visa Transaction ID from the initial transaction where the shopper signed up for a series of Subscription or UnscheduledCardOnFile payments. 



ACH fields


FieldRequiredDescription
BankLocationIdYesThe ABA routing transit number of the account.
BankAccountNumberYesThe US bank account number from which the payment will be debited.
OwnerNameYesName on the bank account.
CountryCodeYesUS
BillingHouseNumberOrName    YesThe number or name of the house. You can omit this and include the data in BillingStreet.
BillingStreetYesThe street name.
BillingCityYesThe city name.
BillingStateOrProvinceYesA valid 2-character abbreviation for the state
BillingPostalCodeYesThe postal code.
BillingCountryYesUS