Migration

When migrating from one PSP (Payment Service Provider) to another, it is essential to plan the migration process carefully to avoid service interruptions. If you have active subscriptions or stored cards that need to remain valid after switching providers, a formal migration is required.

What to do as a Merchant

To initiate a migration, you as the merchant must contact your current provider (old PSP) and request that they export your stored cards and subscription details in a format suitable for transfer to ePay.

We have often experienced delays when PSPs handle export requests. It is therefore strongly recommended that you contact your current provider well in advance and schedule the export as early as possible to avoid impacting your migration timeline.

Step-by-step guide

Plan the migration date
- Coordinate with ePay to agree on a preferred date for the export/import process.
- Ensure your ePay account is fully configured with any necessary acquirer agreements.
- Ensure you have tested your setup at ePay before migrating to avoid downtime.
Contact your current provider
- Submit an export request including the following information:
  - Your new payment provider: ePay Payment Solutions
  - A link to our migration guide and public encryption key: https://docs.epay.eu/get-started/migration
  - Contact details for ePay:
    - Primary Contact: thomas@epay.dk (CTO)
    - CC: niki@epay.dk (Tech Lead)
Once your request has been sent, your current provider will contact ePay to plan the data handover.
ePay will contact you once the technical plan has been agreed upon between the two PSPs to keep you updated on progress.
After the import is completed, your data will be available through the ePay APIs, where you can verify or fetch your stored card and subscription data.

Email request template

Below is a ready‑to‑use email template that you can copy, fill out, and send to your current provider.

Subject: Export Request – Migration to ePay Payment Solutions

Dear [Provider name or contact],

We are planning to migrate our stored card and subscription data to our new PSP, **ePay Payment Solutions**.

Please initiate the export and coordinate the secure data transfer directly with ePay using the contact details below:

New Provider: ePay Payment Solutions
Migration Guide and Encryption Information: https://docs.epay.eu/get-started/migration#what-to-do-as-a-psp
Primary Contact: thomas@epay.dk (CTO)
CC: niki@epay.dk (Tech Lead)

We would appreciate it if you could confirm receipt of this request and provide an estimated timeline for the export to ensure a smooth transition.

Best regards,
[Your name]

How to link subscriptions from your old provider to ePay

Once your subscriptions have been imported into ePay, they become immediately available in both the back office interface and through our API.

When ePay receives your subscription data, each record includes the old provider’s subscription reference. This value will populate the ePay field reference in your imported subscriptions.

This allows you to correlate subscriptions in your own system by linking:

Old PSP subscription identifier → ePay field reference
ePay subscription identifier (new) → ePay field id

For implementation details, see our API documentation.

What to do as a PSP

If you have received an export request from a merchant migrating to ePay, please reach out to our team to coordinate the transfer.

ePay Contacts

Type	Email	Role
Primary Contact	thomas@epay.dk	CTO
CC	niki@epay.dk	Tech Lead

Before transmitting any card data, please ensure the data is encrypted with ePay’s public PGP key. You can verify ePay’s PCI DSS compliance below.

What ePay requires

To complete a card or subscription migration, ePay requires the following data fields for each record:

Field	Description
PAN	The full primary account number (card number).
Expiry	Expiration year and month of the card.
Trace Id	The original authorization or trace ID, required to link MIT transactions to the initial CIT transaction.
Reference	The subscription or card reference from the old PSP. This enables the merchant to link data post-migration.
Customer Id	Merchant-defined customer identifier (if available).

Attestation of Compliance (AOC)

Download ePay PCI-DSS Attestation of Compliance (AOC)

Public PGP Key

When sending card data to ePay during migration, you must encrypt the data using ePay’s public PGP key to ensure data confidentiality and compliance with PCI DSS requirements.

What to do as a Merchant​

Step-by-step guide​

Email request template​

How to link subscriptions from your old provider to ePay​

What to do as a PSP​

ePay Contacts​

What ePay requires​

Attestation of Compliance (AOC)​

Public PGP Key​