API Enhancements:
- Updated EFTPOS routing rules to enforce card type validation
Adjusted routing logic to ensure only debit cards with both global and EFTPOS processing networks are eligible for EFTPOS CNP routing. This prevents incorrect routing of credit cards and ensures compliance with EFTPOS standards.
Impacted Functionality: Rules, EFTPOS
- Implemented COF Standing Instruction Type support for Secure Pay
Implement mapping for COF in Secure Pay Gateway to adopt Secure Pay Release Changes. Paydock will automatically pass COF indicators to Gateway for subscriptions and one-off payments according to the schemes’ rules.
Impacted Functionality: Charges
- Fixed issue that is not possible to complete e2e charge flow with customer_id
Fixed an issue that is not possible to complete the e2e charge flow with customer_id when 3DS is part of the payment flow.
Impacted Functionality: Charges
- Introduced network_token_service_id for On Fly flows
Enabled merchants to explicitly pass network_token_service_id into the Charges API for On Fly flow, so that merchants who don’t have a default network token service enabled can benefit from On Fly flows as well.
Impacted Functionality: Charges
- Fixed issue that authorization (Capture=false) is going through, but then fails on capture (EFTPOS)
Fixed issue that authorization (Capture=false) is going through, but then fails on capture for EFTPOS Gateway.
Impacted Functionality: Charges
- Implemented storing of Correlation ID for all charges sent (EFTPOS)
Implemented logic to store Correlation ID for all EFTPOS Charges to simplify the troubleshooting process.
Impacted Functionality: Charges
- Enhanced MPGS 3DS to ensure the required data is retrieved and sent to Forter in the Order Status api call
Enhanced the MPGS 3DS authentication to retrieve additional data elements from MPGS and ensured that the required data is sent to Forter in the Forter Order Status call.
Impacted Functionality: MPGS 3DS and Forter
- Added Support for PayPal Vault Indicator Flags (Payment Initiator, Usage Pattern, and Usage)
Implemented support for merchants to be able to pass the newly introduced Paypal indicator flags (Payment Initiator, usage_pattern, and usage) for charges created with paypal vaulting as payment source
Impacted Functionality: Paypal Vaulting
.
UI Enhancements:
- Aligned validation for Capture between UI and API
Aligned validation rules between API and UI for Capture request, enabling merchants to capture the amount they choose to capture.
Impacted Functionality: Charges
- Added ‘Merchant Name’ field for Forter registration
Introduced a dedicated “Merchant Name” field in the Forter registration flow to ensure accurate business identification in Forter’s API, separate from the internal “Label” used for merchant reference.
Impacted Functionality: Forter service
- Merchant name character limit validation does not match API
Changed the maximum character limit to 256 up from 128 on the web-application when giving names to companies (merchants). This change was made to reflect the actual limit on backend servers.
Impacted Functionality: Merchant creation page
As a user being notified by email of successful transactions I want to know the gateway type and the transaction type
Added {{ GATEWAY_TYPE }} and {{ TRANSACTION_TYPE }} handlebar variables which enable users to know what gateway type and what transaction type is associated with the transaction, when these values are available.
Impacted Functionality: Email notification template forms
.
Widget Enhancements:
No enhancements in this release.
