Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Integration classes, data classes, and work properties

Updated on September 13, 2021

Pega Smart Dispute for Issuers integrates with the Verifi Cardholder Dispute Resolution Network (CDRN) services with specialized request integration classes, response data classes, and service work layer page properties.

Request integration classes

The PegaCard-Int-ThirdParty-Verifi- integration class stores all the artifacts required to establish a connection with Verifi CDRN. The following table lists the names of the integration classes created for each supported operation:

Operation IDData class

Response data classes

The PegaCard-Interface-ThirdParty-Verifi- data layer stores the Verifi CDRN response data. The following table lists the names of the data classes created for each supported operation:

Operation IDData class

The Verifi CDRN response objects are created as subclasses under the PegaCard-Interface-ThirdParty-Verifi- class.

Service work layer page properties

The following table lists the names of the work properties created for each supported operation:

Operation IDPage propertyData class
Note: The Inquiry service returns a single value that is evaluated as a parameter, and the Verifi CDRN Update service uses the PATCH HTTP method and does not return any output other than a status code. As a result, no work layer page properties exist for these two services.


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