Credentials verified in Lower Chargeback
The activated adapter can verify credentials and expose the supported synchronization or action flow.
Lower Chargeback Provider Hub
One clear directory for every chargeback connection.
Understand what each service can provide, how access works, which settings are required, and what Lower Chargeback can execute before you enable the connection inside Shopify.
Every provider profile and eligible connection is included on Free. Provider contracts, sponsor requirements, regions, and external fees remain separate.
- Total services
- 43 One canonical catalog
- External services
- 42 Plus Shopify Payments
- Direct connectors
- 7 Verified adapter implementations
- Lower Chargeback plan
- Free For every provider connection
Every profile uses one of three honest connection paths
Eligible account activation
The merchant enters the documented provider settings and completes the verification path shown in the profile.
Agreement, sponsor, or portal required
The card explains the real external dependency without presenting provider access as a public self-service API.
Connector directory
Find the exact service your store uses.
Open any service for products, capabilities, regions, settings, actions, limitations, and official documentation.
No matching connector
Try a broader search or reset the filters.
Native
Shopify native
Shopify Payments dispute information available through the store’s authorized Shopify connection. 
Native Shopify Payments
Direct connector Shopify Payments disputes
- Access
- Native Shopify
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +4 View connector details Close connector details
Native
Shopify Payments
Connector overview
What Shopify Payments adds to the hub
This direct connector brings Shopify Payments disputes into Lower Chargeback for Case synchronization, Dispute monitoring, and Evidence review.
Also known as Shopify Payments disputes.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Native Shopify
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The store must use Shopify Payments and grant the dispute evidence scopes required by the enabled features.
- Verification
- Shopify scope verification
- Required identifiers
- Shopify installation
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Accept loss Lower Chargeback API Merchant confirmation required
- Contest Lower Chargeback API Merchant confirmation required
- Submit evidence Lower Chargeback API Merchant confirmation required
Boundaries
Important limitations
- Availability and evidence operations depend on Shopify Payments eligibility and granted Shopify scopes.
- Every dispute action remains merchant-confirmed.
Source material
Official documentation
- Shopify Payments dispute evidence API reference
Networks
Networks and pre-dispute
Network alerts, issuer signals, transaction enrichment, and pre-dispute programs. 
Networks Visa Verifi
Provider portal workflow Rapid Dispute Resolution (RDR), Cardholder Dispute Resolution Network (CDRN), Order Insight / CE3.0, and INFORM
- Access
- Partner API and Provider portal
- Coverage
- Global
Case synchronizationWebhook ingestionPre-dispute alerts +6 View connector details Close connector details
Networks
Visa Verifi
Connector overview
What Visa Verifi adds to the hub
This connector profile documents the access and onboarding path for Rapid Dispute Resolution (RDR), Cardholder Dispute Resolution Network (CDRN), Order Insight / CE3.0, and INFORM, including Case synchronization, Webhook ingestion, and Pre-dispute alerts.
Also known as Verifi, RDR, CDRN, Order Insight, CE3.0, and INFORM.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Pre-dispute alerts, and Outcome synchronization
Case synchronization, Webhook ingestion, Pre-dispute alerts, Alert response, and Outcome synchronization
Transaction enrichment and Order Insight
Case synchronization, Dispute monitoring, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Partner API and Provider portal
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Visa
- Catalog status
- Provider portal workflow
Activation
What the merchant needs
Enrollment and API access require approval from Verifi or an authorized partner.
- Verification
- Provider approval
- Required identifiers
- Merchant account identifier, Acquirer, and Enabled Verifi products
Settings requested inside Shopify
- Verifi portal URL Optional
Optional merchant portal URL used only for a verified portal handoff.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Lower Chargeback does not run the real-time RDR Decision API because decisions require merchant confirmation.
- Hosted RDR rules remain administered in Verifi.
- Order Insight data responses require explicit connection-level consent.
- The current Lower Chargeback connection remains portal-only until API delivery is verified end to end.
Source material
Official documentation
- Verifi dispute solutions Product overview
Networks Mastercard Ethoca
Provider agreement required Ethoca Alerts and Consumer Clarity
- Access
- Partner API, SFTP, and Provider portal
- Coverage
- Global
Case synchronizationWebhook ingestionPre-dispute alerts +6 View connector details Close connector details
Networks
Mastercard Ethoca
Connector overview
What Mastercard Ethoca adds to the hub
This connector profile documents the access and onboarding path for Ethoca Alerts and Consumer Clarity, including Case synchronization, Webhook ingestion, and Pre-dispute alerts.
Also known as Ethoca, Ethoca Alerts, and Consumer Clarity.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Pre-dispute alerts, Alert response, and Outcome synchronization
Transaction enrichment and Consumer Clarity
Connection profile
Access and coverage
- Access
- Partner API, SFTP, and Provider portal
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Mastercard
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Ethoca product enrollment, delivery format and tokenized identifiers must be approved contractually.
- Verification
- Provider approval
- Required identifiers
- Merchant account identifier, Acquirer, and Enabled Ethoca products
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- No Ethoca feed that exposes PAN data is activated without a tokenized delivery variant and the required PCI approval.
- Consumer Clarity data responses require explicit connection-level consent.
- The connection cannot be marked connected before a real provider delivery is verified.
Source material
Official documentation
- Ethoca products Product overview
Networks Discover Fraud Alerts Premium
Provider agreement required Fraud Alerts Premium
- Access
- Partner API
- Coverage
- Global
Case synchronizationPre-dispute alertsAlert response +1 View connector details Close connector details
Networks
Discover Fraud Alerts Premium
Connector overview
What Discover Fraud Alerts Premium adds to the hub
This connector profile documents the access and onboarding path for Fraud Alerts Premium, including Case synchronization, Pre-dispute alerts, and Alert response.
Also known as Discover FAP and Fraud Alerts Premium.
Products and capabilities
Supported provider products
Case synchronization, Pre-dispute alerts, Alert response, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Partner API
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Discover
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Access requires Discover partner enrollment and provider-issued API material.
- Verification
- Provider approval
- Required identifiers
- Discover merchant identifier and Acquirer or processor
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Authentication and feedback configuration are created only from provider-issued production specifications.
Source material
Official documentation
- Discover Fraud Alerts Premium API specifications API reference
Networks American Express Raw Data Disputes
Sponsor or acquirer required Raw Data Disputes
- Access
- Sponsor or acquirer and SFTP
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +3 View connector details Close connector details
Networks
American Express Raw Data Disputes
Connector overview
What American Express Raw Data Disputes adds to the hub
This connector profile documents the access and onboarding path for Raw Data Disputes, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as Amex Raw Data and American Express Raw Data.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Outcome synchronization, and File exchange
Connection profile
Access and coverage
- Access
- Sponsor or acquirer and SFTP
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- American Express
- Catalog status
- Sponsor or acquirer required
Activation
What the merchant needs
The merchant must be eligible for Raw Data and approve Lower Chargeback or its transfer bridge as an authorized delegate.
- Verification
- Sponsor or acquirer approval
- Required identifiers
- American Express merchant number, Approved delegate, and SFTP enrollment
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- File exchange is activated only after American Express enrollment and host-key verification.
Source material
Official documentation
- American Express Raw Data Program requirements
Payments
PSPs, acquirers and BNPL
Dispute workflows from processors, acquirers, gateways, and pay-later providers. 
Payments Stripe
Direct connector Stripe disputes
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +6 View connector details Close connector details
Payments
Stripe
Connector overview
What Stripe adds to the hub
This direct connector brings Stripe disputes into Lower Chargeback for Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Stripe disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, Outcome synchronization, and Transaction refund
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must control the Stripe account and provide credentials with the minimum required permissions.
- Verification
- Credential verification
- Required identifiers
- Stripe account
Settings requested inside Shopify
- Restricted or secret API key Required
Use a key scoped to the connected Stripe account and required dispute operations.
- Webhook signing secret Optional
Required before Stripe webhook ingestion is enabled.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Refund Lower Chargeback API Merchant confirmation required
- Accept loss Lower Chargeback API Merchant confirmation required
- Contest Lower Chargeback API Merchant confirmation required
- Submit evidence Lower Chargeback API Merchant confirmation required
Boundaries
Important limitations
- Stripe is presented only as an external dispute source, never as a Shopify payment alternative.
- Refunds may be sent only through the Stripe account that processed the original transaction.
- Webhook ingestion remains disabled until the signing secret is verified.
External dispute source only. Stripe is not presented as a gateway or an alternative to Shopify Payments. Lower Chargeback does not change checkout or process payments.
Source material
Official documentation
- Stripe Disputes API API reference
Payments PayPal
Direct connector Customer Disputes
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +6 View connector details Close connector details
Payments
PayPal
Connector overview
What PayPal adds to the hub
This direct connector brings Customer Disputes into Lower Chargeback for Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as PayPal Customer Disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, Outcome synchronization, and Transaction refund
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The PayPal application must belong to or be authorized for the merchant account.
- Verification
- Credential verification
- Required identifiers
- PayPal merchant account and PayPal application
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Client ID Required
PayPal application client ID.
- Client secret Required
PayPal application client secret.
- Webhook ID Required
PayPal webhook ID used to verify inbound events.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Refund Lower Chargeback API Merchant confirmation required
- Accept loss Lower Chargeback API Merchant confirmation required
- Contest Lower Chargeback API Merchant confirmation required
- Submit evidence Lower Chargeback API Merchant confirmation required
Boundaries
Important limitations
- Refunds may be sent only through the PayPal account that processed the original transaction.
Source material
Official documentation
- PayPal Customer Disputes API API reference
Payments Braintree
Provider onboarding Braintree disputes
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +6 View connector details Close connector details
Payments
Braintree
Connector overview
What Braintree adds to the hub
This connector profile documents the access and onboarding path for Braintree disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as PayPal Braintree.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, Outcome synchronization, and Transaction refund
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must provide API credentials for its Braintree gateway account.
- Verification
- Credential verification
- Required identifiers
- Braintree merchant ID
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Merchant ID Required
Braintree merchant ID.
- Public key Required
Braintree API public key.
- Private key Required
Braintree API private key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Refund Not active in Lower Chargeback Handled according to the provider workflow
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Capabilities are restricted to those enabled for the connected Braintree merchant account.
Source material
Official documentation
- Braintree dispute management Integration guide
Payments Adyen
Provider onboarding Adyen Disputes API
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Adyen
Connector overview
What Adyen adds to the hub
This connector profile documents the access and onboarding path for Adyen Disputes API, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Adyen Disputes API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The Adyen web service user must have dispute permissions for the selected merchant account.
- Verification
- Credential verification
- Required identifiers
- Adyen merchant account
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Merchant account Required
Adyen merchant account identifier.
- API key Required
API key assigned to the Adyen web service user.
- Webhook HMAC key Required
HMAC key used to authenticate Adyen webhook notifications.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Available dispute actions depend on the dispute stage and Adyen account permissions.
Source material
Official documentation
- Adyen Disputes API reference API reference
Payments Checkout.com
Direct connector Checkout.com disputes
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Checkout.com
Connector overview
What Checkout.com adds to the hub
This direct connector brings Checkout.com disputes into Lower Chargeback for Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Checkout and CKO.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must provide a scoped secret key and the account-specific API hostname prefix.
- Verification
- Credential verification
- Required identifiers
- Checkout.com account
Settings requested inside Shopify
- Secret API key Required
Checkout.com secret key with the required dispute scopes.
- Webhook signature key Required
Signature key used to authenticate Checkout.com webhook events.
- API account prefix Required
Account-specific API hostname prefix issued by Checkout.com.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Lower Chargeback API Merchant confirmation required
- Contest Lower Chargeback API Merchant confirmation required
- Submit evidence Lower Chargeback API Merchant confirmation required
Boundaries
Important limitations
- The API prefix accepts only a single provider-issued hostname label and cannot contain a URL or path.
Source material
Official documentation
- Checkout.com Disputes API API reference
Payments Square
Direct connector Square Disputes API
- Access
- Public API
- Coverage
- North America, Europe, United Kingdom, and Asia Pacific
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Square
Connector overview
What Square adds to the hub
This direct connector brings Square Disputes API into Lower Chargeback for Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Square Disputes API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- North America, Europe, United Kingdom, and Asia Pacific
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The Square application must be authorized for the merchant account and required dispute scopes.
- Verification
- Credential verification
- Required identifiers
- Square merchant account
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Access token Required
Square access token authorized for the required merchant location.
- Webhook signature key Required
Signature key used to authenticate Square webhook events.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Lower Chargeback API Merchant confirmation required
- Contest Lower Chargeback API Merchant confirmation required
- Submit evidence Lower Chargeback API Merchant confirmation required
Boundaries
Important limitations
- Availability follows Square seller-country and account eligibility.
Source material
Official documentation
- Square Disputes API overview API reference
Payments NMI
Direct connector Chargeback Monitoring and Query API Reporting
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +1 View connector details Close connector details
Payments
NMI
Connector overview
What NMI adds to the hub
This direct connector brings Chargeback Monitoring and Query API Reporting into Lower Chargeback for Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as NMI Payment Gateway and Network Merchants.
Products and capabilities
Supported provider products
Webhook ingestion and Dispute monitoring
Case synchronization, Dispute monitoring, and Transaction enrichment
Connection profile
Access and coverage
- Access
- Public API
- Integration
- Monitoring
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must control the NMI gateway account and use a dedicated security key. Chargeback data is available only when the configured processor supports reporting.
- Verification
- Credential verification
- Required identifiers
- NMI gateway account and Chargeback-capable processor
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Settlement currency Required
Three-letter uppercase currency used when a chargeback webhook omits currency.
- API security key Required
Dedicated NMI security key with the minimum Query API permissions.
- Webhook signing key Required
Signing key shown in NMI Merchant Portal for webhook verification.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
This profile does not expose a financial or procedural action.
Boundaries
Important limitations
- Chargeback reporting is available only when the merchant's configured processor supports it.
- NMI documents monitoring and notification, not API evidence submission or chargeback decisions.
Source material
Official documentation
- NMI Chargeback Events API reference
- NMI Query API API reference
- NMI Webhooks Integration guide
Payments Authorize.Net
Direct connector Fraud Management Webhooks and eCheck Returns & Chargebacks
- Access
- Public API and Provider portal
- Coverage
- North America, Europe, United Kingdom, and Asia Pacific
Webhook ingestionFraud preventionPortal access View connector details Close connector details
Payments
Authorize.Net
Connector overview
What Authorize.Net adds to the hub
This direct connector brings Fraud Management Webhooks and eCheck Returns & Chargebacks into Lower Chargeback for Webhook ingestion, Fraud prevention, and Portal access.
Also known as Authorize.net, Auth.Net, and ANet.
Products and capabilities
Supported provider products
Webhook ingestion and Fraud prevention
Portal access
Connection profile
Access and coverage
- Access
- Public API and Provider portal
- Integration
- Monitoring
- Regions
- North America, Europe, United Kingdom, and Asia Pacific
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must control the Authorize.Net account and supply credentials from API Credentials and Keys.
- Verification
- Credential verification
- Required identifiers
- Authorize.Net merchant account and Merchant Service Provider for card disputes
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Merchant currency Required
Three-letter uppercase currency for fraud-monitoring events.
- API Login ID Required
API Login ID generated in the Authorize.Net Merchant Interface.
- Transaction Key Required
Transaction Key generated in the Authorize.Net Merchant Interface.
- Signature Key Required
Hex-encoded Signature Key used to verify X-ANET-Signature webhooks.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
This profile does not expose a financial or procedural action.
Boundaries
Important limitations
- Authorize.Net does not manage credit-card chargebacks; the merchant's MSP or acquirer owns that dispute process.
- The connector provides fraud-filter monitoring. eCheck returns remain available in the Authorize.Net portal.
- No chargeback decision or evidence action is sent through Authorize.Net.
Source material
Official documentation
- Authorize.Net API API reference
- Authorize.Net Webhooks Integration guide
- Authorize.Net chargeback responsibilities Program requirements
Payments Razorpay
Region-limited Razorpay disputes
- Access
- Public API
- Coverage
- India
Case synchronizationWebhook ingestionDispute monitoring +4 View connector details Close connector details
Payments
Razorpay
Connector overview
What Razorpay adds to the hub
This connector profile documents the access and onboarding path for Razorpay disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Razorpay Disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- India
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The merchant must have an eligible Razorpay account with dispute API access.
- Verification
- Credential verification
- Required identifiers
- Razorpay account
Settings requested inside Shopify
- Key ID Required
Razorpay API key ID.
- Key secret Required
Razorpay API key secret.
- Webhook secret Required
Secret configured for Razorpay webhook verification.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- The integration is limited to markets and merchant categories supported by Razorpay.
Source material
Official documentation
- Razorpay Disputes API API reference
Payments Airwallex
Region-limited Airwallex disputes
- Access
- Public API
- Coverage
- North America, Europe, United Kingdom, and Asia Pacific
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Airwallex
Connector overview
What Airwallex adds to the hub
This connector profile documents the access and onboarding path for Airwallex disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Airwallex disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- North America, Europe, United Kingdom, and Asia Pacific
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The merchant account must be enabled for Airwallex Payments and dispute API access.
- Verification
- Credential verification
- Required identifiers
- Airwallex account
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Client ID Required
Airwallex API client ID.
- API key Required
Airwallex API key.
- Webhook secret Required
Secret used to verify Airwallex webhook events.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Availability follows Airwallex entity, region and product eligibility.
Source material
Official documentation
- Airwallex dispute API integration Integration guide
Payments Amazon Pay
Region-limited Amazon Pay disputes
- Access
- Public API
- Coverage
- North America, Europe, United Kingdom, and Asia Pacific
Case synchronizationWebhook ingestionDispute monitoring +6 View connector details Close connector details
Payments
Amazon Pay
Connector overview
What Amazon Pay adds to the hub
This connector profile documents the access and onboarding path for Amazon Pay disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Amazon Pay disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, Outcome synchronization, and Transaction refund
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- North America, Europe, United Kingdom, and Asia Pacific
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The Amazon Pay merchant and signing key must be active in the selected region.
- Verification
- Credential verification
- Required identifiers
- Amazon Pay merchant ID and Registered public key
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Region Required
Amazon Pay region for this merchant account.
- Merchant ID Required
Amazon Pay merchant ID.
- Public key ID Required
Amazon Pay public key ID.
- Private key Required
Private key corresponding to the registered Amazon Pay public key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Refund Not active in Lower Chargeback Handled according to the provider workflow
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Regional endpoints and dispute capabilities follow the Amazon Pay merchant region.
Source material
Official documentation
- Amazon Pay dispute management Integration guide
Payments Worldpay
Provider agreement required Worldpay Chargeback API
- Access
- Partner API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Worldpay
Connector overview
What Worldpay adds to the hub
This connector profile documents the access and onboarding path for Worldpay Chargeback API, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Worldpay Chargeback API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Partner API
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Worldpay must enable the Chargeback API and issue the account-specific credentials.
- Verification
- Provider approval
- Required identifiers
- Worldpay merchant entity and Worldpay account identifier
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Credential fields are added only from the merchant's approved Worldpay specification.
Source material
Official documentation
- Worldpay Chargeback API API reference
Payments Nuvei
Provider onboarding Nuvei Dispute Management
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Nuvei
Connector overview
What Nuvei adds to the hub
This connector profile documents the access and onboarding path for Nuvei Dispute Management, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Nuvei Dispute Management.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
Dispute Management must be enabled for the Nuvei merchant site.
- Verification
- Credential verification
- Required identifiers
- Nuvei merchant ID and Nuvei merchant site ID
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Merchant ID Required
Nuvei merchant ID.
- Merchant site ID Required
Nuvei merchant site ID.
- Secret key Required
Secret key issued for the Nuvei merchant site.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Enabled operations follow the Nuvei merchant site's dispute configuration.
Source material
Official documentation
- Nuvei dispute management Integration guide
Payments dLocal
Region-limited dLocal chargebacks
- Access
- Public API
- Coverage
- Latin America, Africa, Middle East, and Asia Pacific
Case synchronizationWebhook ingestionDispute monitoring +4 View connector details Close connector details
Payments
dLocal
Connector overview
What dLocal adds to the hub
This connector profile documents the access and onboarding path for dLocal chargebacks, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as dLocal chargebacks.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Latin America, Africa, Middle East, and Asia Pacific
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The dLocal merchant account must be enabled in the applicable processing countries.
- Verification
- Credential verification
- Required identifiers
- dLocal merchant account
Settings requested inside Shopify
- X-Login Required
dLocal account login identifier used for API authentication.
- X-Trans-Key Required
dLocal transaction key.
- Secret key Required
dLocal signing secret.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Available countries and chargeback operations depend on the dLocal merchant contract.
Source material
Official documentation
- dLocal chargebacks Integration guide
Payments Klarna
Region-limited Disputes Management V4
- Access
- Public API
- Coverage
- North America, Europe, United Kingdom, and Asia Pacific
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Klarna
Connector overview
What Klarna adds to the hub
This connector profile documents the access and onboarding path for Disputes Management V4, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Klarna Disputes Management V4.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- North America, Europe, United Kingdom, and Asia Pacific
- Card networks
- Not card-network specific
- Catalog status
- Region-limited
Activation
What the merchant needs
Disputes Management V4 must be enabled for the Klarna merchant account.
- Verification
- Credential verification
- Required identifiers
- Klarna merchant ID and Klarna region
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Region Required
Klarna region for these API credentials.
- API username Required
Klarna API username.
- API password Required
Klarna API password.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Availability and dispute workflows vary by Klarna market and product.
Source material
Official documentation
- Klarna Disputes Management V4 Integration guide
Payments Afterpay / Clearpay
Region-limited Afterpay disputes
- Access
- Public API
- Coverage
- North America, Europe, United Kingdom, and Asia Pacific
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Afterpay / Clearpay
Connector overview
What Afterpay / Clearpay adds to the hub
This connector profile documents the access and onboarding path for Afterpay disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Afterpay and Clearpay.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- North America, Europe, United Kingdom, and Asia Pacific
- Card networks
- Not card-network specific
- Catalog status
- Region-limited
Activation
What the merchant needs
The merchant account must be enabled for the Afterpay Disputes API in its region.
- Verification
- Credential verification
- Required identifiers
- Afterpay merchant ID and Merchant region
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Region Required
Afterpay or Clearpay merchant region.
- Merchant ID Required
Afterpay merchant ID.
- Secret key Required
Afterpay merchant secret key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Clearpay is an Afterpay regional alias and is not a separate provider connection.
- Documented dispute API limitations remain applicable per region.
Source material
Official documentation
- Afterpay Disputes API Integration guide
Payments Affirm
Region-limited Disputes API V3
- Access
- Public API
- Coverage
- North America and United Kingdom
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Affirm
Connector overview
What Affirm adds to the hub
This connector profile documents the access and onboarding path for Disputes API V3, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Affirm Disputes API V3.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- North America and United Kingdom
- Card networks
- Not card-network specific
- Catalog status
- Region-limited
Activation
What the merchant needs
Disputes API V3 must be enabled for the Affirm merchant account.
- Verification
- Credential verification
- Required identifiers
- Affirm merchant account and Merchant region
Settings requested inside Shopify
- Environment Required
Select the provider environment represented by these credentials.
- Region Required
Affirm merchant region.
- Public API key Required
Affirm public API key.
- Private API key Required
Affirm private API key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Affirm dispute availability is region and product dependent.
Source material
Official documentation
- Affirm Disputes API V3 API reference
Payments Fiserv
Sponsor or acquirer required Fiserv Disputes
- Access
- Sponsor or acquirer and Partner API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Fiserv
Connector overview
What Fiserv adds to the hub
This connector profile documents the access and onboarding path for Fiserv Disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Fiserv Disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Sponsor or acquirer and Partner API
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Sponsor or acquirer required
Activation
What the merchant needs
The merchant's Fiserv acquiring relationship must sponsor and enable the applicable Disputes product.
- Verification
- Sponsor or acquirer approval
- Required identifiers
- Fiserv merchant identifier, Acquirer relationship, and Enabled Fiserv product
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Credentials and endpoints are modeled only after the sponsoring Fiserv product is identified.
Source material
Official documentation
- Fiserv Disputes API reference
Payments Global Payments
Sponsor or acquirer required Disputes Management
- Access
- Sponsor or acquirer and Partner API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Global Payments
Connector overview
What Global Payments adds to the hub
This connector profile documents the access and onboarding path for Disputes Management, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Global Payments Disputes Management.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Sponsor or acquirer and Partner API
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Sponsor or acquirer required
Activation
What the merchant needs
Global Payments must enable dispute management for the merchant's acquiring account.
- Verification
- Sponsor or acquirer approval
- Required identifiers
- Global Payments merchant identifier and Acquiring entity
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Authentication varies by Global Payments platform and is not inferred before onboarding.
Source material
Official documentation
- Global Payments disputes management Product overview
Payments J.P. Morgan Payments
Provider agreement required Dispute Management
- Access
- Partner API
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
J.P. Morgan Payments
Connector overview
What J.P. Morgan Payments adds to the hub
This connector profile documents the access and onboarding path for Dispute Management, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as JPMorgan Payments and J.P. Morgan Dispute Management.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Partner API
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Provider agreement required
Activation
What the merchant needs
The merchant must be accepted into the applicable J.P. Morgan Payments dispute program.
- Verification
- Provider approval
- Required identifiers
- J.P. Morgan merchant identifier and Acquiring relationship
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Product availability, including beta access, is confirmed by J.P. Morgan before activation.
Source material
Official documentation
- J.P. Morgan Dispute Management Integration guide
Payments Paystack
Region-limited Paystack disputes
- Access
- Public API
- Coverage
- Africa
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Paystack
Connector overview
What Paystack adds to the hub
This connector profile documents the access and onboarding path for Paystack disputes, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Paystack disputes.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Africa
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The merchant must have a Paystack account in a supported country.
- Verification
- Credential verification
- Required identifiers
- Paystack merchant account
Settings requested inside Shopify
- Secret key Required
Paystack secret key used for API access and webhook verification.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Paystack availability follows its supported African markets.
Source material
Official documentation
- Paystack dispute management Integration guide
Payments Flutterwave
Region-limited Flutterwave chargebacks
- Access
- Public API
- Coverage
- Africa
Case synchronizationWebhook ingestionDispute monitoring +5 View connector details Close connector details
Payments
Flutterwave
Connector overview
What Flutterwave adds to the hub
This connector profile documents the access and onboarding path for Flutterwave chargebacks, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Flutterwave chargebacks.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Accept dispute, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Africa
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The merchant must have an eligible Flutterwave account with chargeback access.
- Verification
- Credential verification
- Required identifiers
- Flutterwave merchant account
Settings requested inside Shopify
- Secret key Required
Flutterwave API secret key.
- Webhook secret hash Required
Secret hash configured for Flutterwave webhooks.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Not active in Lower Chargeback Handled according to the provider workflow
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Available actions and markets follow the connected Flutterwave account.
Source material
Official documentation
- Flutterwave chargebacks Integration guide
Payments Solidgate
Region-limited Solidgate chargebacks
- Access
- Public API
- Coverage
- Europe and United Kingdom
Case synchronizationWebhook ingestionDispute monitoring +4 View connector details Close connector details
Payments
Solidgate
Connector overview
What Solidgate adds to the hub
This connector profile documents the access and onboarding path for Solidgate chargebacks, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Solidgate chargebacks.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Contest dispute, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- Evidence workflow
- Regions
- Europe and United Kingdom
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Region-limited
Activation
What the merchant needs
The merchant account must be enabled for Solidgate chargeback notifications and evidence handling.
- Verification
- Credential verification
- Required identifiers
- Solidgate merchant account
Settings requested inside Shopify
- Public key Required
Solidgate merchant public key.
- Secret key Required
Solidgate merchant secret key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Contest Not active in Lower Chargeback Handled according to the provider workflow
- Submit evidence Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Only actions documented for the connected Solidgate account are exposed.
Source material
Official documentation
- Solidgate chargebacks Integration guide
Payments PayU
Provider portal workflow PayU chargeback process
- Access
- Provider portal
- Coverage
- India
Dispute monitoringEvidence reviewEvidence submission +1 View connector details Close connector details
Payments
PayU
Connector overview
What PayU adds to the hub
This connector profile documents the access and onboarding path for PayU chargeback process, including Dispute monitoring, Evidence review, and Evidence submission.
Also known as PayU chargebacks.
Products and capabilities
Supported provider products
Dispute monitoring, Evidence review, Evidence submission, and Portal access
Connection profile
Access and coverage
- Access
- Provider portal
- Integration
- Portal workflow
- Regions
- India
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Provider portal workflow
Activation
What the merchant needs
The merchant must have PayU dashboard access for the applicable Indian merchant account.
- Verification
- Provider portal verification
- Required identifiers
- PayU merchant account
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Provider portal Merchant confirmation required
- Accept loss Provider portal Merchant confirmation required
- Contest Provider portal Merchant confirmation required
- Submit evidence Provider portal Merchant confirmation required
- Respond to alert Provider portal Merchant confirmation required
Boundaries
Important limitations
- The documented connection is portal-only and is never presented as an API integration.
Source material
Official documentation
- PayU chargeback process Integration guide
Management
Management and prevention
Chargeback management, representment, prevention, and fraud intelligence services. 
Management Chargeflow
Provider onboarding Chargeflow platform
- Access
- Public API and Managed service
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +4 View connector details Close connector details
Management
Chargeflow
Connector overview
What Chargeflow adds to the hub
This connector profile documents the access and onboarding path for Chargeflow platform, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Chargeflow API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Managed representment, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API and Managed service
- Integration
- Managed service
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must authorize its Chargeflow organization and the connected payment accounts.
- Verification
- Credential verification
- Required identifiers
- Chargeflow organization
Settings requested inside Shopify
- API key Required
Chargeflow API key issued for the merchant organization.
- Webhook secret Optional
Required before Chargeflow webhook ingestion is enabled.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Provider-managed Merchant confirmation required
- Contest Provider-managed Merchant confirmation required
- Submit evidence Provider-managed Merchant confirmation required
- Respond to alert Provider-managed Merchant confirmation required
Boundaries
Important limitations
- Managed submissions remain subject to merchant confirmation in Lower Chargeback.
Source material
Official documentation
- Chargeflow API overview API reference
Management Justt
Provider onboarding Justt chargeback management
- Access
- Public API and Managed service
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +4 View connector details Close connector details
Management
Justt
Connector overview
What Justt adds to the hub
This connector profile documents the access and onboarding path for Justt chargeback management, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Justt API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Managed representment, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API and Managed service
- Integration
- Managed service
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must have an active Justt account and API access.
- Verification
- Credential verification
- Required identifiers
- Justt merchant organization
Settings requested inside Shopify
- API key Required
Justt API key issued for the merchant account.
- Webhook secret Optional
Required before Justt webhook ingestion is enabled.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Provider-managed Merchant confirmation required
- Contest Provider-managed Merchant confirmation required
- Submit evidence Provider-managed Merchant confirmation required
- Respond to alert Provider-managed Merchant confirmation required
Boundaries
Important limitations
- Managed representation remains merchant-confirmed in Lower Chargeback.
Source material
Official documentation
- Justt API API reference
Management Kount Chargeback Management
Provider onboarding Midigator Events API and Midigator Order Data
- Access
- Public API and Managed service
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +3 View connector details Close connector details
Management
Kount Chargeback Management
Connector overview
What Kount Chargeback Management adds to the hub
This connector profile documents the access and onboarding path for Midigator Events API and Midigator Order Data, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Kount, Midigator, and Kount Midigator.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, and Outcome synchronization
Transaction enrichment and Managed representment
Connection profile
Access and coverage
- Access
- Public API and Managed service
- Integration
- Managed service
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must have Kount Chargeback Management or Midigator API access.
- Verification
- Credential verification
- Required identifiers
- Kount or Midigator merchant ID
Settings requested inside Shopify
- Merchant ID Required
Midigator merchant identifier.
- API key Required
Midigator API key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Provider-managed Merchant confirmation required
- Contest Provider-managed Merchant confirmation required
- Submit evidence Provider-managed Merchant confirmation required
- Respond to alert Provider-managed Merchant confirmation required
Boundaries
Important limitations
- Midigator is a product alias within the Kount card and is not counted as a separate provider.
Source material
Official documentation
- Midigator Events API API reference
Management Forter
Provider agreement required Forter dispute management
- Access
- Private API, Managed service, and SFTP
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +5 View connector details Close connector details
Management
Forter
Connector overview
What Forter adds to the hub
This connector profile documents the access and onboarding path for Forter dispute management, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as Forter Dispute Management.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Managed representment, Fraud prevention, Outcome synchronization, and File exchange
Connection profile
Access and coverage
- Access
- Private API, Managed service, and SFTP
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Forter must approve the merchant, data exchange and dispute workflow.
- Verification
- Provider approval
- Required identifiers
- Forter account identifier, Enabled Forter products, and Approved delivery method
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- No private API or SFTP fields are exposed before Forter provides the approved specification.
Source material
Official documentation
- Forter product overview Product overview
Management NoFraud
Provider agreement required Protected claims
- Access
- Private API and Managed service
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +3 View connector details Close connector details
Management
NoFraud
Connector overview
What NoFraud adds to the hub
This connector profile documents the access and onboarding path for Protected claims, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as NoFraud Portal API.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Managed representment, Fraud prevention, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Private API and Managed service
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
The merchant must have an active NoFraud protected-claims agreement and approved API access.
- Verification
- Provider approval
- Required identifiers
- NoFraud account identifier and Protected payment accounts
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Only claims covered by the merchant's NoFraud agreement are represented.
- Credentials are requested only after NoFraud confirms the approved authentication contract.
Source material
Official documentation
- NoFraud Portal API API reference
Management Chargebacks911
Provider agreement required Chargeback management
- Access
- Private API, Managed service, and SFTP
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +4 View connector details Close connector details
Management
Chargebacks911
Connector overview
What Chargebacks911 adds to the hub
This connector profile documents the access and onboarding path for Chargeback management, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as CB911.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Managed representment, Outcome synchronization, and File exchange
Connection profile
Access and coverage
- Access
- Private API, Managed service, and SFTP
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Chargebacks911 must approve the merchant, payment sources and delivery method.
- Verification
- Provider approval
- Required identifiers
- Chargebacks911 client identifier, Connected processors, and Approved delivery method
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Private API and file-transfer fields are created only from the signed integration specification.
Source material
Official documentation
- Chargebacks911 connectors Product overview
Management Riskified
Provider agreement required Dispute Resolve
- Access
- Private API and Managed service
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +4 View connector details Close connector details
Management
Riskified
Connector overview
What Riskified adds to the hub
This connector profile documents the access and onboarding path for Dispute Resolve, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as Riskified Dispute Resolve.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Managed representment, Fraud prevention, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Private API and Managed service
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Riskified must approve Dispute Resolve and the merchant's payment-source mapping.
- Verification
- Provider approval
- Required identifiers
- Riskified shop identifier and Payment-source mapping
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Connection fields are derived only from the merchant-specific Riskified onboarding package.
Source material
Official documentation
- Riskified Dispute Resolve onboarding Program requirements
Management Signifyd
Provider agreement required Chargeback Recovery
- Access
- Private API and Managed service
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +4 View connector details Close connector details
Management
Signifyd
Connector overview
What Signifyd adds to the hub
This connector profile documents the access and onboarding path for Chargeback Recovery, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as Signifyd Chargeback Recovery.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Managed representment, Fraud prevention, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Private API and Managed service
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
The merchant must have a Signifyd Chargeback Recovery agreement and approved payment-source mapping.
- Verification
- Provider approval
- Required identifiers
- Signifyd account identifier and Protected payment sources
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Only protected orders and contractually enabled recovery workflows are represented.
Source material
Official documentation
- Signifyd Chargeback Recovery Product overview
Management Disputifier
Provider agreement required Chargeback management
- Access
- Private API and Managed service
- Coverage
- Global
Case synchronizationDispute monitoringEvidence review +3 View connector details Close connector details
Management
Disputifier
Connector overview
What Disputifier adds to the hub
This connector profile documents the access and onboarding path for Chargeback management, including Case synchronization, Dispute monitoring, and Evidence review.
Also known as Disputifier chargeback management.
Products and capabilities
Supported provider products
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Managed representment, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Private API and Managed service
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Disputifier must approve the merchant organization and connected processors.
- Verification
- Provider approval
- Required identifiers
- Disputifier organization and Connected processors
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- Private organization API credentials are not modeled before contractual access is granted.
Source material
Official documentation
- Disputifier integrations Product overview
Management Chargeblast
Provider onboarding Chargeblast Alerts
- Access
- Public API
- Coverage
- Global
Case synchronizationWebhook ingestionPre-dispute alerts +2 View connector details Close connector details
Management
Chargeblast
Connector overview
What Chargeblast adds to the hub
This connector profile documents the access and onboarding path for Chargeblast Alerts, including Case synchronization, Webhook ingestion, and Pre-dispute alerts.
Also known as Chargeblast Alerts API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Pre-dispute alerts, Alert response, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API
- Integration
- API workflow
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must have an active Chargeblast alert account and API access.
- Verification
- Credential verification
- Required identifiers
- Chargeblast merchant account
Settings requested inside Shopify
- API key Required
Chargeblast API key.
- Webhook secret Required
Secret used to verify Chargeblast alerts.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Respond to alert Not active in Lower Chargeback Handled according to the provider workflow
Boundaries
Important limitations
- Alert response availability follows the enabled Chargeblast alert products.
Source material
Official documentation
- Chargeblast Alerts implementation Integration guide
Management Merchanto
Provider agreement required Merchanto Horizon
- Access
- Private API and Managed service
- Coverage
- Global
Case synchronizationPre-dispute alertsDispute monitoring +2 View connector details Close connector details
Management
Merchanto
Connector overview
What Merchanto adds to the hub
This connector profile documents the access and onboarding path for Merchanto Horizon, including Case synchronization, Pre-dispute alerts, and Dispute monitoring.
Also known as Merchanto Horizon.
Products and capabilities
Supported provider products
Case synchronization, Pre-dispute alerts, Dispute monitoring, Managed representment, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Private API and Managed service
- Integration
- Contract-defined
- Regions
- Global
- Card networks
- Defined by provider contract
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Merchanto must approve the merchant and provide its white-label integration contract.
- Verification
- Provider approval
- Required identifiers
- Merchanto organization, Connected processors, and Enabled products
No credential form is exposed. Activation follows the provider access path described above.
Action handling
What can happen after synchronization
- Refund Defined by provider contract Merchant confirmation required
- Accept loss Defined by provider contract Merchant confirmation required
- Contest Defined by provider contract Merchant confirmation required
- Submit evidence Defined by provider contract Merchant confirmation required
- Respond to alert Defined by provider contract Merchant confirmation required
Boundaries
Important limitations
- No white-label or private API fields are exposed before provider approval.
Source material
Official documentation
- Merchanto Horizon solutions Product overview
Management Sift
Provider onboarding Dispute feedback
- Access
- Public API
- Coverage
- Global
Fraud feedbackFraud prevention View connector details Close connector details
Management
Sift
Connector overview
What Sift adds to the hub
This connector profile documents the access and onboarding path for Dispute feedback, including Fraud feedback and Fraud prevention.
Also known as Sift dispute feedback.
Products and capabilities
Supported provider products
Fraud feedback and Fraud prevention
Connection profile
Access and coverage
- Access
- Public API
- Integration
- Monitoring
- Regions
- Global
- Card networks
- Not card-network specific
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must have a Sift account and server-side Events API access.
- Verification
- Credential verification
- Required identifiers
- Sift account ID
Settings requested inside Shopify
- Account ID Required
Sift account identifier.
- API key Required
Sift server-side API key.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
This profile does not expose a financial or procedural action.
Boundaries
Important limitations
- Sift is used for dispute feedback and fraud prevention only; it does not submit chargeback actions.
Source material
Official documentation
- Sift Events API API reference
Management Ravelin
Provider onboarding Dispute feedback
- Access
- Public API
- Coverage
- Global
Case synchronizationFraud feedbackFraud prevention View connector details Close connector details
Management
Ravelin
Connector overview
What Ravelin adds to the hub
This connector profile documents the access and onboarding path for Dispute feedback, including Case synchronization, Fraud feedback, and Fraud prevention.
Also known as Ravelin dispute feedback.
Products and capabilities
Supported provider products
Case synchronization, Fraud feedback, and Fraud prevention
Connection profile
Access and coverage
- Access
- Public API
- Integration
- Monitoring
- Regions
- Global
- Card networks
- Not card-network specific
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must have Ravelin API access for its account.
- Verification
- Credential verification
- Required identifiers
- Ravelin merchant account
Settings requested inside Shopify
- API key Required
Ravelin API key for the merchant account.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
This profile does not expose a financial or procedural action.
Boundaries
Important limitations
- Ravelin receives dispute feedback for risk decisions and does not submit dispute actions.
Source material
Official documentation
- Ravelin dispute endpoint API reference
Management Dispute.com
Provider onboarding Dispute.com platform
- Access
- Public API and Managed service
- Coverage
- Global
Case synchronizationWebhook ingestionDispute monitoring +4 View connector details Close connector details
Management
Dispute.com
Connector overview
What Dispute.com adds to the hub
This connector profile documents the access and onboarding path for Dispute.com platform, including Case synchronization, Webhook ingestion, and Dispute monitoring.
Also known as Dispute.com API.
Products and capabilities
Supported provider products
Case synchronization, Webhook ingestion, Dispute monitoring, Evidence review, Evidence submission, Managed representment, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Public API and Managed service
- Integration
- Managed service
- Regions
- Global
- Card networks
- Depends on the processor of the original transaction
- Catalog status
- Available to configure
Activation
What the merchant needs
The merchant must authorize its Dispute.com account and connected payment sources.
- Verification
- Credential verification
- Required identifiers
- Dispute.com account
Settings requested inside Shopify
- API key Required
Dispute.com API key.
- Webhook secret Optional
Required before Dispute.com webhook ingestion is enabled.
Credential values are entered only in the secure connection modal and are never displayed on this public page.
Action handling
What can happen after synchronization
- Accept loss Provider-managed Merchant confirmation required
- Contest Provider-managed Merchant confirmation required
- Submit evidence Provider-managed Merchant confirmation required
- Respond to alert Provider-managed Merchant confirmation required
Boundaries
Important limitations
- Managed submissions remain subject to merchant confirmation in Lower Chargeback.
Source material
Official documentation
- Dispute.com API documentation API reference
Provider names and logos identify the referenced services and do not imply endorsement or partnership. Live access remains subject to the merchant’s own provider account and the requirements shown in each profile.
Provider Hub inside Shopify
Choose a service, enter its settings, and verify the connection.
Connection settings remain in the secure Shopify modal. This public directory never requests or displays credential values.