Verifi Spoke
Summarize
Summary of Verifi Spoke
Integrate your ServiceNow instance with the Verifi Spoke to enhance the card dispute resolution process through Verifi APIs. This integration promotes early engagement between issuers and merchants in the dispute lifecycle, simplifying pre-dispute resolutions and reducing chargebacks.
Show less
Key Features
- Facilitates dispute management with merchants to prevent escalation, conserving time and resources.
- Enables creation, management, and closure of dispute cases using API actions for improved stakeholder collaboration.
- Allows early dispute resolution with merchant involvement to minimize chargebacks.
- Streamlines processes to lessen the effort needed in managing disputes.
- Enhances communication and cooperation among cardholders, issuers, and merchants.
Spoke Requirements
- Set up a JSON Web Token (JWT) Key with a shared key (HMAC) and connect a JWT provider for signing configuration.
- Ensure installation of dependent plugins:
- ServiceNow Integration Hub Runtime (com.glide.hub.integration.runtime)
- ServiceNow Integration Hub Action Step - REST (com.glide.hub.actionstep.rest)
Spoke Actions
The Verifi Spoke offers actions to efficiently resolve cardholder disputes, including:
- Create Case Request Builder: Securely create and submit dispute cases for merchant communication.
- Look up Case Request Builder: Retrieve case details from the Verifi API.
- Look up Multiple Cases Request Builder: Retrieve multiple case details in one attempt.
- CDRN Eligibility Request Builder: Check merchant eligibility on a case in real-time.
- Update Case Request Builder: Update case statuses to CLOSED or REVOKED for efficient management.
Connection and Credential Alias Requirements
Integration Hub utilizes aliases for managing connection and credential information, simplifying configuration across multiple environments. Changes to connection or credential information do not require updates to individual actions using those connections.
Integrate your ServiceNow instance with the Verifi Spoke to streamline the card dispute resolution process by using the Verifi APIs. This integration facilitates early connections between issuers and merchants in the dispute lifecycle, which simplifies conflict resolutions at the pre-dispute stage and minimizes chargebacks.
Request apps on the Store
Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Subscription information
This spoke requires a subscription. Contact your ServiceNow account manager or sales representative for subscription details. For more information, see Legal schedules - IntegrationHub overview
Spoke version
Verifi Spoke v1.0 is the latest version.
Supported versions
This spoke was built for Verifi API version 4.0 but may be compatible with later versions.
Key features
- Address disputes with merchants to prevent escalation, which saves time and resources for both issuers and cardholders.
- Create, manage, and close dispute cases by using API actions to ensure smoother operations and enhanced collaboration among stakeholders.
- Resolve disputes early with direct merchant involvement to minimize chargebacks.
- Leverage streamlined processes and pre-dispute resolutions to reduce the effort required in managing disputes.
- Improve cooperation and communication between cardholders, issuers, and merchants.
Spoke requirements
Set up the JSON Web Token (JWT) Key with a shared key (HMAC) and connect a JWT provider to the signing configuration by using a JWT key reference.
Spoke dependencies
- ServiceNow Integration Hub Runtime (com.glide.hub.integration.runtime)
- ServiceNow Integration Hub Action Step - REST (com.glide.hub.action_step.rest)
Spoke actions
The Verifi Spoke provides actions to resolve cardholder disputes efficiently.
| Category | Action | Description |
|---|---|---|
| Verifi Case Management | Create Case Request Builder | Use the Request Builder and response parser of the Verifi Create Case API to create a case that represents the cardholder's dispute and submit it for merchant communication. |
| Create Case Response Parser | ||
| Look up Case Request Builder | Use the Request Builder and response parser of the Look up Case API to retrieve the case details from Verifi API. | |
| Look up Case Response Parser | ||
| Look up Multiple Cases Request Builder | Use the Request Builder and response parser of the Look up Multiple Cases API to retrieve multiple case details from the Verifi API. The issuer can identify multiple case IDs in a single retrieve attempt. | |
| Look up Multiple Cases Response Parser | ||
| CDRN Eligibility Request Builder | Submit a real-time check for merchant eligibility on a case using the CDRN case inquiry-only call, which is facilitated by the request builder and response parser of the Verifi eligibility API. | |
| CDRN Eligibility Response Parser | ||
| Update Case Request Builder | Use the request builder and response parser of the Verifi patch API to update the case status to either CLOSED or REVOKED. This functionality enables issuers to efficiently manage case outcomes. | |
| Update Case Response Parser |
Connection and credential alias requirements
Integration Hub uses aliases to manage connection and credential information, and OAuth credentials. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection.
For information about setting up the spoke, see Set up Verifi Spoke