Changes to the API and webhooks that affect your integration, newest first.
2026-11-18
- Changed Breaking (live 2026-11-18): the sandbox now checks the API IP whitelist the same way as production. A sandbox request from an IP address that is not on your whitelist gets HTTP
403(Your IP address is not API whitelisted.), and a sandbox request without theX-PARTNER-IDheader gets HTTP400(Missing X-PARTNER-ID header.). Register your server IP addresses before testing in the sandbox. Accounts with IP whitelisting disabled skip the IP whitelist match. See IP Whitelisting.
2026-11-17
- Changed
POST /api/inquirynow rejects anamountthat is missing, not numeric, or below 1 with HTTP400and the new error codeINVALID_AMOUNT(Invalid amount, minimum 1.). No inquiry is created and no balance is reserved. Amounts of 1 and above are unchanged. See Inquiry.
2026-11-16
- Added optional
company_namefield onPOST /api/create/va,POST /api/checkoutandPOST /api/checkout/va: your company name, shown as the Virtual Account name when your customer pays by VA. Supported on selected banks only; elsewhere a default name is shown. Allowed characters: letters A-Z, spaces and.; other characters (including digits) are removed. Values longer than 30 characters are cut, and if fewer than 3 letters remain the value is ignored (e.g.A+BbecomesABand is ignored). When sent, it is also returned incustomer_details/customer_objof the checkout responses and incustomer_infoof the Payment Completed webhook. See Virtual Account.
2026-11-12
- Added HTTP
403with error code40301001(Client is inactive) on every signed API endpoint when the client account has been deactivated. See Authentication.
2026-11-05
- Added
data.similarity_scoreanddata.trigger_sourceonPOST /api/inquiry(including replays),POST /api/check/inquiryand the V2 disbursement webhooksdisbursement.v2.completed,disbursement.v2.failanddisbursement.v2.expired: the beneficiary name similarity score and who decided the name check. The V1disbursement.completedcallback is unchanged. See Inquiry. - Added sandbox keywords
NONAME,REJECTandREVIEWincustomer_nameto test the name check. See Inquiry. - Added name-check auto-reject (opt-in per account, Enforce mode): an inquiry whose name similarity score is below the auto-reject threshold fails at
POST /api/inquirywith the existingreasonRejectedandtrigger_sourceauto_reject. No balance is deducted;disbursement.v2.failand the V1disbursement.completedcallback (statusfail) are sent at once. No new status, error code or reason. - Changed for accounts with name validation on, an inquiry whose bank returns no account holder name is now held for review (
statuspending,similarity_score0) instead of passing asvalid; with auto-reject in Enforce mode it fails withreasonRejected. Previously the name check was skipped when the bank returned no name.
2026-10-30
- Added optional
transfer_typefield onPOST /api/inquiry:bifast(default, unchanged behaviour) orrtolto send the payout over real-time online transfer. See Inquiry. - Added error code
INVALID_TRANSFER_TYPE(HTTP 400) whentransfer_typeis neitherbifastnorrtol. - Added
data.transfer_typeonPOST /api/inquiryandPOST /api/check/inquiryresponses: the transfer type used,bifastorrtol. - Added
data.transfer_type(bifastorrtol) to the payout webhooksdisbursement.completed,disbursement.v2.completed,disbursement.v2.failanddisbursement.v2.expired. See Disbursement Completed Webhook.
2026-10-29
- Added
payer_info(payer name, PAN, issuer code, issuer name) to thepayment.completedandpayment.v2.completedwebhooks, for merchants enabled for it during onboarding. Keys the payment channel does not provide arenull.