Skip to main content

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

On-Us acquirer case - standalone

Updated on June 10, 2022

The acquirer can create a temporary On-Us dispute case and process On-Us standalone (clients using only Pega Smart Dispute for Acquirer) in the Begin On Us Acquirer Case view.

Pega Foundation for Healthcare

In the Begin On Us Acquirer Case view, the Acquirer submit the following details:

  • Card number
  • Acquirer reference number
  • Dispute amount and Currency
  • Scheme
  • Reason code/Dispute category
  • Condition code/Dispute sub category
  • Attach Document (Maximum allowed 2 MB: TIFF, JPEG, PDF)

On Submit the case routes to the On-Us Acquirer processing view and then routes to the appropriate work queue with proper accounting where the dispute amount is debited from the Acquirer clearing account and credited to the Issuer clearing account.

The following figure shows an example of the Begin On Us Acquirer Case view.

Begin On Us Acquirer Case
The Acquirer can create a temporary case object and enter the required field details on the Begin On Us Acquirer Case screen.

On the On-Us Acquirer processing view, the Acquirer review the dispute amount and have an option to accept or reject the On-Us dispute. In the case of Accept the case is moved to the Process Acquirer liability screen, where the liability amount can be split among Write-off account and merchant account. In the case of Reject, the user need to specify the reason for rejection and enter the details so the case is resolved as Resolved-Rejected.

The following figure shows an example of the On-Us Acquirer processing view.

On-Us Acquirer processing
The Acquirer verifies the dispute amount and accept or reject case for further processing.

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