Changelog – Release 102

API Enhancements:

• Added support for customer.payment_source.card_funding_method & card_issuer (EFTPOS)

Enhanced EFTPOS Charge object with customer.payment_source.card_funding_method and customer.payment_source.card_issuerfields based on BIN data. Enabled merchants to see new fields as part of reporting.

Impacted Functionality: Charges

• Introduced AccountType field in charge and account verify requests (EFTPOS)

Introduced the ability to pass AccountType field for EFTPOS when making an account verify or payment request, to allow merchants to specify the type of account rather than always sending the default value. The AccountType field has possible values: savings, cheque, default.

Impacted Functionality: Charges

• Introduced support for passing order.certainty field for Authorization Request

Introduced the ability for merchants to pass order.certainty parameter for Authorization request (charges?capture=false) as an optional parameter. The order.certainty field has possible values: ESTIMATED, FINAL.

Impacted Functionality: Charges

• Fixed Incorrect storedOnFile Value in Subscription Refunds via MPGS gateway

This ticket addresses a bug where MPGS subscription refunds incorrectly send the storedOnFile value as NOT_STORED instead of STORED. Ensuring compliance with MPGS expected behavior

Impacted Functionality: Subscription, MPGS

.

UI Enhancements:

• Corrected Message for Deleted Standalone 3DS Service on UI

Resolved an issue where an incorrect “is a required property” message was displayed under the GPayments dropdown in the Checkout configuration when a previously selected Standalone 3DS service was deleted. The system now correctly shows “Archived service selected” in such instances, providing clearer user feedback.

Impacted Functionality: Checkout

.

Widget Enhancements:

• Click to Pay Performance Optimization & remote-app enhancement

Enhanced the optimization pattern for the Click to Pay SDK, enabling background loading and deferred customer data injection. This means merchants can now load the SDK concurrently with other checkout processes, leading to noticeably improved perceived performance and a smoother user experience for your customers.
This enhancement includes:

1. Optimized Click to Pay Initialization: The underlying initialization process for Click to Pay has been refined to boost its loading speed.
2. Background Loading using hold_for_customer_data: This new parameter enables the Click to Pay SDK to load in the background, allowing merchants to parallelize SDK initialization with their checkout flow.
3. Deferred Customer Data Injection using injectCustomerData: This method allows for customer data to be injected later in the Click to Pay flow, supporting the new optimization pattern.

Also, implemented an enhancement to further simplify Click to Pay merchant developer experience and ensure we have only one approach for our iframe instead of two separate iframe rendition methods

Impacted Functionality: Click to Pay, Client SDK