Ethoca spoke

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
  • Summarize
    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 Ethoca spoke

    The Ethoca spoke enables ServiceNow customers to integrate their ServiceNow instance with their Ethoca account to efficiently manage card dispute resolution and prevent fraud. This integration facilitates access to detailed merchant information, subscription control, digital receipts, and dispute management within the platform.

    Show full answer Show less

    Key Features

    • Streamlines dispute resolution by enhancing collaboration between issuers and merchants via Ethoca Alerts throughout the dispute lifecycle.
    • Supports resolution at the pre-dispute stage, benefiting both issuers and cardholders by reducing disputes and chargebacks.
    • Provides enriched merchant and transaction information to improve transparency and handling.

    Spoke Requirements and Dependencies

    • An Integration Hub subscription is required to use this spoke.
    • Ethoca configuration details needed include certificate, key alias, consumer key, and keystore password.
    • Dependent plugins must be installed:
      • ServiceNow Integration Hub Runtime (com.glide.hub.integration.runtime)
      • ServiceNow Integration Hub Action Step - REST (com.glide.hub.actionstep.rest)
    • Note that some plugins are licensable features if used outside this spoke and require appropriate licenses.

    Spoke Actions

    The Ethoca spoke includes several actions categorized under Consumer Clarity and Issuer Alerts Management to support dispute and fraud management workflows:

    • Consumer Clarity: Enables cardholders to view credit card transactions with detailed merchant and transaction information.
    • Issuer Alerts Management:
      • Create Transaction Alert: Submits batches of transactions flagged as fraud or disputes to Ethoca for merchant alerts.
      • Look up Transaction Alert Status by Batch: Retrieves processing status of submitted transactions.
      • Look up Alert Status: Provides current alert status delivered to merchants.
      • Look up Alert Outcome by Batch Stream: Returns paginated alerts and outcomes based on batch ID; requires installation of the IntegrationHub Action Template - Data Stream plugin.

    Connection and Credential Management

    Integration Hub uses aliases to manage connection and credential information, including OAuth credentials. This approach simplifies managing multiple environments by avoiding repeated configuration updates when connection details change, enhancing operational efficiency.

    Additional Information

    • The latest version available is Ethoca spoke v3.0.0.
    • The spoke supports Consumer Clarity and Issuer Alerts Management functionalities.
    • For setup instructions, customers should refer to the Ethoca spoke setup documentation.

    Integrate ServiceNow instance with your Ethoca account to manage card dispute resolution and prevent fraud. By using this spoke, you can access detailed merchant information and subscription control, view digital receipts, and manage their disputes.

    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.

    Integration Hub subscription

    This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.

    Spoke version

    Ethoca spoke v3.0.0 is the latest version.

    Supported versions

    This spoke was built for Consumer Clarity and Issuer Alerts Management .

    Key features

    • Streamlines dispute resolution processes
    • Facilitates collaboration between issuers and participating merchants through Ethoca Alerts during the dispute lifecycle
    • Resolves cases at the pre-dispute stage, benefiting both issuers and cardholders
    • Reduces the occurrence of disputes and chargebacks

    Spoke requirements

    • Integration Hub subscription
    • Ethoca configuration details such as, certificate, key alias, consumer key, and keystore password

    Spoke dependencies

    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)
    Note:
    If used outside the spoke implementation, some of these plugins are licensable features and need appropriate licenses.

    Spoke actions

    The Ethoca spoke provides actions to obtain enriched merchant and transaction information. Available actions include:

    Category Action Description
    Consumer Clarity Look up Consumer Clarity Enables cardholders to view their credit card transactions with clear merchant information and transaction details.

    Issuer Alerts Management

    Create Transaction Alert Submits a batch of transactions (confirmed fraud or customer disputes) to Ethoca. These transactions are processed and delivered to merchants as alerts.
    Look up Transaction Alert Status by Batch Returns the processing status of previously submitted transaction requests.
    Look up Alert Status Provides the status of the alert delivered to the merchant.
    Look up Alert Outcome by Batch Stream Retrieves a list of alerts and their outcomes based on the Batch ID provided by the Submit Batch endpoint or Ethoca Notification Callback. Results are paginated with up to 50 alerts per request and a maximum of 1000 alerts per batch.
    Note:
    To enable the Look up Alert Outcome by Batch Stream action, install the ServiceNow IntegrationHub Action Template - Data Stream (com.glide.hub.action_type.datastream) plugin.

    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 Ethoca spoke