Skip to content
PGSwift Docs
Documentation/Changelog

Changelog

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 the X-PARTNER-ID header gets HTTP 400 (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/inquiry now rejects an amount that is missing, not numeric, or below 1 with HTTP 400 and the new error code INVALID_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_name field on POST /api/create/va, POST /api/checkout and POST /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+B becomes AB and is ignored). When sent, it is also returned in customer_details / customer_obj of the checkout responses and in customer_info of the Payment Completed webhook. See Virtual Account.

2026-11-12

  • Added HTTP 403 with error code 40301001 (Client is inactive) on every signed API endpoint when the client account has been deactivated. See Authentication.

2026-11-05

  • Added data.similarity_score and data.trigger_source on POST /api/inquiry (including replays), POST /api/check/inquiry and the V2 disbursement webhooks disbursement.v2.completed, disbursement.v2.fail and disbursement.v2.expired: the beneficiary name similarity score and who decided the name check. The V1 disbursement.completed callback is unchanged. See Inquiry.
  • Added sandbox keywords NONAME, REJECT and REVIEW in customer_name to 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/inquiry with the existing reason Rejected and trigger_source auto_reject. No balance is deducted; disbursement.v2.fail and the V1 disbursement.completed callback (status fail) 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 (status pending, similarity_score 0) instead of passing as valid; with auto-reject in Enforce mode it fails with reason Rejected. Previously the name check was skipped when the bank returned no name.

2026-10-30

  • Added optional transfer_type field on POST /api/inquiry: bifast (default, unchanged behaviour) or rtol to send the payout over real-time online transfer. See Inquiry.
  • Added error code INVALID_TRANSFER_TYPE (HTTP 400) when transfer_type is neither bifast nor rtol.
  • Added data.transfer_type on POST /api/inquiry and POST /api/check/inquiry responses: the transfer type used, bifast or rtol.
  • Added data.transfer_type (bifast or rtol) to the payout webhooks disbursement.completed, disbursement.v2.completed, disbursement.v2.fail and disbursement.v2.expired. See Disbursement Completed Webhook.

2026-10-29

  • Added payer_info (payer name, PAN, issuer code, issuer name) to the payment.completed and payment.v2.completed webhooks, for merchants enabled for it during onboarding. Keys the payment channel does not provide are null.
© 2026 PGSwift. All rights reserved.