Skip to main content


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

Technical overview

Updated on June 10, 2022

Review the activity, class, case type, flow, and data transform rule changes related to On Us Acquirer Case – Standalone.

Pega Foundation for Healthcare

PegaCard-Sd-DisputeAcq-OnUs class

The PegaCaes-Sd-DisputeAcq-OnUs class is a Smart Dispute Acquirer On-Us work class.

For example: The following figure shows a sample configuration of the PegaCaes-Sd-DisputeAcq-OnUs class:

DisputeAcq-OnUs class
The General tab of the DisputeAcq-OnUs class displays configuration settings for the class group.

pyDefault case type

The pyDefault case type is a case type rule for On-Us Acquirer case.

For example: The following figure shows a sample configuration of the pyDefault case type:

pyDefault case type
The Processes tab of the pyDefault case type is used to set starting processes and case wise supporting processes.

BeginOnUsAcquirerCase flow

The BeginOnUsAcquirerCase flow describes the following:

  • Flow to Begin Acquirer On-Us case as a temporary work object and persist case after capturing required details on the Begin Acquier On Us view.
  • Call OnUsAcquirerMainFlow sub-flow to process the case further after persisting.
For example: The following diagram shows a sample flow of the BeginOnUsAcquirerCase flow:

BeginOnUsAcquirerCase flow
The Diagram tab of the BeginOnUsAcquirerCase displays the flow to begin on us acquirer case, persist case, and sub flow to process the case.

OnUsAcquirerMainFlow flow

The OnUsAcquirerMinFlow is the main flow to process On Us Acquirer case after persisting the case.

  • Invoking UploadAttachmentToCase Activity to link attachment to the work object.
  • Invoking GetLongDesc Activity to map certain required fields to the pyWorkPage for case processing.
  • Invoking CreatePartiesAndPopulate to create work parties with appropriate data.
  • Invoking FinAdjustmentSTP sub flow by passing DrAcqClearingCrIssuerClearing as a parameter to accounting to credit dispute amount to Issuer by debiting it from Acquirer.
  • Invoking OnUsAcquirerProcess Subflow for further processing of On Us dispute.
  • Checking Acquirer response on the dispute there by setting the resolution status as Resolved-Rejected if the response is reject.
For example: The following diagram shows a sample flow of the OnUsAcquirerMinFlow flow:

OnUsAcquirerMinFlow
The The Diagram tab of the OnUsAcquirerMainFlow displays the main flow to process on us acquirer case.

UploadAttachmentToCase activity

Use the UploadAttachmentToCase activity to upload attachment to a case. Initially, when the case is a temporary object and the attachment is uploaded, it is stored in the .Attachments pagelist. This activity is used to link it to work object after case got persisted.

For example: The following figure shows a sample configuration of the UploadAttachmentToCase activity:

UploadAttachmentToCase activity
The Steps tab of the UploadAttachmentToCase activity is used to set required parameters and properties for new attachment and attach the file to the work object.

CreatePartiesAndPopulate activity

The CreatePartiesAndPopulate activity creates merchant work parties and maps necessary data to the respective work parties.

For example: The following figure shows a sample configuration of the CreatePartiesAndPopulate activity:

CreatePartiesAndPopulate activity
The Steps tab of the CreatePartiesAndPopulate activity is used to set call to create parties and to populate merchant party.

CreateParties activity

The CreateParties activity creates the necessary parties for the merchant object.

For example: The following figure shows a sample configuration of the CreateParties activity:

CreateParties activity
The Steps tab of the CreateParties activity is used to create merchant party page.

MapOnUsUploadedFileinfo data transform

The MapOnUsUploadedFileinfo data transform rule is used to map uploaded file details from pyUploadedfile page to .Attachments.

For example: The following figure shows a sample configuration of the MapOnUsUploadedFileinfo data transform rule:

MapOnUsUploadedFileinfo data transform
The Definition tab of the MapOnUsUploadedFileinfo data transform sets target to map uploaded file details from the pyUploadedfile page.

SetWQForAcqOnUS data transform

The SetWQForAcqOnUs data transform rule is used to set work queue for acquirer on-us processing disputes.

For example: The following figure shows a sample configuration of the SetWQForAcqOnUs data transform rule:

SetWQForAcqOnUS data transform
The Definition tab of the SetWQForAcqOnUS data transform sets work queue for Acquirer on-us processing disputes.

DrAcqClearingCrIssuerClearing financial adjustment

The DrAcqClearingCrIssuerClearing is a financial adjustment rule that is used to perform debit accounting amount from acquirer clearing account and credit to issuer clearing account.

For example: The following figure shows a sample configuration of the DrAcqClearingCrIssuerClearing financial adjustment rule:

DrAcqClearingCrIssuerClearing financial adjustment rule
The Transactions tab of the DrAcqClearingCrIssuerClearing financial adjustment rule is used to set labels for debit acquirer account and credit issuer account.

DrAcqClearingCrIssuerClearing financial adjustment
The Transactions tab of the DrAcqClearingCrIssuerClearing financial adjustment rule is used to set labels for debit acquirer account and credit issuer account.

AcquirerOnUs work parties

The AcquirerOnUs work parties specifies the list of valid parties for acquirer On-Us processing.

For example: The following figure shows a sample configuration of the AcquirerOnUs work parties:

AcquirerOnUs Work Parties
The list of valid parties to process on-us acquirer case is displayed under the Valid Parties tab.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us