Release notes: Banking.Live 2.27
AUTH-1127: VISA MANDATE: Visa click to pay with FIDO authentication
In line with Visa Mandate AI13856 (Notice to Europe Issuers of Visa Click to Pay with FIDO Authentication), Banking.Live will allow transactions to be approved if FIDO (Fast Identity Online Authentication) was performed.
For full details you can refer to Visa’s Mandate bulletins AI13856 and AI13104.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| Europe | Visa | Cards enabled for eCommerce transactions | Processing: eCommerce Authorizations |
Enablement
No enablement required.
Technical info
Banking.Live will handle these types of transactions and consider it as FIDO authenticated, when the
following values are present:
- 123 DSID 68 Tag 83 = 42 and ECI in (05,06)
Therefore, when these values are present Banking.Live will bypass the requirement for CVV2 to be present or 3DSecure authentication to be performed as FIDO authentication was performed.
AUTH-1146: VISA MANDATE: Changes to authorization response codes
In line with Visa Mandate TL 042025 2.11 (Changes to Authorization Response Codes (Version 2.0)),
Banking.Live now supports new response codes 5C and 9G.
For Visa clients, mapping between some reason codes and response codes will be different.
For full details you can refer to Visa’s Mandate bulletin TL 042025 2.11.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Visa | NA | Processing: Authorizations |
Enablement
Please make sure the new Visa response codes, and their mapping with reason codes, is supported by your system.
Technical info
For CNP transactions, the following reason codes will be mapped to different response codes compared to previously:
- CNP Reason Code 400 would be mapped to RC 5C
- Non-CNP Reason Code 400 would be mapped to RC 12
- CNP Reason Code 414 would be mapped to RC 9G
- Non-CNP Reason Code 414 would be mapped to RC 12
AUTH-1256: VISA MANDATE: Visa data only program
In line with Visa Mandate AI 14552 (Visa Secure Issuers Will Be Auto-Enabled for the Visa Data Only Program), Banking.Live now supports the bypassing of CAVV validation for Visa Data Share Only Program transactions via the enablement of a product flag.
For full details you can refer to Visa’s Mandate bulletin AI 14552.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Visa | Cards enabled for eCommerce transactions | Processing: Authorizations |
Enablement
If you wish to have this product flag enabled, please contact your Client Executive or raise a request via our Customer Support Platform.
Technical info
When the visa_data_share_only_cavv_bypassed product flag is enabled, Banking.Live will bypass
CAVV validation for Visa Data Share Only Program. Banking.Live identifies these types of transactions when the following values are present:
- Field 126.9, position 1 = 03 and CAVV 44.13 = B and ECI 60.8 = 07
AUTH-1145: Issuer On-Behalf Services (OBS) 52 check for CVV validation
This enhancement improves transaction efficiency by reducing unnecessary CVV checks when Mastercard’s pre-validation service (OBS 52) confirms it’s already valid.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Mastercard | Tokenized cards | Processing: Authorizations |
Enablement
No enablement required.
Technical info
For tokenized transactions, if Banking.Live receives OBS 52 (Mastercard Digital Enablement Service
CVC 3 Pre-Validation) as valid and the PAN auto-entry via a magnetic stripe or contactless magnetic
stripe, CVV validation will be skipped based on the OBS result.
AUTH-1170: Logic update: reset update offline PIN counter
We have updated the logic of the offline PIN and unblock script to align with the same behaviour of
online PIN counter resets.
Prior to this release:
- offline PIN block issuer script is only transmitted to the chip when the offline PIN counter is less than 1, e.g. 0.
- for online PIN transactions, the PIN counter is consistently reset each time a PIN is validated.
After this release:
- offline PIN block issuer script is transmitted to the chip and the PIN counter is reset in every EMV contact transaction with a valid online PIN.
- no change to online PIN counter and reset.
To make this change easier for clients, we have introduced this under a new product flag “max_pin_counter”. The default value of this product flag has a max offline PIN counter of 3.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | All | NA | Processing: Authorizations |
Enablement
If you wish to have this product flag enabled, please contact your Client Executive or raise a ticket via our Customer Support Platform.
Technical info
NA.
DEFECT-3000: Addition of product flag: SCA exemption
We’ve introduced a new product flag relating to SCA transactions.
This product flag has been created to solve for SCA exemption transaction scenarios where the recurring indicator field is not present in DE48 SE 22 SF1.
Note: this product flag is disabled as default.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| EEA | Mastercard | NA | Processing: Authorizations |
Enablement
If you wish to have this product flag enabled, please contact your Client Executive or raise a ticket via our Customer Support Platform.
Technical info
Behaviour when“allow_trace_link_for_recurring” product flag is disabled:
- when the recurring indicator field
DE48 SE 22 SF 1, which should contain the value03, was missing from the transaction – thetrace IDlookup was not being triggered – resulting in an SCA decline. However, the recurring indicator inDE61 SE 4was still present.
Behaviour when“allow_trace_link_for_recurring” product flag enabled:
trace IDlookup will be executed based on the presence of recurring indicator fieldDE48 SE 22 SF 1and/or presence of recurring indicator inDE61 SE 4.