--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Verifi Spoke # Verifi Spoke {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Verifi Spoke The Verifi Spoke integrates your ServiceNow instance with Verifi APIs to streamline the card dispute resolution process. This integration enables early communication between issuers and merchants during the dispute lifecycle, helping to simplify conflict resolutions before disputes escalate and reducing chargebacks. It is designed to improve efficiency and collaboration among all parties involved, including cardholders, issuers, and merchants. Show full answer Show less ## Key Features * Build workflows in Flow Designer using actions that invoke Verifi APIs to manage card dispute cases. * Address disputes proactively with merchants to prevent escalation, saving time and resources. * Create, manage, and close dispute cases to ensure smooth operations and enhanced stakeholder collaboration. * Enable early dispute resolution through direct merchant involvement to minimize chargebacks. * Leverage streamlined pre-dispute processes to reduce dispute management effort. * Improve communication and cooperation among cardholders, issuers, and merchants. ## Requirements and Dependencies * An Integration Hub subscription is required to use the Verifi Spoke. * Setup of a JSON Web Token (JWT) Key with a shared HMAC key and connection of a JWT provider for signing configuration is necessary. * Dependent plugins include: * ServiceNow Integration Hub Runtime (com.glide.hub.integration.runtime) * ServiceNow Integration Hub Action Step - REST (com.glide.hub.actionstep.rest) * Some dependent plugins may require additional licensing if used outside the spoke implementation. ## Spoke Actions and Security The Verifi Spoke provides specialized actions to efficiently resolve cardholder disputes, many of which handle sensitive information securely. Actions utilize request builders and response parsers to manage encrypted API communications safely. Key actions include: * Create Case: Build and submit dispute cases for merchant communication. * Look Up Case(s): Retrieve case details, including bulk retrieval of multiple cases. * CDRN Eligibility: Perform real-time checks for merchant eligibility on cases. * Update Case: Change case statuses such as CLOSED or REVOKED to manage case outcomes effectively. ## Connection and Credential Management Integration Hub uses aliases to manage connection and credential information, including OAuth credentials. This approach simplifies configuration across multiple environments by avoiding repetitive updates to connection details when credentials change. ## Additional Information The Verifi Spoke is built for Verifi API version 4.0 and may support later versions. The latest spoke version is v1.0. For setup and detailed configuration guidance, refer to the Verifi Spoke setup documentation. 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 {#verifi-spoke__section_tt2_t1f_qbc} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#verifi-spoke__inline-send-to-store} ## Integration Hub subscription {#verifi-spoke__section_mhk_t1f_qbc} This spoke requires an Integration Hub subscription. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf). ## Spoke version {#verifi-spoke__section_hk1_ytr_zyb} Verifi Spoke v1.0 is the latest version. For version history of the spoke, see [Verifi Spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-verifi-spoke.html). ## Supported versions {#verifi-spoke__section_hrn_t1f_qbc} This spoke was built for Verifi API version 4.0 but may be compatible with later versions. ## Key features {#verifi-spoke__section_irn_t1f_qbc} Verifi Spoke enables a flow designer to build workflows by using actions that invoke Verifi APIs. This integration enables you to do the following tasks: * 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. {#verifi-spoke__ul_rxz_hkc_wyb} ## Spoke requirements {#verifi-spoke__section_lyg_4st_g3b} * Integration Hub subscription * 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. {#verifi-spoke__ul_oxv_ctt_g3b} ## Spoke dependencies {#verifi-spoke__section_asl_nw5_vyb} Ensure that these dependent plugins are installed: * ServiceNow Integration Hub Runtime (com.glide.hub.integration.runtime) * ServiceNow Integration Hub Action Step - REST (com.glide.hub.action_step.rest) {#verifi-spoke__ul_phv_lsk_xyb} Note: Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation. ## Spoke actions {#verifi-spoke__section_srn_t1f_qbc} The Verifi Spoke provides actions to resolve cardholder disputes efficiently. The actions with sensitive information contain sensitive information in the request and response body. One action involves a request builder to securely create requests and a response parser to handle encrypted API responses. The following table lists the actions that have sensitive information.{#verifi-spoke__table_hsl_nw5_vyb__entry__3} | 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. | | Verifi Case Management | Create Case Response Parser | 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. | | Verifi Case Management | 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. | | Verifi Case Management | Look up Case Response Parser | Use the Request Builder and response parser of the Look up Case API to retrieve the case details from Verifi API. | | Verifi Case Management | 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. | | Verifi Case Management | Look up Multiple Cases Response Parser | 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. | | Verifi Case Management | 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. | | Verifi Case Management | CDRN Eligibility Response Parser | 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. | | Verifi Case Management | 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. | | Verifi Case Management | Update Case Response Parser | 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. | [Table 1. Actions with sensitive information] {#verifi-spoke__table_hsl_nw5_vyb} ## Connection and credential alias requirements {#verifi-spoke__section_zrn_t1f_qbc} 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](https://www.servicenow.com/docs/HNTLIIYPkST~VnbxSrdoUg#set-up-verifi-spoke "Integrate the ServiceNow instance and Verifi account by using the JWT authentication to authenticate ServiceNow requests.")