Prebuilt Flows for Initiating Chargeback and Reviewing Second Presentment for Mastercard
Transaction Disputes
To streamline and automate the process of initiating chargebacks and reviewing the second
presentment, use prebuilt record-triggered flows and screen flows.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, and Unlimited
Editions
When a merchant is notified about a disputed transaction through an alert, you can initiate the
chargeback process by cloning and activating the prebuilt record-triggered flows based on the
alert outcome set by the merchant and the time taken by them to respond to the alert.
This table lists the flows provided to initiate the chargeback process and review the second
presentment for disputed transactions.
Flow Label
Description
Default Status
Dispute Management: Initiate Chargeback for Unresolved Merchant Response
When the merchant sets the outcome of an alert that’s raised for a disputed
transaction to Unresolved, this record-triggered flow initiates the chargeback process by
updating the status of the dispute item record to Chargeback Initiated.
Inactive
Dispute Management: Initiate Scheduled Chargeback
When the merchant doesn’t respond to the alert that’s raised for a disputed
transaction within seventy-two hours, this record-triggered flow initiates the chargeback
process by updating the status of the dispute item record to Chargeback Initiated.
Inactive
Dispute Management: Review Disputed Transactions and Create Claim
When the status of a dispute item record is Chargeback Initiated, this screen flow
allows a dispute case owner to review the details of the disputed
transaction, and confirms if the dispute case owner wants to proceed with the claim
creation.
Active
Dispute Management: Review Second Presentment
When the status of the dispute item record is Review Second Presentment, this screen
flow
allows
a dispute case owner to review the chargeback details and claim details associated with the
disputed transaction. The flow then
allows
the case owner to either accept or reject the second presentment.
Active
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.