Core Platform

Enhancements

clientTransactionId now included in reconciliation labels

clientTransactionId is now included as a label in the following transaction types:

• Wallet_Credit_Mode_Offline
• Wallet_Credit_Mode_Offline_Third_Party

clientTransactionId is provided by clients in the Fund Wallet request and helps you keep track of transactions for reconciliation purposes.

For more information, see Transaction Response Labels.

Issuance and Cards

New Features

Convert virtual cards to physical cards

Empower your customers with more choice. With the new Convert Card request, you can upgrade an active virtual card to a physical one. This helps you support fast virtual issuance while still meeting customer demand for in-store or ATM access.

For more information, see Manage Cards.

New Flutter SDK guides for Apple Pay and Google Pay

Now it’s easier than ever to integrate digital wallet provisioning into your Flutter apps. Our new guides walk you through implementing Apple Pay and Google Pay Push Provisioning using Nium’s SDKs—complete with platform channel setup, native code examples, and troubleshooting tips.

Whether you're building for iOS or Android, you can get cards into wallets faster and streamline the in-app payment experience.

For more information, see:

• Apple Pay - Flutter SDK
• Google Pay - Flutter SDK

Payouts and Payins

Enhancements

Improved bank account verification with Nium Verify

We’ve made it easier to integrate and more informative to use. Recent upgrades to Nium Verify improve visibility, clarity, and developer experience.

• Simplified integration: You no longer need to pass the customerId in your requests—less setup, fewer steps.
• Track verification history: Use the new List Verifications request to fetch all verifications sent to Nium.

More detailed results: We’ve refined our response data to help you act with confidence:

• For valid accounts: A new derivedAccountDetails object includes the account holder’s name from bank records—and, where applicable, the name in the local language.
• For invalid accounts: A new failureCode explains why verification failed (e.g. incorrect name or inactive account).
• For unsupported accounts: Responses now include more specific reasons—such as unsupported banks or currency-country mismatches.

These changes help you deliver a smoother onboarding experience and reduce verification delays. Learn more in the updated Nium Verify.

Core Platform

Enhancements

New rfiHashId for Easier RFI Tracking

A new parameter, rfiHashId, is now available in the following requests:

• Fetch Corporate Customer RFI Details​
• Respond to RFI for Corporate Customer

You can now store and use an rfiHashId to uniquely identify and respond to Requests for Information (RFIs), helping ensure accurate tracking and preventing mix-ups.

While templateId remains available, we strongly recommend migrating to rfiHashId for improved accuracy and future compatibility.

For more details, see Requests for Information (RFIs). If you have any questions, please contact your Nium account manager or Nium Support.

Issuance and Cards

There are no changes for this time period.

Payouts and Payins

New features

Nium Playbook Changelog

We’ve launched a changelog for the Nium Playbook, making it easier to track updates to our transaction capabilities all in one place.

Explore the changelog and stay up to date: Nium Playbook

Failure Codes Guide

We’ve published a new Failure Codes guide outlining why transactions may fail and the standardized ISO codes that are returned. These codes helps you by providing a:

• Simplified integration: Standardized failure codes reduce the need to interpret multiple financial messages.
• Faster resolution: Recommended actions are provided for each failure, helping you quickly identify and resolve issues.

Core Platform

Enhancements

Updates to Virtual Account Assignment

Virtual accounts can now only be assigned when a customer’s compliance status is CLEAR. If the status is PENDING, the request will return an error.

This change helps ensure virtual accounts are only assigned to valid customers. For more information, see Virtual Account Number.

Use the Assign Payment ID request to assign virtual accounts. This change ensures virtual accounts are only assigned to eligible customers.

Issuance and Cards

There are no changes for this time period.

Payouts and Payins

There are no changes for this time period.

Core Platform

Enhancements

Wallet-to-Wallet Transfers Now Support External ID

You can now include a senderExternalId in wallet-to-wallet transfer requests. Additionally, you can fetch wallet-to-wallet transfers using the externalId assigned when creating the customer.

This enhancement simplifies transaction tracking and reconciliation. For more information, see Wallet to Wallet Transfer.

Issuance and Cards

There are no changes for this time period.

Payouts and Payins

New Features

Fetch Transaction Lifecycles with External ID

You can now fetch the lifecycle of a transaction and status changes it goes through using the externalID from our Transfer Money request. This change helps make transaction tracking and reconciliation even simpler.

• Search using your External IDs: Retrieve the lifecycle of a transaction using externalID as a parameter.
• Easier Reconciliation: Track transactions using your own reference IDs.
• No Breaking Changes: You can still fetch the lifecycle of transactions using the systemReferenceNumber.

For more information, see Transaction Lifecycle.

Core Platform

Deprecation Notices

P2P Transfer Between Wallets Webhook Deprecation

The P2P Transfer Between Wallets webhook event will be deprecated in March 2025.

• This event was sent for transfers that have Customer_Wallet_Credit_Fund_Transfer as the transactionType.
• The Fund Transfer Between Wallets event will be sent instead for transfers that have Customer_Wallet_Credit_Fund_Transfer as the transactionType.

Issuance and Cards

Enhancements

New childCustomerHashId Field in Assign Card Request

The Assign Card request now includes a childCustomerHashId field. This change helps you keep track of customers under a corporate client account and their activity for accurate record-keeping and oversight.

Payouts and Payins

New Features

Send Payments and Add Beneficiaries in One Step

We’ve made it easier to send payments through Nium! Previously, creating a beneficiary using our Beneficiary endpoint was required before initiating a transfer. With this latest change, you now have the flexibility to send payments without pre-creating a beneficiary.

Specifically, customers can now send payments using the Transfer Money request by either:

• Including beneficiary details directly within the request, along with the account details.
• Including a beneficiaryId (similar to today’s behavior).

This update simplifies payment processing and offers greater flexibility. See the Transfer Money guide. Start creating beneficiaries and payments today for a smoother payout experience! 🚀

Enhancements

Faster Transaction Processing with Document Upload

We’ve enhanced our Upload Transaction Receipt request to streamline payment processing and minimize delays caused by RFIs.

Customers can now upload supporting documentation linked to a payment, allowing us to process transactions faster. Specifically, after using the Transfer Money request to initiate a transaction, retrieve the system reference number from the response.

Then use the Upload Transaction Receipt request to upload documentation; include the system reference number as the transactionId in the path parameter.

For more information, see the following requests:

• Transfer Money
• Upload Transaction Receipt

Core Platform

Nium Portal

New Features

Nium Portal In-line Payouts

In-line Payouts enables any user to create payouts directly in Nium Portal—no coding or integrations needed. Select a beneficiary, set payout details, and you're done! For more information, see Payouts.

API Breaking Changes

Transactions complianceStatus Changes

The complianceStatus returned in the Transactions API response will only return RFI_REQUESTED and RFI_RESPONDED beginning January 15th, 2025. For compliance purposes, the remaining values won’t be supported. If you have any questions, please contact your Nium account manager or Nium Support.

Issuance and Cards

There are no updates for this time period.

Payouts and Payins

Enhancements

Nium Verify now available in India and the European Union

Nium Verify is live in the European Union and India! You can now verify corporate bank accounts in Belgium, France, Italy, Netherlands, and Poland and retrieve the account holder name. For a consolidated list of all Nium Verify’s coverage, see Nium Verify.

New externalID Field

We have introduced a new field, externalID, in the Transfer Money request to allow customers to include their custom reference ID for transactions. This enhancement simplifies reconciliation for clients.

• The externalID field is a string that accepts user-defined reference numbers.
• It supports idempotency by rejecting transactions with duplicate reference numbers, thereby preventing duplicates.
• Customers can filter transactions using externalID via the Transactions API and Fetch Remittance Lifecycle API.
• Additionally, this field is included in all payout webhooks to facilitate seamless reconciliation.

For more info, see Transfer Money in our API Reference.

API Breaking Changes

Fetch Supported Corridor V2 Deprecation

The Fetch Supported Corridor V2 request will be deprecated and unavailable as of April 1, 2025. We’ve launched an updated version, Fetch Supported Corridors V3, which offers enhanced details on supported remittance corridors.

Please integrate with Fetch Supported Corridor V3 by April 1, 2025 to avoid any disruptions. For more information, contact your Nium account manager or reach out to Nium Support.

Core Platform

There are no updates for this time period.

Issuance and Cards

New Features

Multiple Wallets for Card Issuance Clients

Multiple Wallets now supports card issuance, enabling users to issue cards from additional wallets. This helps manage funds across multiple wallets within card spend accounts, enabling flexible expense allocation and greater control over spending.

Card UI Updates:

• Add Card UI: Added a walletHashId dropdown to enable wallet selection during card setup for customer-level association.
• Card List UI: walletHashId is now displayed, showing wallet associations for each card.
• Assign Physical Card UI: Added walletHashId and customerHashId fields for assigning physical cards to specific wallets and customers.

Multiple Wallets and Card Issuance is currently available in:

• Australia
• Canada
• Hong Kong
• Singapore
• United Kingdom

For more information on Multiple Wallets, see Wallets - Overview.

If you’re interested in Multiple Wallets, please reach out to your Nium account manager or contact Nium Support.

Payouts and Payins

New Features

Payins Playbook

We’ve launched an online playbook for pay-in network capabilities. Use it as a guide to receive money on the Nium network.

For more information, see the Payins User Guide.

Enhancements

Nium Verify now available in the United States

Nium Verify is now live in the United States! You can verify bank accounts in the U.S.

Please note our US offering is currently in beta. If you're interested, please reach out to your Nium account manager or contact Nium Support.

For a full list of regions Nium Verify is available in, see Nium Verify.

Paper check payouts now available in the United States

We’ve enhanced our U.S. payout capabilities to support paper checks for beneficiaries.

For more information, see Paper Checks.

Core Platform

New Features

Onboarding Forms: Now available in Japan and New Zealand

Our onboarding forms are now available in Japan and New Zealand English! This update makes it easier for users in Japan and New Zealand to complete the onboarding process in their preferred language.

For more information, see:

• JP onboarding
• NZ onboarding

Issuance and Cards

There are no updates for this time period.

Payouts and Payins

New Features

Nium Verify: Now available in Tanzania and Nigeria

Nium Verify is live in Tanzania and Nigeria! You can now verify bank accounts in these regions and retrieve the account holder's name as registered with the bank. For more information, see Nium Verify.

Additionally, when verifying bank accounts in Vietnam, you can now retrieve the registered account holder’s name as part of the verification response.

API Breaking Changes

Deprecation Notice: Fetch Supported Corridor V2 API

The Fetch Supported Corridor V2 request will be deprecated and unavailable as of April 1, 2025. We’ve launched an updated version, Fetch Supported Corridors V3, which offers enhanced details on supported remittance corridors.

Please integrate with Fetch Supported Corridor V3 by April 1, 2025 to avoid any disruptions.

For more information, contact your Nium account manager or reach out to Nium support.

Core Platform

New Features

Test Nium with our new Simulation requests

Nium has introduced enhanced Simulation APIs to help developers test various services and refine their integrations confidently. This suite allows you to simulate different scenarios across onboarding, payouts, and compliance transitions. By leveraging these simulations, clients can ensure their implementation meets real-world demands without impacting actual operations. Available tests include:

• Onboarding Simulations: Test the compliance statuses for individual and corporate accounts, ensuring readiness before live operation.
• Payout Simulations: Validate transaction flows, including error handling and response to different compliance requirements.
• Flexible Status Transitions: Move transactions through various lifecycle statuses, such as RFI_REQUESTED, PAID, or ERROR, to verify end-to-end processes.

For step-by-step guides and API details, see Testing Nium.

Nium Verify

Ensure accurate bank details and reduce payment failures with real-time account verification. For more information, see Nium Verify.

Enhancements

Multiple Wallets - Account Statement

Clients can now generate account statements for a specific wallet using the Fetch Wallet Statement request. This change helps you better reconcile and manage the different wallets you create.

For more information, see Customer Account Statement.

API Breaking Changes

Biometric Authentication Requirement

Nium will begin updating authentication requirements for online card transactions in line with the latest requirements from card issuers. These changes aim to enhance transaction security and improve the cardholder’s experience by implementing more robust authentication measures.

By April 1st, 2025, all NIUM clients must enable biometric authentication for online transactions made on devices that support biometric verification (e.g., fingerprint or facial recognition). Clients will need to integrate with Nium’s Out-of-Band (OOB) authentication flow to support this functionality. For more information about implementing, see OOB Authentication Flow.

By integrating biometric authentication for online payments, Nium clients can provide their customers with a more convenient and secure method for verifying transactions. Biometric authentication helps increase the success rate of authentication while reducing fraud in high-risk scenarios.

• Higher authentication success rates
• Increased transaction approval rates
• Reduced fraud on high-risk transactions
• Improved security for step-up authentication when biometrics are used

complianceStatus changes

The complianceStatus returned in the API response will only return RFI_REQUESTED and RFI_RESPONDED beginning January 15th, 2025. For compliance purposes, the remaining values won’t be supported. If you have any questions, please contact your Nium account manager or Nium Support.

Issuance and Cards

There are no updates for this time period.

Payouts and Payins

New Features

New beneficiaryIntermediaryBankCode field

We’ve added a new beneficiaryIntermediaryBankCode to the Transfer Money request to help capture the correspondent’s (also called the intermediary’s) bank code. This new field helps reduce transaction rejections where SWIFT payouts to specific corridors require additional information about the intermediary bank.

Core Platform

There are no updates for this time period.

Issuance and Cards

New Features

Bulk Card Issuance

Nium now supports issuing cards in bulk. Bulk card issuance refers to the process where many prepaid or debit cards are produced at the same time.

Bulk issuance is an efficient way to generate and distribute large quantities of cards and helps in saving card delivery costs.

Nium supports both personalized and generic card issuance. Cards can be personalized (Name on Card) or generic (no Name on Card), and can be shipped in one single shipment.

Bulk card issuance is often used for corporate programs, gift cards, payroll, or disbursement programs. Please contact your Nium account manager or Nium support if you’re interested in issuing cards in bulk.

For more information, see Cards Overview.

Payouts and Payins

There are no updates for this time period.