Implementation - Section 75
-
- Last UpdatedMar 29, 2023
- 3 minute read
A Section 75 configuration panel has been added under Smart Dispute Configurations in the Dev Studio, which can be easily extended in the future. A dynamic system setting to enable Section 75 has been created with a default value of true, which can be updated to “false”, if required by clicking Disable in the configuration panel.
Decision Table
Clicking Section 75 Configurations opens a decision table, which defines the eligibility criteria for Section 75. Any changes to the eligibility criteria can be updated in the decision table listed below.

When rule
A WhenUKSec75Txn When rule is used to check whether the issuer and merchant falls under the UK region. “GB”,” GBR”, ”GI” and “GIB” are listed in the rule by default, which can be extended for other countries if needed, based on regulatory changes.

As Section 75 is applicable only for credit cards, a When rule check for credit card transactions has also been included.

A When rule, Sec75Eligible, checks for the Sec75Eligible property, which is set as a result of the decision table IsSection75Eligible, as explained above.

UI Changes
The following UI changes have been made as part of the qualification process. When the issuer and merchant is in the UK region, and the selected dispute reason is in Section 75 eligible dispute reasons, the Section75Questions section is shown to the user.

The questions shown below are displayed to the user when issuer and merchant belong to the UK region and the selected dispute reason is Section 75 eligible.

- If the user selects Write-off, the amount gets debited from write-off account and credited to the cardholder account.
- If the user selects Cardholder liable, there is no accounting involved since no amount is given to the cardholder.

Flow
If the user resolves the dispute without handling section 75 related amount (Remaining amount eligible for refund), a flow Sec75OutBalFlow is spun off which handles the remaining amount. If the Section 75 is already processed, the flow is skipped. If the Section 75 is not processed, section 75 assignment is shown to the user where the user needs to process the Section 75 amount.
