Release notes: Banking.Live 2.11
DEC-148: Introduction of Parent Accounts
The new Parent Account scope will allow the cascading of rules to the Main children accounts. Essentially - a rule will be applied to the transaction if the rule's scope is a parent of the main account of the card the transaction belongs to.
Impact on Clients
This feature allows B2B clients more flexibility in rule application.
PECA-282: EMV Chip Profile Enablement for JETCO
This feature introduces a new endpoint, pws_update_emv_script , that allows issuers to enable a new chip profile on physical cards. By POSTing values in the fields account_number, account_type, account_restriction, and account_currency_code, issuers can stage a script to update the physical chip. The chip will be updated upon the cardholder’s successful ATM authorization. Currently, this feature supports Jetco in Hong Kong.
Impact on Clients
- New Endpoint Integration: Clients who wish to utilise this feature will need to integrate into the new endpoint.
- Regional Support: This feature currently supports only Jetco in Hong Kong.
PECP-162: Viewing token group rules from the Rules page
Users can view, add, or edit token group rules from the Rules page. This functionality was previously only available from the Groups page; therefore, it was added to the Rules page to make it more visible for our users. Previously, users could only view, add, or edit Account Groups from the rules page, but to view Token Groups, users had to navigate to a different page entirely.
Impact on Clients
Change to User Interface on Pay Control (Rules Screen)
AUTH-238: Support for Business Rules - E-commerce for MADA Internal Ledger
As part of our rollout of internal ledger availability for the MADA card scheme, we have implemented support for Business Rules of E-commerce transactions.
Impact on Clients
No impact on users, step towards availability of internal ledger to new/existing KSA clients as an option.
| DEFECT-577 | API Endpoint pws_get_card_detail returns an error for some token |
|---|---|
| Defect Condition | Failure to convert property value of del_code field from type "null" to type "int" |
| Defect Fix | Defect resolved by updating the data type of field in card renewal API. Also, a new query was introduced to correct such data with null del_code whenever we have null. |
| PECA-289 | Error on pws_mada_token_inquiry when parsing MADA response |
|---|---|
| Defect Condition | During internal development testing of MADA Token Inquiry endpoint, fixes were made to the error encountered while parsing the response from MADA. |
| Defect Fix | The Code Fix was done for parsing MADA response was corrected. |
| PECA-688 | QMR report by BIN version doesn't exclude VISA products |
|---|---|
| Defect Condition | There was a code bug related to the casting of values. |
| Defect Fix | The Code Fix was done to fix the typecast, VISA product was successfully excluded from the QMR report |
| DEFECT-759 | DE22 not populated for manual adjustment transaction |
|---|---|
| Defect Condition | Rule engine exception for tokens that have historic transactions without DE22 |
| Defect Fix | The authorisation processing function fixed to capture DE22 |