Core Platform

Enhancements

New Fee Details V3 request

Nium has enhanced our customizable pricing options. This includes pricing based on different payout and payin methods and tiered pricing. To view pricing based on these advanced options, use the Fee Details V3 request. Other enhancements include:

• Enhanced the labels for Fee_Debit transactions by returning additional information on the fees charged to customers. For more information, see Fees.
• See the feeName field to understand which predefined fee was charged for a transaction.
• Refer to the tierType field to see if the fee is based on a tier or non-tier rule.
• See the condition field to understand the conditions where a fee is charged. This includes factors like source_currency, destination_currency, and destination_country.

For more information, see Fee Details V3.

EU, UK and SG Documentation Verification

We've extended Know Your Customer (KYC) E_DOC_VERIFY documentation verification for stakeholders in the EU and United Kingdom. We've also extended E_KYC and E_DOC_VERIFY documentation verification to Singapore.

This change helps simplify the KYC process in the EU, where previously a notarized document was required to onboard beneficial owners.

For details on how to generate a redirectURL for any stakeholders in these regions, see Corporate Customers.

No Expiry for redirectURL

We've removed redirectURL expiration across all regions.

Session expiration is still in place in case a customer begins onboarding but doesn't complete it in a single session.

When a session expires, customers will be able to use the same redirectURL.

Standardized Letter of Authorization

We've standardized our Letter of Authorization (Power of Attorney) across all regions.

For more information, see Letter of Authorization.

Issuance and Cards

There are no changes at this time.

Payouts and Payins

There are no changes at this time.

Core Platform

New Features

Enhanced Account Verification for Payouts

Reduce failed transfers and improve payout success with Nium’s built-in bank verification. Before sending funds, confirm the recipient’s account details in real time—no test deposits or manual checks required. This helps you catch errors early, improve customer experience, and avoid unnecessary fees.

For more information, see Nium Verify.

Issuance and Cards

There are no changes for this time period.

Payouts and Payins

There are no changes for this time period.

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 Features

Local Funding Now Available in Brazilian Real

You can now fund in Brazilian Real (BRL) locally through Nium using Brazil’s most widely used payment systems: PIX (Instant Payment Platform) and TED (Electronic Funds Transfer).

This update helps clients with a presence in Brazil move money faster and reduce cross-border friction.

For more information, see Fund a Wallet.

Core Platform

New Features

Settlement Report Now Available

We’ve launched a daily Settlement Report to support your reconciliation efforts. The report includes all settled transactions across payins, payouts, P2P transfers, and fees.

You can download the report via the Nium Portal or receive it securely via SFTP. For more information, see Settlement Report.

Enhancements

Find Transactions Faster with Improved Filters

We’ve enhanced the Transactions page in Nium Portal to help you locate the data you need—faster:

• Search by External ID
• View transactions across all platform customers
• Filter by date and time with access to full transaction history

For more information, see Nium Portal.

Issuance and Cards

There are no changes for this time period.

Payouts and Payins

There are no changes for this time period.

Core Platform

New Features

Updated Beneficiary Validations

We’ve updated the validation rules for creating beneficiaries to align with those used for creating payouts. This update helps reduce rejections caused by typos or special characters.

For more information, see Add Beneficiary V2.

Ongoing Due Diligence (ODD)

Corporate customers approved more than one year ago are now subject to Ongoing Due Diligence (ODD)—a periodic review based on their risk profile and transaction history.

During this review, a compliance officer may issue one or more Requests for Information (RFIs). Prompt responses are required to complete the review.

Failure to respond may result in temporary account suspension.

For more details, see Corporate 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

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