April 1, 2025

Core Platform

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

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

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.