Skip to main content

Release 1.129

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

ZenPay Release 1.129​

This release introduces new capabilities for issuing credits back to customers, strengthens payment and callback reliability, and expands customer verification options.

This release introduces new capabilities for issuing credits back to customers, strengthens payment and callback reliability, and expands customer verification options. We’ve also delivered significant improvements to points and rewards management, especially for multi‑currency programs, and enhanced customer support and profile management across B2Bpay and Fionix experiences.

Payments & Settlements​

  • Added support for issuing credits back to customers (in addition to refunds) for selected merchants, including configurable daily limits and API access for requesting and tracking credits. This gives merchants a controlled way to correct payments while maintaining strong financial and risk controls.
  • Improved processing of payment statuses
  • Improved processing of batch payments.
  • Fixed an issue where some B2B payments remained in a pending state even after being approved, ensuring that once a payment is approved it progresses correctly and the customer’s card is only charged when the status is updated.
  • Added better handling of PayTo‑related terms and snippets in the payment plugin so that the correct terms and conditions are shown when specific payment options (such as deferred payment methods) are selected.

Points, Rewards & Programs​

  • Enhanced the Manage Rewards experience with a points currency column, currency‑aware filters, CSV export updates, and summaries that respect the chosen currency. This makes it easier for administrators to understand and report on rewards activity per currency.
  • Added support for Velocity Business Flyer as a points transfer partner, including connection and transfer capabilities, so eligible customers can link membership and transfer points to this program.
  • Fixed issues where QBR points redemptions and other partner redemption files were not being generated or reflected correctly in redemption history, ensuring that points earned and redeemed appear accurately in customer and admin views.
  • Addressed minor discrepancies in points statuses in history tables (for example, “Awarded” vs “Redeemed”) so that points histories correctly reflect the underlying action (conversion or redemption).

Customer Experience & Support​

  • Ensured that updates to business address fields (such as additional address lines) in the customer profile are properly saved and reflected in the UI.
  • Improved customer profile handling for New Zealand region customers, fixing issues where the country would revert to Australia and state/province options were limited, so addresses can now be correctly maintained for non‑Australian customers.
  • Implemented a dedicated Customer Support experience in the Fionix/B2Bpay 2.0 platform, including a support entry point on logged‑in pages and a support page that offers clear options to email, call, or access FAQs, plus a structured “Send us an email” form with validation and prefilled profile details where available.
  • Fixed small user interface misalignments and text issues in customer‑facing flows (for example, aligning screens to Figma designs and correcting labels) to provide a more polished and consistent experience.
  • Adjusted CSV exports and labels for customer data (for example, date of birth formatting and column names) to be clearer and more consistent with other areas of the platform.

Integrations & Technical Improvements​

  • Added PayTo status information to callback URLs used by integrators when PayTo is used for one‑off payments or tokenisation, making it easier for integrated systems to understand the current mandate status without additional lookups.
  • Ensured that PayTo token information is available in relevant tokenisation and status webhooks, enabling integrators to link webhook notifications to the correct tokenised account without storing raw bank account details, and improving security by obfuscating account information where appropriate.
  • Resolved an issue where certain callback notifications (for example, for specific TravelPay merchants) were not always received by integrators, improving the reliability and traceability of callbacks for successfully processed transactions.
  • Addressed issues with tokenisation in specific scenarios where customers could encounter a “please contact administrator” error during card token creation, ensuring a smoother tokenisation experience and correcting underlying configuration dependencies.
  • Added a dedicated TravelPay Shield flag on applicable transactions so program and compliance managers can more easily identify and report on transactions that qualify for this protection in admin and merchant portals.
  • Clarified the behaviour and documentation of selected API endpoints (including session‑related endpoints and transaction type descriptions) so integrators have a more accurate and complete view of available responses and transaction types.