Release notes: Banking.Live 2.25

MAND-368 & AUTH-1150: Assigning new leading indicators to AAV for Smart Authentication Direct Services

In line with Mastercard Mandate GLB 10437.2 (Assigning New Leading Indicators to the Accountholder Authentication Value (AAV) for Smart Authentication Direct Services).

Banking.Live now provides support for:

• Supporting AAV leading indicator kJ for successfully authenticated Smart Authentication Direct transactions with Security Level Indicator (SLI) 212.
• The kJ leading indicator will replace the current kC leading indicator shared between Smart Authentication Direct and Smart Authentication Stand-In. Smart Authentication Stand-In low-risk will solely generate the kC leading indicator.
• Supporting AAV leading indicator kU for successfully authenticated SADAE (Smart Authentication Direct Acquirer Exemption) transactions with SLI 216.

This is applicable to Issuers participating in the Mastercard Identity Check program that are enrolled or have opted-in to SADAE.

Applicability

Enablement

No enablement required.

If you require further information you can refer to the Mastercard Mandate bulletin GLB 10437.2 or reach out to your Client Executive.

Technical info

AAV leading indicator fields/values:

Authorization:

• kJ in DE 48, subelement 43, positions 1 and 2 for successfully authenticated Smart Authentication Direct transactions with SLI 212.
• kU in DE 48, subelement 43, positions 1 and 2 for successfully authenticated SADAE transactions with SLI 216.
• The AAV will not be sent in Authorization Request/0100 messages to the Issuer when a transaction is downgraded.

Clearing:

• kJ in PDS 0185 for successfully authenticated Smart Authentication Direct transactions with SLI 212.
• kU in PDS 0185 for successfully authenticated SADAE transactions with SLI 216.

PECP-555: View transaction detail by double-clicking on the transaction row

You can now double-click on a transaction on PayControl to open the transaction detail pop-up screen. Previously, you could only open this pop-up screen via right-click.

Applicability

PECA-681: Enable sending of failed TAR notifications

For clients using Paymentology tokenization notification services, you can now opt-in to receive Tokenization Authorization Request (TAR) notifications where the AuthorizeService has failed.

These notifications will include detailed risk & device or error information for any AuthorizeService failures such as those that fail due to the deviceScore = 01.

You can read more on tokenization notifications here.

Applicability

Enablement

If you are a Paymentology tokenization client and wish to receive failed TAR notifications, please speak with your Client Executive.

DEFECT-1319: Addition of new product flag relating to ASI transactions

We've introduced the product flag “enable_asi_constraint_for_tid”.

When this product flag is enabled the Transaction Identifier (TID) will be unlinked (creating a new TID) if a pre-auth transaction attempts to link to an original transaction (by trace ID) that is an Account Status Inquiry (ASI) transaction.

Please note: this product flag is disabled by default for existing clients.

Applicability

Enablement

No enablement required.

If you wish to have this product flag enabled, please reach out to your Client Executive.