Skip to main content

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

Integration classes, data classes, and work properties

Updated on February 9, 2022

Pega Smart Dispute for Issuers can integrate with the Ethoca Eliminator and Case Outcome services by using specialized request integration classes, response data classes, and service work layer page properties.

Request integration classes

The Int-Ethoca integration class stores all the artifacts that are required to establish a connection with Ethoca Eliminator. The following table lists the names of the integration classes that are created for each supported operation:

Operation IDIntegration class
Case OutcomeInt-Ethoca-CaseOutcomeAPI

Response data classes

The Data-Ethoca data layer stores the Ethoca Eliminator response data. The following table lists the names of the data classes that are created for each supported operation:

Operation IDData class
Case OutcomeDate-Ethoca-OutcomeParameters

The Eliminator response objects are created as subclasses under the Data-Ethoca data class.

Service work layer page properties

For output from the Eliminator service, the Pega Smart Dispute for Issuers work layer contains the MerchantInfoFromEthoca page property that is of class Data-Ethoca.

Note: The Case Outcome services uses the PUT HTTP method and does not return any output other than a status code. As a result, no work layer page property exists for this service.


Smart Dispute for Issuers 7.41 - 7.48 Smart Dispute for Issuers Low-Code App Development Financial Services

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