Changelog

What’s new

Product updates, improvements, and fixes to the Tola Saint API and dashboard.

v1.5.0

August 3, 2026
  • NewBakong is live as a second payment rail. Add your Bakong account ID in Merchant Settings to accept KHQR payments through the National Bank of Cambodia.
  • NewPOST /v1/bakong and GET /v1/bakong/status — dedicated Bakong endpoints, so you always know which statuses to expect.
  • NewA Bakong payment settles as "paid". Treat it exactly like ABA’s "approved" — if your code only checks for "approved", check for both.
  • NewEvery payment and webhook now carries a provider field ("aba" or "bakong"), so you never have to infer the rail from the status.
  • NewOne Bakong account ID covers both USD and KHR — no separate setup per currency the way ABA links need.
  • ImprovedBakong QR codes are built on our servers, so creating a payment never waits on a bank and cannot fail during a bank outage.
  • ImprovedWebhooks that fail are now retried for up to 24 hours instead of being dropped after a few minutes.
  • ImprovedFilter and export by the paid status, and see which rail each payment used in Transactions.
  • ImprovedPOST /v1/payment is unchanged for existing integrations: it keeps using your ABA link, and only uses Bakong if you ask for it or have no ABA link for that currency.
  • FixedQR links now stop working once a payment is paid or expired, so a stale link can no longer be scanned and paid.
  • FixedLong business names and references no longer fail Bakong payments. References up to 128 characters are kept in full.

v1.4.0

July 23, 2026
  • NewHosted QR image endpoint — every payment returns a scannable qr_link.
  • NewSigned webhooks with HMAC-SHA256 and automatic retries.
  • ImprovedStatus responses now include amount and currency.

v1.3.0

July 10, 2026
  • NewBackground poller detects status changes in near real-time.
  • FixedCorrectly decode unicode-escaped aba_data scraped from the merchant page.

v1.2.0

June 28, 2026
  • NewAttach reference and metadata to a payment on create.
  • ImprovedPayment expiry now follows ABA’s actual QR validity window.

v1.0.0

June 1, 2026
  • NewCreate payment and check status endpoints.
  • NewAPI key authentication, rate limiting, and structured logging.