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.

Pega Collections ProcessWSRequest SOAP service

Updated on September 10, 2021

In Pega Customer Service™ for Financial Services, the ProcessWSRequest SOAP Service is used to trigger the strategy through the interaction; to determine the offer that needs to be sent to the customer. 

In Pega Collections, the ProcessWSRequest SOAP service rule is designed to start, stop, or continue offer treatments. It is controlled by a service request parameter RequestType in one of the following ways:

  • When the RequestType is set to InitiateOffer, ProcessWSRequest runs the specific offer that the customer in Collections has accepted.
  • When the RequestType is set to StopOfferProcessWSRequest stops providing offer treatments to that customer. This occurs when a customer in Collections has made a Promise to Pay.
  • When the RequestType is set to BrokenPromise, ProcessWSRequest runs the defined BrokenPromise offer flow on the collections contract strategy.  
  • When the RequestType is set to RTC, ProcessWSRequest runs the specific offer that the customer in Collections has agreed to or the RightToCure offer flow defined in the collections contact strategy.

OfferFlowName is only a necessary parameter when invoking the StopOffer request. It helps to identify the offer to stop. For other request parameters, see Collections ProcessNegotiateOfferRequest SOAP service.

The ProcessWSRequest SOAP service uses the service activity ProcessWSRequest. For more information, see Collections ProcessNegotiateOfferRequest SOAP service.

You can reference the sample data flow for GetCollectionOffer and its referenced strategy DetermineContactTreatment provided in the Pega Customer Decision Hub™ for Financial Services sample application for an example of a Collections strategy. For more details see Using Context Dictionary with Pega Collections and Sample Pega Collections rules

Note: Starting in version 8.5, Pega Customer Decision Hub is Pega's main solution for 1:1 customer engagement, combining the features available in previous versions of Pega Marketing and Pega Customer Decision Hub with many new features. Pega Marketing is no longer available as a separate product.
Collections data flow
  • Previous topic Configuring contexts in Pega Collections
  • Next topic Pega Collections ProcessNegotiateOfferRequest SOAP service


Pega Collections 8.3 - 8.4 Pega Marketing for Financial Services 8.3 - 8.4 Pega Customer Service for Financial Services 8.3 - 8.6 Pega Customer Decision Hub for Financial Services 8.5

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