Dashboard users can now view all files related to payments. This include payment initiation files, payment status reports, and R transactions.
Bulk actions have been expanded to creating internal accounts.
Learn more:
You can now retrieve audit trails via API.
Audit trails are returned as structured objects for actions initiated by API keys, dashboard users, or the Mambu Payments system.
- Each object represents an individual action and includes a fixed set of metadata.
- Users can list and filter audit trails using parameters such as date range, object ID, and sort order.
Learn more in our API reference.
Dashboard users can now customise table layouts, including showing, hiding, and reordering columns.
Dashboard users can now set customise fields and signature date when creating or updating direct debit mandates.
The dashboard now supports the full organization_identification
structure — as defined in ISO 20022 and EPC VOP specifications — for both internal and external accounts.
Users can now view and input multiple identifier types during account creation and editing, and see them across payment and counterparty views.
- Internal and external account forms now accept multiple organisation identifiers (e.g. SIREN, SIRET, DUNS, TAXID).
- Identifier types are mapped to the
organization_identification.others
structure. - Supported fields are displayed in account detail views.
- Identifiers are visible in counterparty panels across payment orders, incoming payments, expected payments, and captures.
legal_entity_identifier
remains supported as before.
Numeral’s bank simulator enables customers or connectivity providers to simulate real-world payment flows, either via the API or directly from the dashboard.
To perform these simulations, you can either use built-in scenarios or upload bank or CSM messages:
- Built-in scenarios are supported in both the API and the dashboard (through a dedicated Simulator screen) with Numeral’s mock bank Demo Bank
- Uploading bank or CSM messages is only available in the API and supports both Numeral’s mock bank Demo Bank and your own partner banks
The dashboard version of the bank simulator is available in sandbox. It currently supports updating payment order statuses and creating account balances, with more scenarios coming soon, including creating incoming payments and creating transactions.
Learn more:
In order to improve the readability of the Payee verification request object, we have renamed requesting_agent
into requesting_agent_bank_code
and responding_agent
into responding_agent_bank_code
.
Numeral now enables customers to monitor connectivity with partner banks, CSMs, and connectivity providers.
Connectivity syncs are created whenever Numeral connects to a partner bank, CSM, or connectivity provider to send and receive payments and reports.
Users can:
- Monitor data exchanges initiated by Numeral
- View connectivity sync status (
success
,failure
, orwarning
) with associated timestamps and metadata - Filter connectivity syncs by type, status, connected account, or date via the API
Each connectivity sync is linked to one or more connected accounts and includes lifecycle information to help users track operational issues of payment processing.
This feature is accessible via the API.
Swift GPI payment tracking now available in the dashboard
Customers can now track payments using Swift GPI directly in the dashboard. Swift GPI-tracked payments have a new Swift GPI tracking tab with their processing timeline and status across correspondent banks.
This feature is part of Swift GPI tracking through partner banks.