Mandatory MID Header Requirements
To enhance transaction traceability and platform security, we are introducing a mandatoryMID
(Merchant ID) header for customer-level API calls.
To enhance transaction traceability and platform security, we are introducing a mandatoryMID
(Merchant ID) header for customer-level API calls.
To enhance transaction clarity and improve regulatory compliance, we are introducing significant updates to the purposeCode
field across our API endpoints. This includes both an expanded list of purpose codes and a mandatory purposeCodeReason
field for specific scenarios.
To improve data completeness and streamline our identity verification processes, we are introducing several updates to our user creation and Standard KYC APIs.
To streamline user onboarding and provide greater flexibility for our partners, we are making the date
field optional for specific user creation flows. This change applies when creating users for non-ramp services, such as direct payouts or collections.
To enhance transaction clarity and improve regulatory compliance, we are introducing a mandatory purposeCodeReason
field for specific API requests. This change will affect all endpoints where purposeCode
is set to other
.
We are implementing enhanced age verification and restrictions for individual user accounts to ensure regulatory compliance across different markets and improve risk management for financial services.
We have implemented changes to enhance order ID generation to improve system reliability for high-traffic scenarios.
We are introducing QR Code payout functionality for Vietnamese Dong (VND) and Brazilian Real (BRL) currencies to provide faster, more convenient payment experiences for end users in these markets.
We are implementing mandatory invoice requirements for all payin and payout transactions to improve compliance, audit trails, and regulatory adherence across our payment platform.
We have implemented changes to make payerName field mandatory for EUR Currency.