Skip to main content

Release 1.130

· 4 min read
Zenith Product Team
Zenith Product Team
Product Management

ZenPay Release 1.130​

This release improves the reliability of PayTo settlements and payment approvals, enhances B2Bpay's integration with accounting systems such as Xero, and makes points balances and rewards behaviour clearer for customers.

This release improves the reliability of PayTo settlements and payment approvals, enhances B2Bpay’s integration with accounting systems such as Xero, and makes points balances and rewards behaviour clearer for customers. We’ve also strengthened program/site awareness for customers and payments, improved customer sign‑up and support experiences, and delivered performance and webhook upgrades for integrators.

Payments & Settlements​

  • Fixed an issue where some PayTo settlements appeared on the wrong date in ZenPay, so settlement dates now more accurately reflect when funds reach your bank and when merchants should expect settlement.
  • Resolved a browser-side error that could appear when making a one-off customer payment, reducing noise and friction during checkout.
  • Improved system performance for certain payment processes

B2Bpay & Accounting Integrations​

  • Corrected how failed B2Bpay payments are reflected in Xero so failed transactions no longer appear as paid and invoices remain outstanding until successfully settled.
  • Added a new capability in the core API to expose current account settings for connected accounting partners (such as Xero), supporting more reliable configuration flows and future self‑service editing of these settings.
  • Updated payment behaviour so that when valid accounting partner details are passed for eligible scenarios, unnecessary 3‑D Secure prompts are avoided, reducing friction in trusted flows while keeping security expectations unchanged elsewhere.
  • Redirected legacy B2Bpay quick registration links to the current sign‑up experience on the new platform, providing a more consistent onboarding journey and ensuring better data collection for new merchants.

Points, Rewards & Programs​

  • Resolved mismatches between “Available Points” on dashboards and the latest balance in points history so customers see a single, accurate view of their points at any time.
  • Fixed an issue where some Qantas Points balances could display as zero despite successful accrual, restoring correct visibility and ensuring customers can redeem their earned Qantas Points.
  • Improved handling of failed redemptions so rejected operations no longer increase redeemed points totals, keeping redemption history and balances accurate.
  • Addressed scenarios where alternative‑fee transactions and accelerator programs did not correctly allocate points, ensuring that points and rewards are now consistently applied in those cases.

Customer Experience & Support​

  • Fixed issues that prevented some newly created users from setting or resetting their password, and corrected “Forgot password” emails so they consistently include a working reset link.
  • Improved sign-up forms by clarifying website URL handling and “I don’t have a website” options, and by making validation and consent checkbox behaviour more reliable, reducing confusion and failed sign‑ups.
  • Improved wallet and payee management so customers can successfully change their default payment method without losing nicknames, and removing a payee no longer displays a misleading error when the operation succeeds.
  • Ensured logged-out customers can submit support enquiries reliably via the “Send us an email” form, and that the support team receives the customer’s own email address as the sender, improving follow‑up and response accuracy.
  • Updated support enquiry categories configured in admin tools so they correctly appear in the customer-facing support page, helping customers choose the most relevant topic when contacting support.

Integrations & Technical Improvements​

  • Made webhook processing more robust with improved reliability, logging and retry handling, and broadened coverage of state changes, including PayTo tokenisation and other lifecycle events, giving integrators a more complete and dependable event stream.
  • Corrected PayTo tokenisation status events so creating a new token is now clearly reported as a new event (rather than an update), making it easier for integrated systems to interpret token lifecycle events accurately.
  • Improved handling of SlicePay data.
  • Resolved issues affecting session creation and redirect flows for certain integrated payment solutions, improving the stability of hosted payment flows and reducing errors when launching payments from connected platforms.