There are no changes at this time.

There are no changes at this time.

Payout Rail Preference — New Currency Support​

Added support for AED (United Arab Emirates Dirham) and MYR (Malaysian Ringgit) currencies in Payout Rail Preference. Clients can now specify preferred routing rails for these corridors using generic modes (REALTIME, SAMEDAY, etc.) or explicit rail IDs.

For more information, see Payout Rail Preference.

Originating FI Screening​

Added support for multi-party payment flows, letting you route payouts through up to 6 originating financial institutions (OFIs) in a single request.

originating_parties — include your chain of originating parties when submitting a payout; first-time parties undergo a short compliance review, then auto-clear for 12 months

Requires enablement by your Nium account manager. GA rollout June 2026. For more information, see OFI Screening Guide.

Payout Schema API​

Added new API that lets you programmatically fetch field requirements, validation rules, and purpose codes for any payout corridor before submitting a transaction - eliminating rejected payouts caused by missing or malformed data. No changes required to existing integrations. Payout Schema API can be queried by destinationCountry, currency, payoutMethod

Available now for all clients. For more information, see Payout Validation Schema.

V5 Simulate Customer Onboarding Status​

We've introduced simulation support for V5 Customer Onboarding, enabling users to drive compliance state transitions using action-based controls — submit_kyc, raise_rfi, clear, and reject — across both individual and corporate customer types. This release aligns simulation capabilities with the V5 data model, where customer lifecycle state is tracked through a combined status and subStatus pair for finer-grained control when testing compliance flows. For more information, see Simulate Customer Onboarding Status (V5).

There are no changes at this time.

There are no changes at this time.

V5 Customer Onboarding APIs​

We’ve launched V5 of our Customer Onboarding APIs to simplify and accelerate global customer onboarding. This release introduces a unified onboarding API across customer types, enhanced file upload capabilities, stronger upfront validations to reduce RFIs, and a standardized data model for a more consistent experience. With clearer status tracking and built-in compliance workflows through KYC Pre-built Form, V5 reduces integration effort and enables faster go-live.

V5 is now live across 9 regions: EU, UK, NL, SG, AU, US, CA, JP, and HK.

For more information, see V5 Customer Onboarding APIs

Async Account Statement Generation​

Nium has revamped the account statement experience with asynchronous report generation. Clients can now request a statement using the new Initiate report generation request, and receive a Report Generation Status webhook once the report is ready. Upon a COMPLETED status, download the statement using the Download report request. Alternatively, statements can be pushed directly to your SFTP server — supporting password-based, SSH key-based, and SSH key + password-based authentication. The new statement APIs are part of the Reports section, a unified API set built to support multiple report types with a single integration.

For more information, see Customer Account Statement.

There are no changes at this time.

There are no changes at this time.

Local Funding Available in Mexico and Colombia

Local funding is now supported in Mexico (MXN) and Colombia (COP). You can create virtual accounts to receive funds locally in these corridors, enabling faster settlement and simplified reconciliation for incoming payments.

For more information, see Virtual Accounts.

There are no changes at this time.

Nium Verify: Name Match for all Corridors

Name match verification is now available for all corridors. The verification response includes a nameMatch field indicating if the account holder's name matches your records.

The nameMatch field returns one of three values: match, partial_match, or no_match, alongside the name registered at the bank in derivedAccountDetails.name.

For more information, see Nium Verify.

Nium Verify: Pakistan Bank Code Support

Pakistan (PKR) verification requests now accept a bank code as an alternative routing identifier. Pass the four-character bank identifier in the bank.bankCode field (for example, HABB for Habib Bank Limited) when a full SWIFT code is not available.

For more information, see Required Fields.

Pre-built Forms

Introduced Pre-built Forms, a ready-to-use experience that lets you collect required information from customers during onboarding and transaction-related compliance reviews—without building or maintaining your own forms.

Pre-built Forms help you manage RFIs consistently across the customer lifecycle, reduce time to go live, and integrate seamlessly into your existing flows—whether used for customer onboarding or transaction compliance.

For more information, see Pre-built Forms.

There are no changes at this time.

Payout Validator

Introduced the Payout Validator, a new capability that lets you validate payouts before debiting funds or creating a transaction.

The Payout Validator checks payout requests against Nium’s payout requirements and corridor rules—surfacing issues such as missing fields, invalid formats, or unsupported configurations upfront. This helps prevent failed payouts, reduce reversals, and give customers clear feedback before submission.

For more information, see Payout Validator.

Updates

There are no changes at this time.

Updates

There are no changes at this time.

New Failure Code

We’ve added a new failure code, RC07.

This code appears when the routing code—or the combination of the beneficiary account number and routing code—is invalid.

For more information, see Failure Codes.

Verification of Payee (EU)

Starting October 9, 2025, all EUR Local payouts from EU-based clients will be subject to Verification of Payee (VoP) checks in line with EU regulations.

These checks confirm that the beneficiary name matches the account details before the payout is processed. Transactions with name mismatches will be automatically rejected.

For more details, see Verification of Payee.

Expanded Nium Verify Coverage: Europe

We’ve expanded Nium Verify coverage across 19 European countries through the new EU Verification of Payee (VoP) framework. This enhancement provides deeper account-name matching and compliance-grade verification for all EUR Local payouts.

• 19 new markets added in Europe via VoP integration
• Direct connections to participating banks through the EPC network
• Real-time account name verification before initiating a payout
• Standardized responses (verified, not_verified, not_supported) across all EU markets

Newly supported markets

Austria, Belgium, Croatia, Cyprus, Denmark, Estonia, Finland, France, Germany, Greece, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Slovenia, Slovakia, Spain

Available now for all EUR Local corridors.

There are no changes at this time.

There are no changes at this time.

Verification of Payee (EU)

Starting October 9, 2025, all EUR Local payouts from EU-based clients will be subject to Verification of Payee (VoP) checks in line with EU regulations.

These checks confirm that the beneficiary name matches the account details before the payout is processed. Transactions with name mismatches will be automatically rejected.

For more details, see Verification of Payee.

Core Platform​

Introducing Live-Authorization for EU Applications​

Live-authorization is a digital alternative to paper-based Power of Attorney (POA) verification.

• For EU applications, any applicant who is not a director must provide a POA signed by a director. If the director is based outside the EEA, this POA must be verified by an apostille.
• Live-authorization is completely digital, requires no apostilization, and requires no manual review, accelerating the verification process.

Live-authorization is currently available for EU applications and will be expanded to other regions soon.
For more information, see Letter of Authorization.

Onboarding Guide Changes​

We have upgraded our onboarding guides for the US region to include the following:

• Addition of optional documents such as Proof of Business and Ownership Chart to improve approval TATs. A Template for Ownership Chart has been added.
• Improved guidance on key topics such as:
  • How to add positions
  • Expected documents for Proof of Business / Source of Wealth
  • New optional fields such as expectedAccountUsage and natureOfBusiness to avoid RFIs

For more information, see Onboarding.

Issuance and Cards​

There are no changes for this time period.

Payouts and Payins​

Schema Preview (Beta)​

Nium has introduced a new beta feature for the GetValidationSchema request.

Subscribed customers can now preview upcoming changes to the Beneficiary Schema before they go live. This early access allows teams to update beneficiary data in advance, ensuring a smooth transition when the changes are officially released.

For more information, contact Schema Preview (Beta).

Upcoming Regulatory Change: Verification of Payee (VoP)​

Starting October 9, 2025, all EUR Local payouts from EU-based clients will be subject to Verification of Payee (VoP) checks, in line with EU regulations.

Any payout with a name mismatch will be automatically rejected.
For more information, see Verification of Payee.

Core Platform​

There are no changes for this time period.

Issuance and Cards​

There are no changes for this time period.

Payouts and Payins​

New Feature​

Know When Funds Will Arrive — Estimated Delivery Time​

Clients can now view the expected delivery time of payouts at the moment a transaction is initiated. This information is shared via the estimatedDeliveryTime field in the REMIT_TRANSACTION_SENT_TO_BANK webhook.

The timestamp reflects when the funds are expected to reach the beneficiary, based on real-time routing data, partner cutoffs, and local holidays.

For more information, see Estimated Delivery Time.

Upcoming Regulatory Change​

Effective October 9, 2025, all EUR Local payouts from EU-based clients will undergo Verification of Payee (VoP) checks per EU regulation. Payouts with name mismatches will be rejected by default.

See the Verification of Payee guide for integration details and configuration steps.

Core Platform

Enhancements

Tags added to Webhooks

We've now added tags to the following webhooks. This change will help you manage webhooks more efficiently.

• Client KYB Status
• Customer Registration

Issuance and Cards

There are no changes for this time period.

Payouts and Payins

There are no changes for this time period.