Enhancements

• Failed Payment Fee: Customers will no longer be charged a failed payment fee if a transaction is declined due to suspected fraud.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

We're back with some more important updates to share.

Enhancements

• System improvements: Increased CPU and memory allocation for backend-services, resulting in faster webhook processing.

Fixes

• Code Cleanup: Refactored and cleaned up backend components to enhance code maintainability and reduce redundant logic.

Enhancements

• Billing Details Checkbox: Users can now manually enter billing details instead of those fetched from Apple or Google Pay.

Fixes

• Apple Pay Safari Restriction: Apple Pay payments will only be available when using the Safari browser to ensure compatibility. The button will be hidden on other browsers.

We are once again excited to share the latest improvements and updates to our services.

Enhancements

• Vault Batch folder cleanup: The Vault Batch process has been improved to better manage temporary folders.
  Now, only specific bank files are removed, enhancing log clarity and reducing errors.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

Here’s a roundup of the recent improvements, fixes, and upgrades we've made to our product.

Enhancements

• Improved payment processing alignment: Safeguards added to ensure billing and payment modules stay in sync, preventing early settlement of unpaid bank payments.
• Optimised system performance: Polling rate reduced from 25 to 20 requests per cycle, enhancing efficiency and reducing system load while maintaining smooth transaction processing.

Fixes

• Apple Pay selection update: Apple Pay will no longer be automatically set as the default payment method, allowing users to select their preferred primary payment method.
• Improved invoice listing: The List Invoices API now returns a null result instead of an error when an invoice lacks a customer ID.
• Corrected subscription invoice: Resolved an issue where future invoice dates were miscalculated for subscriptions activated after their initial creation. Here are the improvements:
  • Future invoices will now be scheduled correctly based on the actual subscription activation date.
  • This fix ensures that customers linking a payment method after subscribing will receive invoices at the expected intervals.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

Here are some recent updates, fixes and enhancements we've made to our product.

Enhancements

• Google Pay integration: The configuration process for Google Pay has been updated to optimise handling. A default value is now introduced for cases where the last name is not provided, ensuring consistent data.
• Fee pricing configuration: The character limit for rule expressions has been increased to 250, allowing for more detailed and complex definitions.
• Fee & revenue logic: Updates have been made to allow for accurate calculation and distribution of revenue for newly supported payment methods, ensuring seamless handling alongside existing methods.
• Improved job management: A new feature has been added to record job execution history, allowing enhanced tracking, auditing, and prevention of duplicate executions.
• Payment retry logic: Automatic payment retries have been implemented for an additional error code, improving transaction success rates.
• Failed payment handling: Mock updates for handling failed payments have been deployed to the Sandbox environment to simulate scenarios and improve robustness.
• Internal platform updates: Revenue share components now support configurations for GCash, Apple Pay, and Google Pay, simplifying setup for these payment methods.
• Alert monitoring: The alert monitoring logic has been refined to reduce noise, with added tags to display invoice channels for improved tracking and visibility.

Fixes

• Resolved 500 HTTP error: Proper boundary checks have been added to prevent Index Out of Bound exceptions when processing Google Pay tokens.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

Happy New Year! A great start to announce the things we worked on as we bid farewell to 2024 and usher in 2025.

Enhancements

• Apple Pay: Enhanced functionality to store additional information returned by Apple Pay, providing improved data insights for analysis and reporting.
• Google Pay: Updated multiple microservices to support Google Pay billing and notifications, enabling seamless system-wide processes.
• Checkout: Support has been added for one-off payments using Google Pay on the checkout page, delivering a secure and seamless payment experience.
• Internal Platform Updates: Functionality has been streamlined to simplify the setup and configuration of pricing and payment methods for GCash, Apple Pay, and Google Pay, allowing for more efficient management by internal teams.
• Pay Now: The message displayed on the Pay Now page has been improved to provide clearer information when a link is accessed after an invoice has been written off.
• Payment API: The number of polling attempts has been increased to 25, enhancing overall transaction reliability and performance.
• Active Subscriptions: Subscription editing has been enhanced to accommodate changes to intervals, making it easier to manage subscriptions.

Fixes

• Vault Bug Fix: Resolved an issue with vault making unauthorised calls to the billing service, ensuring proper access and functionality.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

We're heading towards the end of the year but are still working to deliver fixes and enhancements in our system.

Enhancements

• Vault service upgrades: Updated to newer versions of Java and Spring to enhance security, performance, and compatibility.
• Google Pay integration: Updated multiple microservices to future support billing and payment processing via Google Pay, ensuring seamless transactions across supported platforms.
• Refund policy update: In accordance with payment processor regulations, refunds for New Zealand card payments are now restricted to transactions made within 60 days of the original payment date.
• Customer Reference Number (CRN): The Settlement CSV and Merchant Transaction Reports have been enhanced to include the Customer Reference Number Field.

Fixes

• Ledger imbalance fix: Resolved an issue causing incorrect amounts to be generated for Ezypay revenue payment invoices, ensuring accurate ledger balances.
• Checkout payment fix: Resolved an issue where components of the checkout page failed to load, ensuring a seamless payment experience.
• Internal Systems Notifications: The "download attachment" feature has been fixed to be available for more than 24 hours.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

Here are the updates on fixes and enhancements in our system.

Enhancements

• Pricing & revenue: Updated the status to "Insufficient" instead of "Transferred" when the calculated pricing value is zero, ensuring more accurate reporting records.
• List pricing API: Enhanced to support displaying pricing data for newly added payment method types.
• Payment method configuration: Added support for listing GCash, Apple Pay and Google Pay as part of a merchant's accepted payment methods.
• Payment methods enablement: New payment methods are no longer automatically enabled by default for both existing and newly created merchant accounts.
• Payment method refactoring: We ensured that the payment method type matches the key used in the pricing API to prevent fee pricing retrieval issues and standardise the retrieval of payment method types.
• Customer & merchant emails: We've enhanced this feature to display accurate and relevant data for new payment methods in existing customer and merchant emails.
• Ledger services: Upgraded the ledger service to a newer Java version for improved performance and compatibility.
• Mastercard Tokenisation: Implemented changes based on updates from Mastercard regarding the handling of callback statuses.

Refinements

• Input validation: The payment amount field has been fixed to only accept numeric values.

Fixes

• Pricing and reporting: Resolved an issue where a bug in pricing and revenue calculations prevented settlement reports from being emailed to merchants.
• Pricing display: Resolved an issue causing duplicate items to appear in the pagination when listing certain pricing configuration items on the internal platform.

New Features

• Payment Processor ID: Internal users can now add, edit, and view, relevant payment processor details associated with a merchant. This enhancement improves the management of payment processing IDs, ensuring transactions are routed accurately through the correct accounts.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.

Small tweaks, big impacts. Here are some details about our latest product enhancements and refinements.

Enhancements

• Merchant names in pricing: The pricing component now displays the merchant trading name for easier and more accurate identification by internal admin users.
• GCash hosted page: The requirement to whitelist merchants using GCash on the hosted payment page has been removed, simplifying the integration process.

Here at Ezypay, we are committed to continually enhancing our products and services to serve you better. Your feedback is invaluable to us, so please let us know if you have any questions or comments on this week's updates.