Importing Direct Debit mandates

In certain cases, users may have previously agreed to a payment mandate that gave consent to process a recurring payment using the user's bank details. Using the Workbook Converter, staff can import existing gateway mandates in order to take payments using the formerly agreed upon payment method.

In This Article 

To get started with gateway data migration, review the following sections regarding Global Payments and Stripe:

Global Payments

The process for importing mandates with Global Payments is as follows:

1. Contacting your existing gateway

Contact your current gateway provider to notify them of the planned migration.

2. Gateway Onboarding

See Global Payments: Getting Started Guide for full details.

3. Contact ASI

In order to be put in contact with the appropriate Global Payments analyst, please email paycentral@imis.com.

4. Retrieve required details from Global Payments

Staff will receive information regarding tokens and existing enrollments that are needed during the Workbook Converter import process.

Stripe

The process for importing mandates with Stripe is as follows:

1. Contacting your existing gateway

Contact your current gateway provider to notify them of the planned migration.

2. Gateway Onboarding

You must create a Stripe Connect account and complete onboarding before continuing with the rest of the process. See Stripe: Getting Started Guide for full details.

3. Submit your BACs Data Migration Request

You will need to submit a Data Migration request to Stripe to initiate the process. See Import Bacs data to Stripe for full details.

4. Retrieve required details from Stripe

Staff will receive the following information from Stripe:

  1. old_id – The unique customer ID field from prior system
  2. source_old_id – The unique payment method ID field from prior system
  3. created_customer – The new customer ID created in Stripe
  4. source_new_id – The new payment method id created in Stripe
  5. mandate_id
  6. mandate_reference

Importing with Workbook converter

Once you have successfully onboarded and collected the necessary information, you must import the data. Review Importing AutoPay data into the Workbook Converter for full steps.

Additional information

  • If migrating to Stripe, the end user receives an email from Stripe as well, informing them that their previously agreed upon payment details will be used by your organization for their donation or membership. This email also contains a link to cancel or deny the mandate from being used if the user so chooses.
  • It is recommended to exercise caution when navigating the migration import process to avoid disruptions with current AutoPay enrollments and payments.
  • The migration import process for both gateways may take anywhere from 2-4 weeks, but may be longer if additional complexities or issues arise. Make sure to plan for this transition time accordingly.