The Pega Smart Dispute for lssuers data model is a set of classes that represents data directly used by the application. The details related to how the data is stored and retrieved from storage is handled by an integration layer that works behind the scenes to manage the data. The intent of this guide is to provide an overview of the major areas described in the data model. Not every class contained in the data model is called out. Emphasis has been placed on the major functional areas and how the classes that represent them are grouped and related. You can browse the full set of classes and properties from Data or Application Explorer.

The following matrix provides the key objects used in Pega Smart Dispute for lssuers. You can use the Data Explorer in the Dev Studio to review all data pages.

Key objects in Pega Smart Dispute for lssuers

Object type	Object class	In use in Pega Smart Dispute for Issuers 8.7	Description
Account	PegaCard-lnterface- Account	Yes	A consumer or business legal entity that has financial obligations with the business. An account generally has one-to-many contacts, each with different authorized roles. This object type requires data from an external system of record.
Admin	PegaCard-lnterface- Admin	Yes	Supports the administrative configurations for VCR, MasterCom, Ethoca, Verifi services and low dollar write-off
Approvals	PegaCard-lnterface- Approve	Yes	Supports the business team for approval configurations for Chargeback, Write-off and other functionalities
MasterCard	PegaCard-lnterface- MC	Yes	Supporting data model for MCOM services and associated functionality including Maestro.
Customer Questionnaire	PegaCard-lnterface- Questionnaire	Yes	Supporting data model for CSR Pending Auth and Manual case
Reject Reason	PegaCard-lnterface- RejectReason	Yes	Supporting data model for VCR services and associated functionality
Third Party	PegaCard-lnterface- ThirdParty	Yes	Supporting data model for third party services - Ethoca and Verifi
Transaction	PegaCard-lnterface- Transaction	Yes	Data model for transaction entity. A set of data that represents movement of funds between the bank and another entity 9often another bank). This object type requires data from an external system of record.
Bank	PegaCard-Party- Bank	Yes	Holds the BlN information
Card Holder	PegaCard-Party	Yes	Supporting data model for cardholder
Merchant	PegaCard-Party- Merchant	Yes	Supporting data model for merchant information