API Enhancements:
- Introduced blocking of capture for failed Flypay v2 orders
Implemented an enhancement to prevent the capture of failed Flypay v2 orders, ensuring merchants cannot capture such orders.
Impacted Functionality: Flypay v2
- Enabled cancelation of Flypay v2 charges in “wallet initialized” status
Enabled merchants to cancel Flypay v2 charges in “wallet initialized” status, preventing abandoned wallet charges.
Impacted Functionality: Flypay v2
- Enabled the GPayments configuration with Master Merchant Accounts
Implemented a fix to enable Brands or Master Merchant accounts to configure the GPayment service.
Impacted Functionality: GPayments
- Validated GPayments standalone 3DS request
Introduced validation to ensurecustomer.payment_source.address_country
&shipping.address_country
are provided whencustomer.payment_source.address_state
&shipping.address_state
are provided for standalone 3DS request to GPayments.
Impacted Functionality: Gpayments
- Stored
shipping_amount
for Paypal
Implemented an enhancement for Paypal Vaulting to store theshipping_amount
within the shipping object for charge requests.
Impacted Functionality: Paypal gateway (Paypal Vaulting)
- Enhanced Customer Email for Paypal Vaulting
Implemented an enhancement to prevent the Customer “Email” from being overridden by the email returned inPayPalSavePaymentSourceOTT
during customer creation or modification.
Impacted Functionality: Customer
- Enhanced COF Field for subscriptions with Network Token (SCoF and VTS)
Enhanced subscription processing with Network Tokens (SCoF and VTS) by ensuring the correct Credential on File (COF) fields are sent to the MPGS gateway.
Impacted Functionality: Subscription
- Validated required fields for AfterPay v2 init wallet charge
Implemented validation for the requiredaddress_line1
andaddress_postcode
for initialize wallet charge requests with Afterpay v2.
Impacted Functionality: Afterpay v2
- Ensured consistency in the values stored and sent to Paypal
Implemented a fix to ensure the itemsamount
stored at the charge level is consistent with theitem_total
value sent to PayPal.
Impacted Functionality: Paypal Smart Buttons
- Enhanced logs to tracking Network Token issues
Extended logs with “Process Error Codes” and “Process Error Code Description” to simplify troubleshooting Network Token creation.
Impacted Functionality: Network Tokenisation
- Fixed fallback for deleted Network Tokens
Ensured Vault charges with deleted Network Tokens correctly follow the card flow.
Impacted Functionality: Network Tokenisation
- Improved error handling for Network Token Failover
Extended failover functionality to handle internal errors (not only scheme-related) ensuring reliable Network Token provisioning flow.
Impacted Functionality: Network Tokenisation
Widget Enhancements:
- Improved performance and reliability for the Payment Form widget
Enhanced the Payment Form widget by reducing redundant API calls, modernising token generation, improving load times and reliability while maintaining backward compatibility with legacy features. Deprecated mechanisms were removed to streamline maintenance and enhance security.
Impacted Functionality: Client SDK - Added asterisks to the “Mobile Number” field for Click to Pay
Implemented a fix to display the mandatory “Mobile Number” field with an asterisk and ensure the pre-filled mobile number appears correctly in the widget UI.
Impacted Functionality: Click to Pay
- Enhanced PayPal DataCollector widget
Implemented a fix to ensure that the widget initializes correctly even when the optional config (let payPalDataCollector = new paydock.PayPalDataCollector()
) is not present in PayPalDataCollector.
Impacted Functionality: PayPalDataCollector
- Added control for Paypal Paylater messaging display
Enabled merchants to control the display of the “Paylater messaging” for both the regular Paypal Paylater button & Paypal express checkout Paylater button.
Impacted Functionality: Paypal & Paypal Express Checkout