Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Data model

Updated on June 12, 2022

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.

Pega Smart Dispute for Issuers

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 typeObject class In use in Pega Smart Dispute for Issuers 8.7 Description
AccountPegaCard-lnterface- Account YesA 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 YesSupports the administrative configurations for VCR, MasterCom, Ethoca, Verifi services and low dollar write-off
ApprovalsPegaCard-lnterface- Approve YesSupports the business team for approval configurations for Chargeback, Write-off and other functionalities
MasterCardPegaCard-lnterface- MC YesSupporting data model for MCOM services and associated functionality including Maestro.
Customer Questionnaire PegaCard-lnterface- Questionnaire YesSupporting data model for CSR Pending Auth and Manual case
Reject ReasonPegaCard-lnterface- RejectReasonYesSupporting data model for VCR services and associated functionality
Third PartyPegaCard-lnterface- ThirdPartyYesSupporting data model for third party services - Ethoca and Verifi
TransactionPegaCard-lnterface- TransactionYesData 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.
BankPegaCard-Party- BankYesHolds the BlN information
Card HolderPegaCard-PartyYesSupporting data model for cardholder
MerchantPegaCard-Party- Merchant YesSupporting data model for merchant information

Data Model
Example showing the mapping of Sample data to SD Data layer.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us