Create a Stage Definition for Visa Transaction Disputes
Automate the progression of a disputed Visa transaction through its required lifecycle.
Deploy the standard stage definition template to make sure that every disputed transaction adheres
to the specific state transitions mandated by the payment network.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, and Unlimited
Editions
User Permissions Needed
To create a stage definition for Visa transaction disputes:
Stage Management Design User
AND
Financial Services Cloud Standard OR Financial Services Cloud Extension OR FSC
Service
Selecting the Visa Dispute Fulfillment template auto-populates the stage definition with
pre-configured steps and transitions. The steps automatically point to the correct Omniscripts
and integration definitions required to perform specific dispute lifecycle actions, such as
submitting the initial dispute to Visa Resolve Online (VROL) or processing a pre-arbitration
response.
Note The portions of the Services and features branded as Visa Resolve Online (VROL) are
Non-SFDC Applications and, when enabled, are subject to additional terms and conditions as
further described in the applicable Notices and License Information ("NLI") of the Salesforce Trust and Compliance Documentation.
From Setup, in the Quick Find box, enter Stage Definitions, and then
select Stage Definitions.
Click New.
Select Use a Template, and then click
Next.
For select an object, select Dispute Item.
From the list of templates, select Visa Dispute Fulfillment, and
then click Next.
Enter a name and developer name for the stage definition, and then click
Next.
Activate the stage definition by publishing the definition.
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.