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 Paymentrequest.

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 response 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 capbilties 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.

Enhancement

A new query parameter status has been released for the Virtual Account Details V2 request. With this new parameter, the active/inactive virtual accounts can be filtered by Clients.

There are no changes for this time period.

There are no changes for this time period.

New Feature

Reports are now available in Nium Portal. Reports enhance your financial management experience by providing detailed insights into your transactions. You can now track, analyze, and manage your financial activities with ease. For more information, see Reports.

Breaking API Changes

Starting October 1st, 2024, changes in Nium’s compliance policy will require additional documents and parameters to onboard corporate customers using the Onboard Corporate API. Please update your integration accordingly to avoid disruptions. If you have any questions, please contact your Nium account manager or Nium Support.

• Current State: These documents and parameters are optional.
• Future Requirement: From October 1st, 2024, these fields and parameters will be mandatory.
• Changes to Nium: If the required documents and parameters are not included, the API will return an error indicating the missing documents and/or parameters.

Changes to the Onboard Corporate API include:

• Device Information: IP address and device name is now required for all regions when onboarding corporate customers. See the deviceDetails object in our API Reference for more information about the changes in each country:
  • Australia (AU)
  • Canada (CA)
  • Europe (EU)
  • Hong Kong (HK)
  • Singapore (SG)
  • United Kingdom (UK)
  • United States (US)
• Europe (EU): Additional information and documents are now required for both eKYB and manual KYB when onboarding corporate customers in Europe (EU). For more details, see:
  • EU Required Documents
  • Stakeholder KYC
  • expectedAccountUsage
• Singapore (SG): Proof of Identity and Proof of address documents are now required for stakeholders for both eKYB and Manual KYB when onboarding corporate customers in Singapore (SG). For more information, see SG Onboarding.

There are no changes for this time period.

There are no changes for this time period.

There are no changes for this time period.

Enhancements

• Fetch Card Details V2: Fetching details using the Card Details V2 endpoint now returns the demographics object. The demographics object only gets returned if the card is assigned to an employee but issued within a corporate customer's wallet. For more information, see Card Details V2.
  
  Detials that get returned in the demographics object includes:

  • firstName
  • middleName
  • lastName
  • nameOnCard
  • email
  • mobile

New Features

• Direct Debit is now available for Singaporean (SG) customers. Direct Debit enables SG-based businesses to fund their Nium wallets using their Singaporean SG) bank account in real time.

  • The transaction type for Direct Debit transactions is WALLET_CREDIT_MODE_DIRECT_DEBIT.
  • Reach out to your Nium account manager for details on how to activate Direct Debit.
  • For more information, see Direct Debit SG.

Enhancements

• Maximum limit for INR Proxy (UPI) transactions has been increased to INR 200,000 from INR 100,000. For more information, see the Nium - India Playbook.

Enhancements

• We’ve introduced three new reasons you can include when permanently blocking a customer:

  • UNRESPONSIVE_CUSTOMER
  • DORMANCY
  • OTHER

• Moving forward, when PERMANENT_BLOCK is used, the customer's account will be considered closed, and they can no longer process any further activity.

• Applications rejected due to high risk or non-compliance will now be blocked from being resubmitted. Previously, such applications could be resubmitted but were rejected by our compliance team after review. With this change, applications that have been previously rejected will automatically be rejected without any wait.

  • Resubmission is still allowed for reasons unrelated to compliance, such as incomplete applications, typos, or incorrect addresses.
  • For individual customers, see Individual Customer Onboarding - Overview.
  • For corporate customers, see Corporate Customer Onboarding - Overview.

Enhancements

• We’ve released two new webhook events to help you manage cards:

  • Card Details Updated: This event is triggered to notify the client or cardholder when any card details are updated. For more details, see Card Details Updated.
  • Card Expiry Alert: This event is triggered when a card is approaching its expiration date. For more details, see Card Expiry Alert.

There are no changes for this time period.

Enhancements

• Our eKYC Onboarding APIs are now available for individual customers in Canada. For more details, see CA onboarding.

• Our OpenAPI spec is now available on GitHub. You can download and review our OpenAPI spec to help you build your integration with Nium. For more details, see our Nium OpenAPI repo.

• We've added ▶ Run in Postman buttons to several guides. These buttons give you quick access to our Postman collection and enable you to see how requests run in real-time. For an example, see Individual Customer Onboarding.

There are no changes for this time period.

Enhancement

• We've added additional fields to the remitter object used in the Transfer Money request to provide more details about the payout sender. Fields added include:

  • idExpiryDate
  • idIssueDate
  • originatingFICity
  • originatingFICountry
  For more details, see Transfer Money.