As part of our ongoing support for the Verification of Payee (VOP) rollout under the Instant Payments Regulation, Numeral users can now access a dedicated VOP sandbox environment.

This sandbox is designed to help financial institutions test their VOP implementation and get ready for the October 5, 2025 deadline.

What’s new

You can now use the Numeral VOP Routing and Verification Mechanism (RVM) sandbox to:

• Simulate sending and receiving VOP requests
• Test the matching algorithm against your own account and request data
• Gain hands-on experience with VOP request / response flows in a controlled environment

This provides a secure and EPC-compliant way to validate your setup before going live.

How to get access

Request access through our dedicated form: Access our VOP sandbox

Ressources

• For more information on our VOP solution, visit the VOP documentation
• For more information on VOP, check out our Guide to Verification Of Payee

Numeral now enables customers to migrate payments from their existing system to Numeral, ensuring a risk-free and seamless transition.

Some of our customers replace their existing system with Numeral and need to migrate payments to Numeral to be able to manage R transactions linked to payment send or received in their previous system.

The following 4 objects can currently 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

To learn more about payments migration, read our Migrating payments to Numeral guide.

You can now quickly duplicate an existing payment order in the dashboard:

1. Click on the payment order to duplicate
2. Click on Actions > Duplicate
3. Update attributes of the new payment, if needed
4. Click on Create payment order

We are excited to announce the release of payment approval workflows, bringing enhanced control and security to your payment operations.

What's new:

• Custom approval rules: configure approval workflows based on payment amount thresholds, connected accounts, recipient accounts, and user roles and permissions
• No self-approval option: prevent users from approving their own payment orders
• Full audit trail: Track all approval actions and decisions

Payment approval workflows is available today. Check out our documentation to learn more about implementing secure payment controls.

When adding a new webhook, you can now subscribe to specific events. For example, you can decide to subscribe only events related to incoming_payment.

Numeral webhooks are now signed using HTTP message signatures and a standard “signature base” approach. Read more here.

SEPA participants must be able to receive claims and inquiries on SCT payments. It just got easier to manage SEPA claims and inquiries with Numeral, with:

1. A new Claim object for incoming and outgoing claims non-receipt and claims for value date correction. Claims will automatically be created when received from other SEPA participants. Sending claims is also supported in beta with select SEPA sponsor banks. Contact us to learn more
2. The existing Inquiry object now supports inquiries related to claim non-receipt and claim for value date correction, in addition to inquiries on recalls / RRO. Sending inquiries is also available in beta with select SEPA sponsor banks

Claims and inquiries are available in the Numeral dashboard in the Investigations section of the main navigation bar.

At Numeral, protecting your accounts and payments is our top priority. To enhance security, we are introducing new measures to safeguard your data against potential threats:

1. Effective today: stronger password requirements

All new passwords must meet stricter security standards, including minimum length and complexity.

2. Effective March 3rd, 2025: mandatory password change

All users will be required to update their passwords to meet the new criteria.

3. Effective March 3rd, 2025: mandatory multi-factor authentication

MFA will become mandatory for all accounts. All users will need to use a one-time passcode (OTP) in addition to their password to log in.

Lear more in Multi-factor authentication.

You can now create roles tailored to your organisation’s needs by assigning specific permissions. This gives you full control to define who can access and manage different features.

Learn more in our guide.