Integration and data classes
Pega Smart Dispute for Issuers integrates with the Ethoca Alerts services with specialized request integration classes, response data classes, and service work layer page properties.
Request integration classes
The PegaCard-Int-ThirdParty-Ethoca- integration class stores all the artifacts required to establish a connection with Ethoca Alerts. The following table lists the names of the integration classes created for each supported operation:
| Operation ID | Data class |
|---|---|
| Merchant eligibility API | PegaCard-Int-ThirdParty-Ethoca-MerchantAPI-Browse |
| Create | PegaCard-Int-ThirdParty-Ethoca-CC-CreateEthocaCase |
| Get Alert Id | PegaCard-Int-ThirdParty-Ethoca-AID-GetAlertID |
| Merchant outcome | PegaCard-Int-ThirdParty-Ethoca-GMO-GetMerchantOutcome |
Response data classes
The PegaCard-Interface-ThirdParty-Ethoca- data layer stores the Ethoca Alerts response data. The following table lists the names of the data classes created for each supported operation:
| Operation ID | Data class |
|---|---|
| Merchant eligibility API | PegaCard-Interface-ThirdParty-Ethoca-MerchantAPI |
| Create | PegaCard-Interface-ThirdParty-Ethoca-CC |
| Get Alert Id | PegaCard-Interface-ThirdParty-Ethoca-AID |
| Merchant outcome | PegaCard-Interface-ThirdParty-Ethoca-GMO |
The Ethoca Alerts response objects are created as subclasses under the PegaCard-Interface-ThirdParty-Ethoca- class.
Previous topic Ethoca processing merchant outcome dispute processing Next topic Simulation mode