Purpose Codes Documentation Update

We've expanded and updated our list of Payout Failure Reason codes. This comprehensive guide provides more specific, actionable feedback for every transaction, enabling you to build more robust error handling and better diagnose payout issues in your integration.

This covers the list of banks that are supported for payouts in Malaysia. The merchants need to provide the exact name as given in the list to create successful payouts.

What’s New: Webhook Logs, Re-sends, Auth & Access Control

This addition outlines the file types supported by our stack. Please refer to the sections mentioned in this section for details on each category.

Going forward, providing a clear and concise description for each payout transaction will become mandatory.

We’ve added a Confirmation Documents section to the Vendor Payouts and Settlements summary screens – giving you direct access to key documents related to your transactions.

• Settlement Object
  • Resource representing a batch of transactions that are cleared and paid out.
  • Endpoints for constituent transaction listing:
    • Fetching the list of payins associated with a settlement
    • Fetching the list of refunds associated with a settlement
    • Fetching the list of collects associated with a settlement
    • Fetching the list of adjustments associated with a settlement
    • Fetching the list of payouts associated with a settlement
  • Webhook Events
    • Real-time notifications for key lifecycle updates

Integrated customers will now need to pass the following fields mandatorily while creating a checkout/payin transaction:

This update enhances payout success rates and streamline validations for required fields, leading to a more efficient and reliable payout experience which will require users to make changes to your existing API integrations by 30th April 2025.