Numeral enables its customers to migrate and manage their historical payment operations, giving them full visibility of their payment history and control over R transactions.

Process

Numeral offers 4 CSV file templates used to import payment orders, incoming payments, return requests, and direct debit mandates. The remaining of this guide explains how to populate these files.

Once populated and received, Numeral will import, test, and validate data in a test environment before repeating the import into a production environment

Use cases supported

CSV templates

ℹ️

Import CSV templates can be downloaded here.

• Templates contain mandatory and optional columns. See the full description of each columns for import type below
• Each entry must contain an id column filled with a unique internal ID (ideally a UUID v4, but it could also be a custom format). Return requests will be imported after payment orders and incoming payments, as their related_payment_id column must reference the id column of payment orders or incoming payments previously imported
• Files can contain up to 100,000 entries each
• CSV separator used is ";". Make sure to escape this character or encapsulate all strings that could include this character with double quotes

Payment orders

Incoming payments

Return requests

ℹ️

Relationships between return requests and payment orders are preserved via related_payment_id andrelated_payment_type fields.

Direct debit mandates