API Enhancements:
- Enhanced the Single Sign-On functionality and extended the functionality to other levels
The existing Single Sign-On functionality that was previously available only for the “Merchant“ (Company level) has been enhanced and extended to other levels. Merchants can set up the Single Sign-On functionality. For example on the “Brand” level brand users can sign-on using this functionality.
The Single Sign-On only impacts the scope (level) where it was initially configured.
Merchants can update the Single Sign-On setup through either the Dashboard or contacting the support team.
Impacted Functionality: Single Sign-On functionality, Sign in Open
- Introduced the reference field at the transaction level for refunds for Flypay v2
Introduced the reference field at the transaction level for refunds for Flypay v2. This ensures that the reference provided for the merchant’s refund requests are saved in this field instead of in the transaction.external_reference field at the transaction level.
Impacted Functionality: Flypay v2 and all other gateways
- Stopped the triggering of the ‘transaction_sync’ process for charges with 3DS
Stopped the triggering of the ‘transaction_sync’ process for charges with 3DS and active fraud without payments.
Impacted Functionality: Backend Charges
- Updated the error message for ‘invalid format of ID’ for charges and gateways
Enhanced the error messages for ‘Invalid Format ID’ to avoid showing underlying technology.
Impacted Functionality: Backend Charges
- Restricted the refund for charges in the ‘refund_requested’ status
Restricted refunds for charges in the status ‘refund_requested’.
Impacted Functionality: Refunds
- Enhanced the error message for check-balance when using incorrect gateways
Enhanced the error message for check-balance when using incorrect gateways where before there was only a 500 error.
Impacted Functionality: Check Balance
- Enhanced the validations to prevent capture for cancelled pre-authorisations
Enhanced the validations to prevent capture for cancelled pre-authorisations for gateways without Auto-void.
Impacted Functionality: Charges
- Fixed the behaviour for the remediation endpoint for the customer payment source expiration warning
Fixed the remediation endpoint for the expiration warnings.
Impacted Functionality: Notifications
- Changed the FatZebra reference field mapping
Changed the FatZebra reference field mapping.
Impacted Functionality: Charges
- Fixed the mapping for the rejected responses for FatZebra
Fixed the mapping for the rejected responses for the FatZebra Bank Direct Debit integration. Previously Paydock was not mapping the rejected responses from FatZebra correctly, which resulted in the Paydock status displaying as ‘completed’ but the gateway status displaying as ‘rejected’.
Impacted Functionality: Charges
- Introduced the Cancel transaction by ID endpoint for the Stripe service
Created the Cancel transaction by ID endpoint for the Stripe integration to enable the successful cancellation of a Capture transaction action when it is marked as “Failed” or “Pending”.
Impacted Functionality: Stripe Cancel Charge logic
Widget Enhancements:
- Removed the old Zip logo from the Zip widget
Removed the old Zip logo from the Zip widget to ensure compliance with Zip branding guidelines.
Impacted Functionality: ZipMoney
UI Enhancements:
- Upgraded the currencies library in the UI to the latest version to ensure only valid currencies are used
Upgraded the currencies library in the UI to the latest version to ensure only valid currencies are used. Previously there was a discrepancy in the currency list on the front end and this has been resolved.
Impacted Functionality: Front-End Charges
- Amended the wording of the Rules toggle
Amended the wording for the Rules Toggle to clarify when the Rules are enabled or disabled.
Impacted Functionality: Rules Engine
- Fixed the navigation between the charges and transaction level templates
Fixed the issue that occurred while navigating between the charges and transaction templates in Brand level reporting so merchants do not need to refresh the page.
Impacted Functionality: Transactions
- Resolved the incorrect spelling of the In-Progress status
Fixed misspelling of ‘In-Progress’ status, which was previously ‘In-Progres’.
Impacted Functionality: Transactions
- Enabled both the Transaction and Charge level fields to be displayed in the UI simultaneously
Enabled both the transaction and charges fields to be displayed in the UI at the same time.
Impacted Functionality: Transactions
- Improved the validation errors for ‘Custom Fields‘
Improved the validation errors for ‘Custom Fields’ when creating charges.
Impacted Functionality: Transactions
