API Enhancements:
- Enhanced the “card_used” flag
Enhanced the card_used flag for Vault Tokens to ensure the flag will no longer change from “false” to “true” for the following operations:
- MPGS in 3ds request
- Accertify standalone fraud
- Gpayments standalone 3ds
Now, only financial authorizations (direct charges; authorized charges) and verification will trigger changes to card_used.
Impacted Functionality: Vault Token
- Improved the handling of customer information for Paypal
Removed the auto-overwrite of the customer’s details (first name, last name, email, and phone number) sent in the wallet init request with customer information extracted from the Paypal wallet. This will ensure the customer information sent in the wallet init request is retained in the charge.
Impacted Functionality: Paypal (smart button)
- Improved error messaging when modifying Network Tokens with inactive/archived/failed status
Updated the error message for Edit Network Token API from “Network Token not in active/suspended status” to “The edit action is supported only for Network Tokens in active status” to improve clarity.
Impacted Functionality: Network Tokens
- Added validation preventing OTT creation with an expired card
Added validation preventing OTT (One-Time Token) creation with an expired card.
Impacted Functionality: OTT
Widget Enhancements:
- Implemented Recognition Tokens for Click to Pay
Introduced recognition tokens for Click to Pay to ensure consumer profiles will be remembered in case browsers stop supporting third-party cookies by utilizing recognition tokens used as first-party cookies. The implementation covers:
- Added recognition tokens to Click to Pay SDK calls.
- Exposed recognition token events to merchants for them to handle.
- Supported the injection of recognition tokens into CtP SDK widget initialization for merchants.
- Implemented functionality to delete recognition tokens when new consumers select
"Not you", "Not your cards", or a returning consumer unselect the"Remember Me"checkbox.
Please note this change will not impact merchants until browsers stop supporting third-party cookies. Merchants will then have to handle these events:
recognitionTokenRequestedevent: triggered upon the completion of the checkout process by consumers.recognitionTokenDroppedevent: occurs when new consumers click"Not you", "Not your cards"or returning consumers unselects the"Remember Me"checkbox.
Impacted Functionality: Click to Pay
- Ensured the SDK reinitialises upon “signOut”
Ensured the SDK reinitialises upon signOut to prevent cards from one Click to Pay profile from appearing in another profile within the same browser.
Impacted Functionality: Click to Pay
- Introduced “Remember Me” for New and Returning Users for Click to Pay
Introduced the “Remember Me” checkbox option for new and returning users for Click to Pay UI flows. Also, ensured the “Remember Me" flag is sent in the SDK calls to Mastercard for new and returning user flows.
Impacted Functionality: Click to Pay
UI Enhancements:
- Improved Vii Gateway connection on Sandbox
Fixed the error “merchant_settings.acquiring_institution_id: is missing but it is required" on Sandbox while connecting Vii Gateway.
Impacted Functionality: Vii
- Improved the Dashboard Graph accuracy
Resolved the issue with incorrectly calculated transaction numbers in the Dashboard Graph, ensuring the data displayed is now accurate.
Impacted Functionality: Dashboard
- Added ‘Bank Account’ UI tab for Fatzebra
Enabled the UI tab to use ‘Bank Account’ as the payment source when creating a charge with FatZebra gateway.
Impacted Functionality: Dashboard
- Added the feature for creating support tickets directly in Hubspot
Replaced the UI widget from HelpScout to HubSpot as part of our internal platform migration.
Impacted Functionality: UI Dashboard
- Improved the Dashboard Graph in Production
Fixed the issue where the Dashboard Graph failed to load for clients with large volumes of transactions.
Impacted Functionality: Dashboard
