Changelog

• PRODUCTION RELEASE DATE: 04/12/2024
• SANDBOX RELEASE DATE: 20/11/2024

Go to Release notes 90

API Enhancements:

• Extended /standalone-3ds, /3ds, /refunds, /fraud, /verification endpoints with customer_id and customer.payment_source_id

Enhanced the following endpoints to accept customer_id or payment_source_id as the source for payment:

• {{url}}/v1/charges/fraud
• {{url}}/v1/charges/standalone-3ds
• {{url}}/v1/charges/3ds
• {{url}}/v1/charges/verification
• {{url}}/v1/charges/refunds

Impacted Functionality: Standalone refunds, Charges, Verification, Fraud, 3DS

• Extended /3ds endpoint with optional challenge preference request parameter

Introduced a new optional field to {{url}}/v1/charges/3ds with supported values:

• CHALLENGE_MANDATED
• CHALLENGE_PREFERRED
• NO_CHALLENGE
• NO_PREFERENCE
• REQUEST_TRUSTED_MERCHANT_LISTING

This enhancement gives merchants control of how 3DS challenges are handled during a transaction, offering greater flexibility over the customer experience.

Impacted Functionality: 3DS

• Added status_code and status_code_description fields to transaction and error summary (Verification API)

Added status_code and status_code_description to transaction object and error summary in the response for /v1/charges/verification, offering further details on the occurred error.

Impacted Functionality: Verification

• Enhanced the error summary for Vii integration (Check Balance)

Enhanced the error message for Check Balance endpoint and response code = 9 from Vii when the card is temporarily locked: "The card has been temporarily locked. It will be unlocked on {{LockoutEndTime}}".

Impacted Functionality: Vii

• Enhanced the error message for not yet attached to the bulk charges

Introduced new status code = 409 and error message = "Charges in request do not match attached charges in bulk: {:bulk_reference}" when not yet attached to the bulk charges passed:

• {{url}}/v1/bulk-charges/:bulk_reference/cancel
• {{url}}/v1/bulk-charges/:bulk_reference/capture
• {{url}}/bulk-charges/:bulk_reference/fraud
• {{url}}/v1/bulk-charges/:bulk_reference/refund

Impacted Functionality: Bulk Charges

• Resolved missing the payment source ID in the ‘Customer Card Expiration Warning’ webhook event

Added the missing paymentsourceID field in the “Customer Card Expiration Warning (-1 month)” webhook event, ensuring that all customer and payment source fields are included in notifications by default.

Impacted Functionality: Notifications

UI Enhancements:

• Introduced Overwrite toggle for Customer Info

Introduced the "Enable Customer Information Overwrite" checkbox for the PayPal gateway, enabling merchants to replace consumer information with payer details retrieved directly from the PayPal wallet at the charge level.

Impacted Functionality: Paypal

Widget Enhancements:

• Enhanced widget to perform Luhn Check on Name Field before submission

Updated the Payment Widget to perform a local Luhn check on the Cardholder Name; Billing details → First Name; and Billing details → Last Name fields before submission, further enhancing security.

Impacted Functionality: Widget

• Restricted archived gateways for widget initialization

Restricted the usage of archived gateway for widget initialization, supported by the error message: Provide gateway_id or set default gateway.

Impacted Functionality: Widget

• PRODUCTION RELEASE DATE: 30/10/2024
• SANDBOX RELEASE DATE: 13/11/2024

Go to Release notes 89

API Enhancements:

• Updated URL for Pin Payments

Updated domain for Pin Payments from pin.net.au to newly migrated pinpayments.com.

Impacted Functionality: Pin Payments

• Implemented timeout for MastercardSCoF Enroll Card API

Implemented a 5-second timeout wait period to further enhance the reliability of the MastercardSCoF (Network Token) enrolment process, accounting for potential latency in the response from Mastercard.

Impacted Functionality: Network Token (MastercardSCoF)

• Improved the subscription retry logic

Updated the subscription logic to resolve an issue with single retry failures, ensuring retries function correctly and reducing failed charges for merchants.

Impacted Functionality: Subscriptions

UI Enhancements:

• Removed support for Discover cards from Click to Pay

Removed the "Discover" card scheme from the list of supported schemes for Click to Pay as the Discover scheme has exited Australia.

Impacted Functionality: Click to Pay

• Improved Mastercard SCOF registration on UI

Resolved a bug that incorrectly made AcquirerData fields mandatory when creating a Mastercard SCOF registration via the UI.

Impacted Functionality: Mastercard SCOF, Registrations

• Implemented logic to schedule the Next Report iteration for Recoverable Errors

Introduced error categorisation for Reporting into “Recoverable” and “Non-Recoverable” errors, with automatic scheduling of the next report iteration for all Recoverable errors instead of Failing the report. This enhancement improves the reliability of our reporting system and reduces the need for manual intervention.

Impacted Functionality: Reporting

• Added “Service” and “Service Name” fields in the Subscriptions service

Fixed an issue where “Service” and “Service Name” fields were not displaying when filtering by “Subscription ID.” This fix ensures the gateway_type and gateway_name are transmitted from the backend as expected, restoring consistency in displayed data.

Impacted Functionality: Subscriptions

• Added missing “Vault Token Reference” and “Vault Type” fields to Vaults CSV download

Resolved an issue where the Vault Token Reference and Vault Type fields were missing from the Vaults CSV download. These fields are now included in the exported CSV, providing merchants with complete vault data.

Impacted Functionality: Vaults

• Fixed acceptance pop-up duplication on the UI

Fixed the issue causing a double “Accept/Decline” message to appear when the user first logs into UI.

Impacted Functionality: Dashboard

Widget Enhancements:

• Enhanced the Click to Pay widget UI

Implemented a fix to ensure the Click to Pay modal window DCF screen and Learn More messaging are centralised.

Impacted Functionality: Click to Pay

• Resolved issue with rendering payment sources for removed customers in the Payment Sources widget

Fixed an issue where payment sources remained visible in the widget after a customer was deleted. Now, when a customer is removed, all associated payment sources are properly cleared.

Impacted Functionality: Payment Sources Widget

• Resolved issue with direct report for a specific template not working

Fixed an issue where the direct report for a specific template didn’t work as expected and was failing or stuck loading.

Impacted Functionality: Reporting

• PRODUCTION RELEASE DATE: 23/10/2024
• SANDBOX RELEASE DATE: 9/10/2024

Go to Release notes 88

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:

1. Added recognition tokens to Click to Pay SDK calls.
2. Exposed recognition token events to merchants for them to handle.
3. Supported the injection of recognition tokens into CtP SDK widget initialization for merchants.
4. 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:

1. recognitionTokenRequested event: triggered upon the completion of the checkout process by consumers.
2. recognitionTokenDropped event: 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

• PRODUCTION RELEASE DATE: 2/10/2024
• SANDBOX RELEASE DATE: 19/9/2024

Go to Release notes 87

API Enhancements:

• Improved the resending of notification logs

Introduced a solution to ensure the resending of the email notification from the notifications log list to a different destination (email) is correct.

Impacted Functionality: PUT /v1/notifications/logs/:id endpoint

• Introduced the configuration of AU phone numbers for VISA Click to Pay

Implemented a solution to ensure the configuration of AU phone numbers for Visa profiles in Click to Pay, with proper format validation.

Impacted Functionality: Click to Pay

• Improved the logic for Click to Pay refunds sent to MPGS

Implemented a solution to ensure that the storedOnFile value "Stored" is correctly sent to the MPGS gateway for Click to Pay charges refunds.

Impacted Functionality: Click to Pay

• Improved the Cryptogram logic for VISA C2P payments via MPGS gateway

Implemented a solution to prevent the missing onlinePayment Cryptogram error when processing Visa cards added to Click to Pay profiles via MPGS.

Impacted Functionality: Click to Pay

• Removed PAN detection validation in the Reference field

Removed Luhn checks from reference, reference2 and reference3 fields in charge requests to prevent merchants from encountering validation errors.

Impacted Functionality: Charges

UI Enhancements:

• Improved the Subscription ID search in Paydock Dashboard

Implemented a solution to ensure subscriptions are correctly displayed when searched by Subscription ID in the Paydock dashboard. This resolves the issue where valid subscriptions were not appearing in search results, eliminating the need for manual workarounds.

Impacted Functionality: Subscription - UI section

• PRODUCTION RELEASE DATE: 21/8/2024
• SANDBOX RELEASE DATE: 12/8/2024

Go to Release notes 85

API Enhancements:

• Unified error summary details messages

Implemented a unified structure for error summary as documented in API Documentation. Potential impact on those customers processing the response for the endpoints below where the structure will change.

AS-IS:

Code Block
"error_summary": { "message": "Invalid Transaction Details", "code": "invalid_transaction_details", "details": { "messages": [ { "gateway_specific_code": "9", "gateway_specific_description": "Invalid PIN", "description": "Invalid Transaction Details", "status_code": null, "status_code_description": null } ] } }

TO-BE:

Code Block
"error_summary": { "message": "Invalid Transaction Details", "code": "invalid_transaction_details", "details": { "gateway_specific_code": "9", "gateway_specific_description": "Invalid PIN", "messages": [ "Invalid Transaction Details" ] } }

• Create charge
  • POST /v1/charges
    • Using vault-token with fraud object in request body
    • Using customer from gateway (ref_token)
    • Process charge with pre-auth 3DS (for TillPayments gateway)
    • Using OTT (for TillPayments gateway)
• Get balance
  • POST /v1/charges/balance
• Standalone refund
  • POST /v1/charges/refunds
• Verification
  • POST /v1/charges/verification
• Dynamic pricing
  • POST /v1/charges/dynamic-pricing
• Standalone 3DS
  • POST /v1/charges/standalone-3ds
• Pre-auth 3DS (using vault token)
  • POST /v1/charges/3ds
• Finalize and decline fraud charge in status inreview
  • POST /v1/charges/:id/process
  • POST /v1/charges/:id/decline
• Create OTT (VisaSRC)
  • POST /v1/payment_sources/tokens
• Gateway account
  • POST /v1/gateways/:gateway_id/accounts
  • POST /v1/gateways/:gateway_id/accounts/:id
• Customers
  • POST /v1/customers - only for creating a customer with payment destination (body.payment_destination)
  • POST /v1/customers/:id - only for updating a customer with payment destination (body.payment_destination or body.default_payment_destination)
• Customer payment source
  • POST /v1/customers/:_id/payment_sources/:_payment_source_id/verify - verify customer payment source
• Services
  • POST /v1/services/:id/verify - update service credentials (only for service.group = 3ds)
  • POST /v1/services/:id/generate-access
• Transfers
  • POST /v1/transfers/:id/capture

Impacted Functionality: Error messages

• Increased key maximum expiration from 90 days to 1 year for “global” scope

Changed maximum expiration date for all keys from 90 days to 1 year for “global” scope.

Impacted Functionality: Keys

• Blocked the exchange of Click to Pay OTT into permanent vault tokens, customers, and subscriptions

Blocked the exchange of Click to Pay OTT into permanent Vault tokens, customers, and subscriptions flows. This is to ensure customers do not use the Click to Pay OTT (FPAN/Card scheme token), intended for one-off payments, for recurring payments.

Impacted Functionality: Click to Pay, Customer & Subscription

Widget Enhancements:

• Enhanced the Click to Pay Android OTP screen experience

Introduced a fix for the Click to Pay OTP screen to ensure proper alignment of information when a user switches the OTP receipt channel from Email to Mobile.

Impacted Functionality: Click to Pay

UI Enhancements:

• Enhanced "Signup" page flow with clarifying details

Improved the "Signup" page by adding a text reminder to indicate that users are in the signup flow, not the sign-in flow. We have also introduced the ability to return to the previous step for better user experience.

Impacted Functionality: Sign-up flow, Frontend

• Updated the text for File Settings → Quotes information icon in the Request Report functionality

Changed text for File Settings → Quotes information icon in the Request Report functionality from "When enabled, the quotes will be added to the field values in the report" to “When enabled, quotes (“) will be added to the start and end of each value in the report. Please enable this option if you expect delimiters to be populated in the report values to prevent interference with file formatting” to make it more descriptive and clear for merchants.

Impacted Functionality: Reporting