C86 regulation
Pega Smart Dispute™ Agentic Automation includes eligibility Rules, Service-Level Agreements, and processing Rules for various government consumer regulations. The C86 regulation governs the handling of fraud cases involve credit cards issued by an issuing bank in the Canadian region.
C86 regulation scenarios
Based on the regulatory guidelines, Pega Smart Dispute Agentic Automation addresses the following three key scenarios under the C86 regulation:
- Report of unauthorized use: If the cardholder reported to the issuing bank that their credit card, the account information, or personal authentication details have been lost, stolen, or at risk of unauthorized use, then the cardholder is not liable for any unauthorized transactions after making the report.
- Liability of unauthorized use: The maximum liability of the cardholder for a claim for the unauthorized use of their credit cards is CAD 50 unless the cardholder has demonstrated gross negligence in safeguarding the credit card, the account information, or the personal authentication information; in this scenario, the cardholder might be liable for the entire transaction amount.
- Personal authentication information: If the cardholder has demonstrated gross negligence in safeguarding the credit card information, the account information, or the personal authentication information, the cardholder might be held liable for the entire transaction amount.
C86 regulation implementation
A dispute is eligible for C86 only for Canada issued credit cards on Fraud disputes. The eligibility criteria include the following
- Card type: Credit
- Issuer country code: CA OR CAN or 124
- Exception type: Fraud
When a Initiate Visa Dispute Case fulfils C86 eligibility criteria, the Case displays a new question in the Supplemental information View, which helps clarify whether the cardholder has already reported any suspicious activity on the card from which the transactions are disputed, as shown in the following figure:
Dispute liability processing scenarios under C86 regulation:
During the processing of a dispute Case, if the dispute Case is eligible C86-liabilility, then the Case adheres to one of the following scenarios:
-
If the cardholder reports suspicious activity on the disputed card during the Collect supplemental info Step. The cardholder cannot be held liable for any decline reason or the entire dispute amount.
Consider the following dispute scenario: The cardholder reports suspicious activity on the disputed card. The Issuer holds the cardholder liable for CAD 40 and selects confirmed fraud or gross negligence of the cardholder as the reason for declining the dispute. The Pega Smart Dispute Agentic Automation application supports the C86 regulation by resolving the dispute Case with the As the customer has reported the fraud on the same card before the transaction took place, liability is not permitted message.
- If the overall liability amount is decided against the cardholder, the limit cannot exceed the cap of CAD 50 on the claim.
Consider the following dispute scenario: A customer raises a fraud dispute with the issuing bank. The issuing bank investigates the dispute and confirms that it is a valid fraud dispute and with no gross negligence by the customer. If the issuer holds the card holder liable when resolving the dispute resolution for CAD 100, the Pega Smart Dispute Agentic Automation application supports the C86 regulation by showing the Card holder liability cannot exceed 50 CAD on claim as per C86 rules message.
- If the cardholder is made liable because of gross negligence in safeguarding their card or personal information, then the cardholder can be held liable for the entire dispute amount.
Consider the following dispute scenario: The cardholder is grossly negligent in safeguarding their card and personal information. The Issuer holds the cardholder liable for CAD 100 and selects the decline reason as gross negligence of cardholder. The Pega Smart Dispute Agentic Automation application supports the C86 regulation by resolving the dispute Case as RESOLVED-CUSTOMERLIABLE.
This Topic is available in the following Modules:
Want to help us improve this content?