Skip to main content

July 9, 2024

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.

June 25, 2024

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:

May 28, 2024

There are no changes for this time period.

April 30, 2024

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.

April 16, 2024

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.

March 5, 2024

New Features

  • Clients can now manually execute FX conversions. With this change, you're given greater control and flexibility over how funds get converted in customer wallets and the associated settlement timeframes.

    • Pass the new ExecutionType field when making requests to the /Quote API to indicate a manual scheduled FX conversion. This field defaults to at_conversion_time if nothing is passed.

    • Manual scheduled FX conversions must be executed using the /Execute endpoint (within the ExpiryTime) to transfer funds from the source currency to the destination currency within the wallet.

      • New fields:

        • ExecutionType: Set to at_conversion_time for timed conversions and manual for manual FX conversions.
        • ExpiryTime: This is a timestamp that indicates when the FX conversion expires. Manual conversions must be executed before this time.
    • We've also updated the following APIs:

Enhancements

February 20, 2024

Enhancements

February 6, 2024

New Features

  • We have introduced a new feature to Nium Portal called Batch Payouts. With batch payouts, you can now effortlessly process multiple transactions in one go while ensuring all your payouts are handled seamlessly. Learn more about batch payouts from our blog.

    For details on how to create batch payouts, see Batch Payouts.

  • We've released a Postman collection for all Nium APIs. Use the collection to build your integration.

    For more information, see Postman Collection.

January 23, 2024

New Feature

We have introduced a new Webhook event type called CUSTOMER_COMPLIANCE_STATUS applicable for individual customers. This event is triggered when there is a change to the individual customer's compliance status. For more information, see the Customer-compliance status event in our API reference.

Prior to this change, you had to configure a separate URL to receive the customer compliance status from Nium. The new event update will improve the developer experience by simplifying the number of integration steps. You can now use the same URL configured to receive all Webhook events and subscribe to the new event.

You can also subscribe to the event type CARD_CLIENT_KYB_STATUS_WEBHOOK to receive the compliance status of corporate customers. The Callback to receive customer-compliance status will continue to be supported.

Enhancement

We have introduced two new fields - ClientMarkupRate and MarkupRate - to help you apply FX markup rates to your customers.

  • The ClientMarkupRate is the markup rate you negotiated with Nium.
  • The MarkupRate field details the FX markup fees configured for your customer.
  • If there are no fees configured for your customer, the MarkupRate will default to the ClientMarkupRate.

Both fields can be found in the response body of the following APIs:

Having these fields readily available offers a convenient way to charge FX markup fees to your customers and helps you further monetize your FX services for revenue generation.

December 19, 2023

There are no changes for this time period.