Product	Summary
Digital Acceptance	Early decline custom error code Saved payment method usage details Larger payload in the webhooks Temporary disable eftpos on Apple Pay Deprecated 3DS version 2.1.0 Refund Authorisations

Digital Acceptance

Early decline custom error code

Early decline occur when we have setup flow rules to decline a transaction prior to sending out the payment processor. By default the error_code is set to flow_decline when there is an early decline, we can now setup custom error codes to give you context on which flow rule caused the decline. This will help you determine the next call to action with for your system and customer.

We will support the following set of custom error codes, please work with us if you need more flow rules set:

Custom Error Code	Description
`flow_unsupported_card`	Declined because the card scheme is not supported, the customer has supplied a card scheme that is not supported
`flow_anti_fraud`	Declined because our fraud engine has considered this high risk and rejected the transaction
`flow_region_block`	Declined because the card is issued from a country that is not supported
`flow_bin_block`	Declined because the card is part of a BIN range that is not supported

Saved payment method usage details

There is a minor API enhancement that adds usage data to saved paymenth methods. This will enable you to know how often a payment method has been used or how recently it's been used. You can use this to display the most used payment method more prominently in their checkout.

We added support for four new fields to our get-payment-method API.

last_used_at - The date and time when this payment method was most recently used for any transaction
usage_count - How often this payment method was used for any transaction
cit_last_used_at - The date and time when this payment method was most recently used for a CIT transaction
cit_usage_count - How often this payment method was used for a CIT transaction

In addition to this, the buyers payment methods API has been updated to support the sorting of payment methods by these fields.

Webhook Enhancement

Our webhooks will support a larger payload. These payloads contain more of the important context, and are backwards compatible with the smaller payloads.

Apple Pay iOS 18 eftpos

We have disabled pure eftpos support in Apple Pay. This new feature introduced in iOS 18 allows customers to choose which scheme to use for a co-branded EFTPOS card. As support for this is limited in downstream connectors, this has been temporarily disabled until we are ready to introduce a feature to allow a merchant to configure the schemes they want to accept via Apple Pay.

Deprecated 3DS version 2.1.0

We updated our 3DS integration to ensure version 2.1.0 is no longer used for most schemes. The only scheme still
using 2.1.0 is UnionPay.

Refund Authorisations

As part of Mastercard and Visa scheme mandates refunds are now sent as authorisation requests. This will apply to the following payment methods, debit cards, credit cards, prepaid cards, Apple Pay, Google Pay and Click 2 Pay.

Approved refunds

If a refund authorisation is approved, the refund will appear on the cardholder's account in real time to provide notification that the refund has been accepted.

Declined refunds

If a refund authorisation is declined, the issuer has indicated that the cardholder's account is unable to receive credits, when this happens you will need to find an alternative method to refund your customer. These declines happen because:

the account is closed
the account is locked
the account is for a product that is unable to accept refunds, commonly seen in prepaid products