Release notes: Banking.Live 2.20

PECA-587: pws_linked_acc_card_list documentation

This release aligns the API response documentation with the actual API response for the List Accounts Linked To Card API.

Applicability

Enablement

No enablement required.

Technical info

Now when you call the List Accounts Linked To Card API the response will return the cu_id as per the API documentation.

DEFECT-2022: Addition of product setting flag "Consider ASI eCommerce"

We have introduced the product flag "Consider ASI (Account Status Inquiry) eCommerce".

This flag allows products the ability to differentiate between ASI and eCommerce transactions, allowing ASI transactions to not be declined when the "Decline all eCommerce transactions" product flag is enabled.

Applicability

Enablement

No enablement required.

The "Consider ASI eCommerce" product flag is enabled by default - therefore, products with the "Decline all eCommerce transactions" product flag enabled will see no change to their processing logic.

If you are wanting to disable the "Consider ASI eCommerce" product flag, you can speak with your Client Executive or raise a ticket via our Customer Support Platform.

Technical info

You can now choose to allow eCommerce-initiated ASI transactions to be approved when the product flag "Decline all eCommerce transactions" is enabled.

This is done by disabling the newly introduced "Consider ASI eCommerce" product flag (it is enabled by default).

PECA-606: Inclusion of decrypted values (CardInfoData, TokenData & RiskInformation) in MADA Tokenization Notifications

Applicable only to Mada Tokenization clients.

We have updated the tokenization notifications sent to you to include decrypted CardInfoData, TokenData & RiskInformation from the originally encryptedData field.

This change allows you to process risk and fraud monitoring data, ensuring
compliance with SAMA’s (Saudi Arabian Monetary Authority) requirements for Issuers.

• Decrypted risk scores: you now receive decrypted RiskInformation in notifications, extracted from the encryptedData field.
• Compliance with SAMA requirements: this update ensures adherence to mandatory checks for Issuers as required by SAMA.
• Improved risk monitoring: provides you with actionable insights to strengthen their fraud and risk management efforts.
• RedactedPCI related fields: to ensure you remain within PCI scope - PAN, Security Code (CVV), Expiry Date, Token & Token Expiry is redacted.

Applicability

Enablement

This is a configurable feature, please reach out to your Client Executive to enable/disable this feature.

Technical info

Decrypted encryptedData data is now included in notifications across the following:

• Tokenization eligibility request (TER): CardInfoData
• Tokenization authorization request (TAR): CardInfoData & RiskInformation
• Tokenization activation code request: CardInfoData
• Activation methods request (AMR): CardInfoData & RiskInformation (RiskInformation is for VTS (Visa Token Services) only)
• Tokenization notification request (TNR): CardInfoData, TokenData & RiskInformation

If you require tokenization message samples for this, please reach out to your Client Executive and reference PECA-606.

For more details, please refer to the corresponding sections in the Mada documentation (pages 51, 56, 66, 70, 84, 95, 103, and 109).

AUTH-987: Parsing of DE104 for Visa Direct transactions

This release introduces further parsing to DE104 of Visa Direct transactions in FAST authorization messages.

For Visa - Field 104, usage 2 is a variable length data element based on the ISO composite TLV format. The elements of a TLV-formatted field are defined as follows:

• The length subfield is a one or two-byte binary subfield that contains the number of bytes in the field. This number includes the total length of all dataset IDs and dataset lengths, along with the lengths of
  the TLV elements.

Applicability

Enablement

No enablement required.

Technical info

If you are requiring further information on Field 104 and its sub-fields, please refer to Visa's processing documentation related to Visa Direct Transactions.

DEC-347: Improve pws_list_rules response time

Applicability

Defect condition

The List Rules API response time was taking longer than it should.

Defect fix

This fix optimizes the List Rules API processing and reduces the response timeframe to be within acceptable timeframes i.e. within 1 second.

DEFECT-2107: pws_virtual_to_physical response error on UAT

Applicability

Defect condition

An internal server error was being returned in some cases when calling the Virtual Card To Physical Card Conversion API on UAT.

Defect fix

This fix resolves the specific issue and introduces the new general API error code response of 987 with description “We are temporarily unable to handle this request. Please try again later". If you receive this error response, you should re-attempt the API call.

You can find the full list of API error response codes here.

DEFECT-2162: pws_rules_list fix

Applicability

Defect condition

It was identified thatthe List Rules API was failing in some intances on UAT.

Defect fix

This fix resolves the issue.

CLR-610: Improve performance of ps_get_iso_v3

Applicability

Improvement

This improvement further optimizes the performance of the internal ps_get_iso_v3 function. The function is used as part of processing clearing and settlement messages received and collating the presentments reports.

PECA-615: (UAT) pws_load_balance V2 API fix

Applicability

Defect condition

An issue was identified where Load Balance V2 was not behaving as it should in UAT. The specific issue was that the Load Balance V2 API was allowing funds to be loaded onto cards when
the cards had "Block load" enabled.

Note: this was specific to UAT.

Defect fix

This fix resolves the issue. This means that when Load Balance V2 is used to load a card with "Block load" enabled, the card will decline the specified load amount.