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.

Customer accounts are leveraged in most payment operations. Manually managing them or passing them from third-party solutions for each task can be tedious and error prone.

With internal accounts, Numeral customers can store, manage and leverage their customer accounts directly in their payments platform.

This information can then be directly leveraged in the following workflows:

• Create a payment order (as originating account)
• Create a direct debit mandate (as originating account )
• Create an expected payment (as internal account replacing virtual account)
• Automatically link
  • Incoming payments with internal accounts
  • Transactions with “virtual” internal accounts
• Automatically process incoming instant payments in real-time
• In the future, automatically answer Verification Of Payee requests

Internal accounts are available for free for all customers.

Note that in addition to the launch of internal accounts, we are replacing the following objects:

• Counterparty becomes Account holder
• Counterparty account becomes External account
• Virtual account becomes Internal account with type = “virtual”

Also note that connected accountsare now accessible under “Settings” in the Numeral dashboard.

Learn more about this migration in the dedicated changelog, and find more information about internal accounts:

• API reference

Without the proper tools, it can be complex for payment operations teams to identify payment issues quickly, uncover potential optimisation for payment operations, and view long-term payment trends at a glance.

Numeral's new dashboard home gathers all the insights payment and finance teams need:

• Payment operations: Identify and solve payment issues as soon as they happen.
• Liquidity: Visualise and manage your liquidity over time and across banks
• Analytics: Uncover long-term payment trends and gather insights on repeated issues to optimise your payment operations

New widgets will be added in the future, including views on payment retries and account verifications.

The dashboard home is available for free to all customers that have access to the dashboard.

Numeral customers now can visualise in the dashboard, for each configured webhook, all the events sent to said webhook.

Using incorrect BICs can lead to payment failures, and end users providing the wrong BIC with their IBAN can indicate a fraud tentative.

With Bank code lookup, customers can easily retrieve the BIC associated with an IBAN to improve payment success rate and prevent potential fraud.

Bank code lookup is available via:

• An API endpoint, through which customers can submit an IBAN and obtain the corresponding BIC in response
• The dashboard when creating a payment order or an external account. Clicking on the “Lookup” button will automatically populate the Bank code field based on the provided Account number

Bank code lookup is available to all customers and currently supports IBANs of the countries listed here.

API endpoint

Dashboard users customers now can view the reconciliation rule used by the automated reconciliation engine to reconcile reconcile a payment or transaction.