API Enhancements:
- Fixed InProgress Charge for Checkout + capture=false
Fixed the issue of the Afterpay v1 authorized charges being stuck in “in progress” status when the unsupported cancel operation is attempted, ensuring that the charge fails instead. This change was also replicated for other affected gateways.
Impacted Functionality: Afterpay, Authorize, Brain, Eway, Ezidebit35, Ezidebit, FatZebra, Flo2Cash, Forte, IpPayments, Merchantwarrior, Nab, Paperless, Payeezy, Payment express, PaypalClassic, PaywayRest, Pin, PromisePay, Securepay, Sqid and Worldpay
- Updated the “Reference” field for wallet Charges
Introduced support for merchants to be able to update the “reference” field for wallet charges using the POST /v1/charges/:id endpoint and also ensured that the reference field is stored at the charge level.
Impacted Functionality: Wallets (Paypal, Afterpay v2, GooglePay, ApplePay, and Flypay v1 & v2)
- Enhanced Report Settings configuration
Introduced report generation settings with the ability to select delimiter character, file type and quoted settings to provide merchants with more control over the report generation settings.
Impacted Functionality: Charge Reports
- Updated Report Limit change from 5 to 20
Extended report limit from 5 to 20 to provide merchants with the ability to create multiple reports simultaneously.
Impacted Functionality: Charge Reports
- Implemented UNHRC changes for custom fields
Introduced enhancement for New Zealand UNHCR to pass charge_id and transaction_id in customer fields 1 and 2 for Merchant Warrior.
Impacted Functionality: Custom Fields (Merchant Warrior)
- Fixed FatZebra Bank Account Vault Token as New Payment Source
Fixed issue whilst creating new Payment Source for FatZebra as Bank Account.
Impacted Functionality: Payment Sources
- Changed url and port for internal MS communications
Changed the use of hardcoded configuration to environment configurations.
Impacted Functionality: Services and api-Core Micro-services
- Enhanced ‘Invalid Card Number’ error message for Standalone Refunds
Enhanced error message for standalone refunds.
Impacted Functionality: Standalone Refunds
- Added New Relic logging for the charges with Vault Token
Added New Relic logging to the flow of creating a charge with a vault token. This is for both session and permanent vault, and ensures that it is possible to track ‘in progress’ charges in the future and identify the root cause of the issue.
Impacted Functionality: Analytics
- Added refund service logs for eWay
Added logs for refunded charges created after a direct charge.
Impacted Functionality: Analytics
- Added the field ‘resource.data.status’ in the customer’s logs that were created through a one-time token
Resolved an issue where the resource.data.status field was missing for customers created through a one-time token. The status field properly reflects customer status, ensuring data consistency.
Impacted Functionality: Customers
- Resolved unauthorized modification caused by mismatched vault tokens
Addressed issue where it was possible to modify a customer’s payment source with a new vault token that differed from the stored one. Now, if a mismatch occurs, an error message prompts merchants, ensuring data integrity and preventing unauthorized modifications.
Impacted Functionality: Customers
- Updated error messages for invalid ID formats across customer, subscription, and vault endpoints
Updated error messages for invalid ID formats across customer, subscription, and vault endpoints, enhancing usability and reducing confusion during troubleshooting.
Impacted Functionality: Customers, Subscriptions, Vaults
- Updated card_used flag for Subscription creation
Updated the card_used flag during subscription creation, enabling accurate tracking of card usage and enhancing subscription management.
Impacted Functionality: Subscriptions
- Unblocked Bank Account Exchange to Session Vault Token
Removed restrictions preventing the exchange of bank accounts into Session Vault Tokens and enabled the use of bank accounts for payment operations.
Impacted Functionality: Vaults
Widget Enhancements:
- Implemented Paypal onClick handler
Implemented and exposed a new wallet SDK callback. Merchants can execute custom logic after the Paypal button is clicked and return a boolean flag to indicate whether the consumer can continue to make a payment or not.
Impacted Functionality: Paypal
- Introduced ClosePopup Event Handling
Introduced support for the onCheckoutClose event for wallets, Paypal, Apple Pay, and Google Pay, to ensure that merchants are aware that a customer has closed the wallet popup.
Impacted Functionality: Paypal, Apple Pay, and Google Pay
- Implemented Onclick event handling for Apple Pay and Google Pay
Implemented support to allow for validations to be run on button click through an onclick callback. If validation fails for a wallet button, the wallet flow can be aborted by the merchant.
Impacted Functionality: Apple Pay, and Google Pay
UI Enhancements:
- Resolved visibility issue for the “Update Subscription” button
Fixed the visibility issue of the “Update Subscription” button on the Subscription Details page, ensuring it is always visible for an improved user experience.
Impacted Functionality: Subscriptions
- Corrected error when front-end report creation fails
Corrected the error returned when the creation of a report fails in the UI. This is now shown as a pop-up message.
Impacted Functionality: Reporting
- Fixed error in the console for the card number field on Add new charge
Fixed the error appearing in the console for the card number field on the ‘Add New Charge’ page.
Impacted Functionality: Charges
- Fixed error message when not populating custom fields
Fixed error message when custom fields are not populated and they are required.
Impacted Functionality: Charges
Security Patches
- Standard security update: Rework startup validation script
