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 integrates with the Verifi Create Insight and Set Insight Outcome services by using specialized request integration classes, response data classes, and service work layer page properties.

Request integration classes

The Int-Verifi integration class stores all of the artifacts that are required to establish a connection with Verifi Order Insight. The integration class that handles the Create Insight service requests is Int-Verifi-CreateInsightAPI.

Note: Because the Set Insight Outcome service requests are sent to Verifi through the VerifiPatchMethod function, no integration class exists for this service.

Response data classes

The Data-Verifi data layer stores the Verifi Order Insight response data. The following table lists the names of the data classes for each supported operation:

Operation IDData class
Create InsightData-Verifi
Set Insight OutcomeData-Verifi-OutcomeParameters

The Order Insight response objects are created as subclasses under the Data-Verifi data class.

Service work layer page properties

For output from the Create Insight service, the Pega Smart Dispute for Issuers work layer contains the MerchantInfoFromVerifi page property of the Data-Verifi class.

Note: The Set Insight Outcome service uses the PATCH HTTP method and returns only a status code as output. 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