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.

Core Platform

New Features

Multiple Wallets

Corporate customers can now have multiple wallets on the Nium platform. Multiple Wallets offers more choice and convenience to clients and helps ledger management with single or multiple currencies.

• Currently, whenever a customer is onboarded on to Nium, a default wallet is created and linked with the customer. All transactions are credited and debited from that single wallet.

• With this change, customers can now hold balances and transfer funds between multiple wallets based on their business needs.

• The assignment of virtual accounts to any wallet is supported by the Assign Payment ID request.

• We’ve introduced three new APIs to support this feature:

  • Add Wallet
  • Update Wallet
  • Fetch Wallet

• We're actively working on bringing card issuance and card-based transactions for additional wallets.

• Currently, card issuance and card-based transactions only support the default wallet that was created and linked with the customer after completing onboarding.

• Multiple wallets are currently only available in select regions. The regions Multiple Wallets are available include:

  • Australia (AU)
  • Canada (CA)
  • Hong Kong (HK)
  • Singapore (SU)
  • United Kingdom (UK)
  • United States (US)

Please contact your Nium account manager or Nium support to evaluate your business use case and configure wallets for you.

Enhancements

Stay Informed with Our New Status Page

Monitor the real-time status of Nium services with our new Status Page. Stay updated on service performance and incidents, and subscribe to notifications for timely alerts on any service changes or issues. See our guide for more information.

Virtual Account related information

The account type returned in the API response of Virtual Account Details V2 and the Client Details request for GMO_JP bank has been changed from SAVINGS to LOCAL to make it standardized across all banking partners.

Issuance and Cards

There are no updates for this time period.

Payouts and Payins

There are no updates for this time period.

Core Platform

Enhancements

Intermediary Bank Code for Virtual Accounts from JPMC SG

The virtual account detail returned by the Virtual Account Details V2 API will now include the intermediary bank SWIFT BIC for virtual accounts issued for non-SGD currencies. This will be available in the routingCodeValue2 field and should be used for fund transfers through virtual accounts issued by JPMC SG.

Nium Portal

Virtual Account Numbers

You can now create virtual account numbers directly in the Nium Portal on the Customer Balances page. This caters to users who prefer the portal over our API.

For more information, see Virtual Account Numbers.

GPI Details for SWIFT Transactions

Global Payments Innovation (GPI) details for SWIFT transactions are now included in transaction reports, providing end-to-end visibility into transaction statuses.

For more information, see GPI details.

Payout Return Reasons

Transaction reports now display reasons for returned payout transactions, helping you identify and prevent issues.

For more information, see Transaction reports.

Nium Docs

New Financial Institutions Use-Case Guide

We’ve released a new use-case guide tailored for Financial Institutions (FIs). It provides detailed integration steps, fund flow examples, and an overview of key Nium features.

For more information, see Financial Institutions.

Issuance and Cards

There are no updates for this time period.

Payouts and Payins

Enhancements

Customer-Named Virtual Accounts Now Available for Hong Kong Payins

We’re enhancing payin capabilities in Hong Kong! You can now collect funds into customer-named virtual accounts in HKD via local methods, and in USD, EUR, GBP, AUD, CAD, and CNY via wires.

For more information, see Virtual Account Number.

Enhanced Reference Info for Nepal Payments

Beneficiaries in Nepal can now see the sender's name in Rupee payouts, improving transaction tracking. This adds transparency and security to every transaction.

Enhancements to the Proof of Payments API

The ultimate remitter’s name will now appear on the Proof of Payment PDF for on-behalf payouts, helping Financial Institutions manage third-party payout use cases more effectively.

For more information, see the Get Proof of Payment request.

Core Platform

There are no changes for this time period.

Issuance and Cards

Enhancements

Apple SDK

Our Apple Pay SDK has been enhanced to display the client's name when adding a card to an Apple Wallet. This helps you better manage cards in your Apple Wallet.

• SDK Version: 2.0.2
• Run pod update or pod repo update to get the latest version.

If you have any questions about our Apple SDK, please contact Nium Support.

Card Webhook Update

The walletProvider field in the VTS Token webhook is now restricted to applePay and googlePay.

This corrects an issue where some responses returned APPLE or GOOGLE. For more information, see VTS Token.

Payouts and Payins

There are no changes for this time period.

Core Platform - Enhancements

Nium Portal - Redesigned Customer Balances Page

We've redesigned the Customer Balances page to enhance usability:

• Review, at a glance, what features are enabled for each currency. This change helps you better understand what capabilities are available when managing those funds.
• Create Virtual Accounts for Payin-enabled currencies. Non-developers can now create Virtual Accounts in Nium Portal without directly using Nium’s API.

For more details, see the Nium Portal - Customer Balances.

There are no changes for this time period.

There are no changes for this time period.

There are no changes for this time period.

There are no changes for this time period.

New Feature

Account Verification

We’ve released a new Account Verification request that helps you verify payee details while creating beneficiaries. This change helps you simplify your integration, removing the need for a separate integration dedicated to verifying account details.

For more information, see Account Verification.

Enhancements

Updates to the Fetch Supported Corridors V3 Request

We’ve made the following changes to the Fetch Supported Corridors V3 request:

• payoutMethodCategory query parameter: Helps you separate supported payout methods by corridor - for more information and a detailed breakdown, see the Nium playbook.
• The query parameters beneficiaryAccountType, customerType, and payoutMethod have been made enums.

For more information, see the Fetch Supported Corridors V3 request.

New isOffMarket Parameter

We’ve introduced a new isOffMarket field to help you understand when off-market fees get applied to Conversion and Quote requests.

• The isOffMarket field is returned in the response to the following requests:

  • Create Quote
  • Fetch Quote by ID
  • Create Conversion
  • Fetch Conversion By Id
• Please note that this field isn't returned unless off-market requests have been enabled by Nium.

For more information, see FX - Overview.