February 4, 2025
- Core Platform
- Issuance and Cards
- Payouts and Payins
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
transfersthat have Customer_Wallet_Credit_Fund_Transfer as thetransactionType. - The Fund Transfer Between Wallets event will be sent instead for
transfersthat haveCustomer_Wallet_Credit_Fund_Transferas thetransactionType.
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: