Release notes: Banking.Live 2.15

CLR-338: Providing 1644 recon messages to our clients through FAST

Provide 1644 reconciliation messages from Mastercard through FAST.

Applicability

Enablement

This new feature is available to clients issuing with Mastercard and using FAST Settlement V3. Enabling these messages is performed through PayControl by Paymentology.

• If you are using FAST Settlement V3 and issuing with Mastercard you can speak with your Client Executive to have this enabled.
• If you are issuing with Mastercard and not using FAST Settlement V3, you can speak with your Client Executive about upgrading to the latest FAST Settlement Version.

Technical info

The specific 1644 message types in-scope are:

• File Currency Summary (680)
• Financial Position Detail (685)
• Settlement Position Detail (688).

FAST sample messages are available under Reconciliation samples - Mastercard.

---

PECA-381: Reorganise swagger API params by required first followed by optional - changes

In line with company strategic goals and feedback received from clients, the reorganization of swagger API parameters aims to improve clarity and usability.

These changes are to the original release item (PECA-287) where some fields were not organised in the mandatory first, optional second order.

Clients will find the API specifications easier to understand, reducing the time needed for integration and assists clients in onboarding to our services as quickly and as smoothly as possible.

NOTE: This does NOT change how our APIs function or are processed.
This update ONLY changes how the fields appear on the API Explorer and PayControl's API specification screen.

Applicability

Enablement

No enablement required.

Changes are purely visual in display on the PayControl API specification screen and the API explorer.

Technical info

PayControl's API specification screen and the the API explorer now reflect this.

PECA-376: PCID outbound API missing API key and basic auth

We have updated the outbound API for PCID to include API key and basic auth support, which were previously missing. This enhancement ensures secure and flexible authentication methods for our clients.

• The outbound API now supports API key and basic auth for secure authentication.
• The API will use the appropriate authentication method based on the provided configuration.
• This ensures seamless and secure integration for clients using the outbound PCID API

Applicability

Enablement

Implementation Manager will help in setup via PayControl.
The implementation will:

• Send the API key in the header if the API key configuration is present.
• Send basic auth credentials in the header if basic auth configuration is present.

If you are using the outbound PCID API, please reach out to your Implementation Manager or Client Executive.

NOTE: This outbound API is optional and specific to client's utilizing Paymentology's tokenization services.

Technical info

You can find further information on this outbound API under Retrieve Product Configuration ID.

AUTH-656: Bypass PIN validation step for tokenized virtual cards

As some merchants in South Africa require a PIN for virtual card transactions, a feature flag has been created to enable this process.

Applicability

Enablement

This is enabled by enabling a feature flag. This is performed by Paymentology internally. All clients have this feature flag disabled by default.

Technical info

NA. All clients are disabled by default.

---

DEFECT-1384: AVS check not including MDES transactions

Applicability

Defect condition

AVS result code in DE48_83 is not including in the response to scheme of MDES transaction with:

• DE48_26 in ('103, '216, '217', '327')
• DE48_82: 52 (AVS requested)
• card token flag allow avs check fail is turned on
• product setting flag of 'allow_avs_fail_as_avs_supported' is set to TRUE

Defect fix

DE48_82 (AVS request indicator) and DE48_83 (AVS response) result is now included in the DE48 output and sent in the reponse to scheme for MDES transactions.

NOTE: This has no impact to FAST messages. In FAST messages we send the iso message received from the scheme (as part of the FAST ISO node), in 0100 messages this won't be present in DE48 from the scheme, we send the AVS check result in the response to the scheme.

DEFECT-1373: PayControl test simulator not sending settlement records

Applicability

Defect condition

Test simulator was not sending settlement records.

Defect fix

Fix released. Test simulator is now sending settlement records.

DEFECT-1368: Missing DE39=NO in filtering condition on PayControl transactions screen

Applicability

Defect condition

On PayControl transactions screen there was no ability to filter for: 'Filter By: Response Code; DE39 = NO'.

Defect fix

Fix deployed allows for filtering of DE39=NO i.e. 'Filter By: Response Code; DE39=NO'.

DEFECT-1336: DE18 Merchant_Category missing from FAST message (MCC 5816)

Applicability

Defect condition

Defect specific to MCC 5816: where Merchant_Category (SUMMARY node) was passing NA when there was a merchant category on the transaction itself and DE18 (ISO_MSG node) is present.

Defect fix

Fix deployed: Merchant_Category (SUMMARY node) will pass 5816 when merchant category on the transaction itself and DE18 (ISO_MSG node) is 5816 and present.

PECA-385: Mada tokenization flow could insert messageReasonCode into 'status' column in p_card_wallet_token_lifecycle

Applicability

Defect condition

An internal method can return messageReasonCode that will be stored in the status column in backend table, when it shouldn't. The staus column should contain the information on the token status that can be used to see the history/lifecycle of the token.

Defect fix

Fix deployed will not insert any record in backend table if there is no information on the token status in the request payload.

DEFECT-1301: Missing DE51 for Jetco certification

Applicability

Defect condition

Jetco balance inquiry transactions were getting declined with DE39 = 78 during handleAuth call as MNQ transactions don't have any DE49 and DE51 fields.

Defect fix

Fix deployed: For Jetco MNQ transactions, currency check is bypassed (DE51).

All other schemes are not affected.

DEFECT-1286: MC completion advice transaction failed due to 0 amount

Applicability

Defect condition

Advice transaction was received with 0 amount in DE4, DE5, DE6 resulting in transaction failure.

Defect fix

Investigation showed DE48 SE63 was invalid for specific transaction advices from acquirer.

We have still put a fix in place to handle invalid DE48 SE63. Now when the same invalid issue occurs with DE48 SE63, transaction advice can still be processed normally.

CLR-413 & AUTH-702: Creating index in backend tables to improve function performance in PayCore DB

Applicability

Defect condition

Issue where authorization transactions were timed out intermittently due to time it took for Rules Engine processing checks.

The specific clients impacted are already aware.

Defect fix

This fix improves the processing performance by adding specific indexes for two functions in PayCore DB in all Banking.Live environments.

The fix resolves the specific cause of the issue.

PECA-371: Bug fix for pws_action_list api endpoint so that it works for requests with type "alert"

Applicability

Defect condition

The List Action API had a bug when it is called with the type “alert”. The API response would return with error id: 989.

NOTE: no clients were using this specific feature.

Defect fix

Fix deployed: when pws_action_list API endpoint is called with type "alert", API response will return as per the documentation specification for pws_action_list.

DEFECT-1154: 3DS ecommerce transaction declined with incorrect code

Applicability

Defect condition

A transaction was received where merchant sent authorization request without 3DS and was declined with reason code 57: Decline - card enrolled to 3DS verification but verification failed.

Since the transaction didn't fail but wasn't tried we need to respond to MC with reason code 65, so the merchant retries with 3DS.

Defect fix

Fix deployed to decline this type of transaction with reason code 65, so the merchant can retry with 3DS.

DEFECT-1143: Internal settlement matching task failed and had to be run manually.

Applicability

Defect condition

Internal settlement matching task failed and was run manually. Investigation carried out revealed underlying cause.

Defect fix

Fix deployed to fix cause of task failure.

❕

NOTE: internal monitoring systems and support team were alerted to task failure and were able to manually run the specific task and file that initially failed. No impact to clients.

DEFECT-1342: MAX PAN updated to lowest PAN value on backend table (HOTFIX already deployed)

Applicability

Defect condition

MAX PAN value for any product should be the lowest possible PAN value plus the number of created cards.

However, the MAX_PAN value of any product is changed to the lowest possible PAN number each time there is any change in product level from PayControl.

Defect fix

HOTFIX already deployed: This fix rectifies the above and means the MAX_PAN value is NOT updated to lowest PAN value during a change in product level from PayControl.

No clients are impacted.

DEFECT-908: Encoding incorrect for merchants with special characters

Applicability

Defect condition

A transaction with merchant name: Krónan ehf. was encoded as: Kr�nan ehf. In the FAST message sent to client it was Kr�nan ehf. when it should have been Krónan ehf.

Defect fix

This fix allows for special characters to be parsed through in the FAST message to clients and displayed correctly in PayControl.

No transactions have been declined or impacted specifically by this defect and the fix means that special characters can now be parsed through to clients as they are initially received by the scheme.

FOR YOUR REFERENCE:

• Mastercard uses ISO 8859-1 single byte encoding (for ASCII), this fix allows all character representations from ISO 8859-1 to be forwarded in the FAST message and displayed correctly in PayControl.
• You can refer to the Mastercard Customer Interface Specification documentation for their full list of supported character sets.

MCCP-139: CloseOperationalDay_s function closes days only within the cycle

Applicability

Defect condition

CloseOperationalDay_s function closes days only within the cycle and does not pick up days from previous cycle.

Defect fix

Fix deployed for CloseOperationalDay_s closes all past days irrespective of cycle.

MCCP-154: Issue in reversal function for the credit function

Applicability

Defect condition

Issue in reversal function logic caused some transactions that were auto-unblocked to not impact the balance on the credit side due to the issue in specified function.

Defect fix

Fix deployed means that a transaction that is auto-unblocked will be in a reversed state, therefore impacting the balance on the credit side.

MCCP-157: Payment Details from credit statement api fetch all cycles payment data

Applicability

Defect condition

With existing logic, we are receiving all the payment from 1st cycle to the current cycle when pws_get_credit_statement API is called. There is no filter of cycle id for the data selection since in this API we will have cycle id as input param we need to filter the data based on the cycle id.

Defect fix

Fix deployed means when pws_get_credit_statement API is called it returns only payments that are done within that cycle.