Release notes: Banking.Live 3.6
MHC-717: Aligning weak pin response of M1 with M4
Weak PIN response handling has been aligned across M1 and M4. When a PIN change is rejected due to a weak PIN, a clear and accurate error message is returned to indicate the reason for the rejection.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | NA | NA | Modules – HSM & Crypto |
Enablement
No client action is required. The enhancement is applied automatically.
Technical info
No API changes are included in this update. The change is limited to improved response messaging for weak PIN validation.
AUTH-1719: Change in Response Code for Invalid CVV Declines (Mastercard)
Mastercard transaction declines caused by invalid CVV1, CVV2, or CVV3 will now return a more accurate authorization response code. Previously, these declines were returned with Response Code (RC) 57, which could make it difficult to identify the underlying reason. Going forward, Response Code (RC) 63 will be used to clearly indicate a CVV-related validation failure.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Mastercard | NA | Processing - Authorisations |
Enablement
No action is required from clients. The change is applied automatically.
Technical info
No API or integration changes Clients may choose to update reporting, analytics, or cardholder messaging to reflect the updated response code for CVV-related declines
AUTH-1948: DE48 JSON Support in FAST Active Response
For Mastercard clients, a new feature enables DE48 tag data to be returned in JSON format within the FAST active authorization response. This allows clients to send structured DE48 sub-elements, such as Merchant Advice Codes (MACs), while continuing to support the existing DE48 response for clients who do not require this capability. With this enhancement: DE48 tag data is appended to the authorization response sent to the Mastercard network. DE48 content is included as a JSON object in the response payload. Authorization processing does not validate the DE48 tags or values provided. Important notes: Availability is dependent on the client being enabled on the new authorization engine processing. Legacy authorization processing does not support JSON-formatted DE48 responses. Clients who choose not to adopt this feature can continue using the existing DE48 response with no impact to transaction flows. This enhancement supports sending Merchant Advice Codes (DE48 SE 84) for eligible clients and allows population of other DE48 sub-elements in accordance with Mastercard specifications.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Mastercard | NA | Processing - Authorisations |
Enablement
No action is required for clients who do not wish to use this feature. If you wish to have this feature enabled, please contact your account manager.
Technical info
DE48 tag data is included as a JSON object in the FAST active authorization response and forwarded to the Mastercard network as provided Authorization processing does not validate DE48 tags or values Clients are responsible for ensuring DE48 content complies with Mastercard specifications Supports sending Merchant Advice Codes (DE48 SE 84) for eligible clients, as well as other DE48 sub-elements defined by Mastercard Sample authorization response: {"rid": "2367185", "tid": "2586225970779603250", "mtid": "0110", "de2_tok": "437114100", "de4": "000000000450", "de6": "000000000386", "de7": "0131061637", "de11": "603250", "de39": "00", "de48": { "84": "03", "88": "Y" }}