UI Enhancements:
- Brand Enhancements – Introduced the new ‘My Brand’ section, which contains brand details.
The existing ‘My Brand’ area has been divided into two sections: ‘Brand Styles’ and ‘My Brand’. The ‘Brand Styles’ section has been blurred for brand users who cannot parameterise the styles. This includes users who do not have a domain and are not main users. The ‘My Brand’ section aligns with information at a brand level.
Impacted Functionality: Brand configuration.
- Non-highlighted options in the brand “Sub-Menu” are now highlighted.
When you click on the sub-menu options in the Brand ‘Sub-Menu’, all options are now highlighted.
Impacted Functionality: Brand configuration.
- Added new service – Paypal classic – Field label names are misaligned.
Updated the Paypal service connection labels from “Client ID” to “Username”, and “Secret Key” to “Password”. These changes ensure alignment with the official Paypal labels.
Impacted Functionality: Paypal gateway configuration.
- When toggling between “Pre-Auth” and “Direct” payment type options, the “Gift Card” tab is now consistently displayed with the “By Smart Routing” option in the “Payment Information” section.
Made minor changes to ensure that the “Gift Card” tab displays correctly when switching payment types. This enhances the user’s experience.
Impacted Functionality: The “Gift Card” tab in the “Payment information” section.
- Implemented a fix to ensure that the appropriate default initialization source (MOTO) is sent to the gateway when an authorised charge is created from the dashboard using a Session Vault Token.
Previously there was an issue where an incorrect initialization source was sent when a session vault token was used to create an authorized charge through the dashboard. This has been resolved.
Impacted Functionality: Charge creation.
- Implemented a fix in the UI to ensure that when companies have over 100 gateways, all additional gateways are connected and loaded in the dashboard.
Impacted Functionality: Dashboard (gateway services).
API Enhancements:
- Block the use of Session Vault Token for gateways that require PAN for refunds.
Blocked the use of Session Vault Token for gateways (EFTPOS, VII & DCI) that require PAN for charge refunds.
Impacted Functionality: EFTPOS, VII & DCI Gateways. Charge processing through session vault.
- GooglePay Wallet Contract refactoring.
Refactored the GooglePay wallet contracts so that they align with the Paydock contracts’ standard. This creates consistency among the wallet endpoints.
Impacted Functionality: GooglePay wallet.
- ApplePay Wallet Contract refactoring.
Refactored the ApplePay wallet contracts so that they align with the Paydock contracts’ standard. This creates consistency among the wallet endpoints.
Impacted Functionality: ApplePay wallet.
- Cybersource – REST API Digest Parentheses Removal (REST HTTP Signature).
Removed the parenthesis from the headers of API calls to Cybersource for all Paydock supported flows related to the Cybersource service. This ensures that it is compliant.
Impacted Functionality: Cybersource.
- Updated the error message that is returned when an attempt is made to create a charge using a vault token that does not have a gateway_id.
Updated the error messages that are returned when an attempt is made to create either a charge (direct, authorized, 3DS inbuild), or a standalone refund, using a vault token created without a gateway_id.
Impacted Functionality: Charge creation.
- Enhancement for 3DS Charge response fields with “Null” values.
Removed the fields below from the fields available in charges response to ensure consistency & alignment as these fields currently always return “null” as their values.
- data.amount_original
- data.amount_surcharge
- data.transactions.amount_fee
Impacted Functionality: MPGS.
Widget Enhancements:
- Enhancement for Paypal: Learn more Messaging and single button display.
Introduced a new meta parameter “standalone” for Paypal wallets. This enables merchants to display either the Paypal button, or the Paypal Pay in 4 button (with the Learn more Messaging). The new meta parameter can be set to either “true” or “false”.
Impacted Functionality: Paypal.
