Payments Migration

Numeral now enables customers to migrate and manage historical payment operations, ensuring a risk-free and seamless transition from their previous system

Context
Some of our customers start using Numeral to replace an existing payment infrastructure, meaning they have payments already recorded and managed. They’re wary of losing their old data, and even after switching to Numeral, they may continue receiving R transactions linked to past payments — but they’re unable to manage them without transferring the related data.

The feature
This new feature decreases the risk and complexity of migration projects by giving customers full visibility of their payment history and control over R transactions — even long after their previous system has been switched off.

As of now, the following 4 objects can be imported in Numeral:

• Payment orders: outgoing SCT, SCT Instant, SDD, and Bacs payments

• Incoming payments: incoming SCT, SCT Instant, SDD, and Bacs payments

• Return requests: recalls and originator requests for recalls by the originator (RFRO)

• Direct debit mandates: SEPA and Bacs direct debit mandates

  How it works
  Customers use Numeral’s templates to share CSV files containing the payment operations they want to migrate. Numeral currently offers 4 CSV file templates used to import payment orders, incoming payments, return requests and direct debit mandates.

We then populate the staging or sandbox environment for validation, and once approved, move the data to the production environment. No events are triggered — all historical data are faithfully recreated as-is, ensuring a clean and consistent migration.

Since R transactions can be received up to 13 months after the original payment, we ensure the migration covers at least that period.

Next steps
To learn more about the supported use cases and access the CSV templates to share with our product team, click here to read our Guide on How to Migrate your payment history to Numeral.