Release notes: Banking.Live 2.21
AUTH-992: Addition of unique identifier in FAST Active and FAST Passive Header (optional)
FAST requests go through multiple network devices and applications, such as revers proxies and load balancers, the addition of a unique identifier will ease the troubleshooting of a particular FAST request (when/if required).
This unique identifier is an optional product feature.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | All | All | FAST: Active and Passive |
Enablement
If you wish to enable the FAST Header unique identifier, please contact your Client Executive.
This is an optional product feature and is controlled by a product flag.
Note: this product flag is disabled by default.
Technical info
Paymentology alerts clients when FAST messages timeout. In the event the request fails to reach the application, troubleshooting of the transaction is simplified with the use of this unique identifier as it allows clients to track the transaction with ease and efficiency.
Please find a sample of the HTTP request header “X-REQUEST-ID” below:
**X-REQUEST-ID: 3b1d0580-da62-491f-be00-7bb132df886e**
DEFECT-2239 & DEFECT-1948: PaySecure specification reminder
This is a reminder related to PaySecure API, specifically Set PIN, Set PIN V2, Verify PIN and Verify PIN V2.
- the PIN value provided in these two API's must adhere to the format specified in the PaySecure API documentation.
- the expected length is 16 characters, values shorter than this will fail validation.
- expected value should match the format below:
- in case PIN it should be PIN block format.
- 246784FFFFFFFFFF (2 = ISO format, 4 = PIN length, 6784 = Actual PIN, FFFFFFFFFF = Padding)
- PAN format is clear text and AES encrypted.
- masked PAN is not accepted.
- if incorrect value, such as masked PAN is used, we will return error "Failed to verify pin due to an invalid PAN"
You are encouraged to review the PaySecure API documentation and ensure compliance with the defined PIN and PAN structure. Please refer to the specific API links provided above.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | All | All | API: PaySecure API |
PECA-600: New Tokenization Customer Service API for account holder messaging in Apple Wallet
We have introduced support to integrate with the Mastercard CS API - Account Holder Messaging.
Account Holder Messaging enables Issuers to display customized messages per token within ApplePay Wallet.
This enhancement allows you to send tailored communications directly below the digitized card image in the Apple Wallet, improving engagement with your cardholders.
If your enabling your cardholders to use ApplePay Wallets, you can now leverage this functionality to share relevant updates, notifications, or promotional messages directly with them.
Applicability
| Region | Scheme | Card type | Product |
|---|---|---|---|
| All | Mastercard & ApplePay | Tokenized cards using ApplePay through Paymentology provided tokenization services (MeaWalet) | API: Tokenization (ApplePay) |
Enablement
If you wish to use this API, please refer to the API specification available and contact your Client Executive to have it enabled.
Note: this is specific to clients using tokenization services through Paymentology (MeaWallet).
Technical info
Functionality:
- messages are displayed within Apple Wallet.
- messages can be customized for each token to provide timely and relevant cardholder communication.
API specifications for this new API are available on PayControl and on the API Explorer under Account Holder Messaging.