To prepare your Salesforce instance for dispute operations, assign the necessary
permission sets and activate external credentials. To retrieve data from the core banking
system, connect to MuleSoft and create an integration definition. To define the process for your
entire dispute workflow, create and activate the service process definition.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, and Unlimited
Editions
Assign Transaction Dispute Management Permissions to User Assign the relevant permission sets, and configure object and field-level security for the Case object and other dispute-related objects. These settings authorize users to capture dispute details, see merchant alerts, and initiate chargebacks.
Connect to MuleSoft and Enable Integration To get financial transactions from a core banking system in the dispute intake form, connect your Salesforce and MuleSoft instances and enable integration between Salesforce and the core banking system.
Configure Dispute Reason Codes and Reason Subcodes When a service representative captures a transaction dispute request, they select a reason code and a reason subcode that describe the issue in the transaction. To make sure that these codes are available during the dispute intake process, add them as picklist values, and create dispute reason records.
Enable Visa Resolve Online (VROL) Integration Enable the integration of Transaction Dispute Management with Visa to enrich Visa transactions data in the dispute intake form and to process Visa chargebacks.
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.
