Compare the same job
A representment service, an alert network, and a fraud platform are not interchangeable even when each reduces chargeback loss.
Chargeback provider comparison
Compare providers by how the work actually gets done.
Put chargeback management and prevention services side by side across access, onboarding, pricing visibility, capabilities, action execution, coverage, and documented limitations.
The matrix is factual, not a ranking. Different provider types solve different parts of the chargeback lifecycle, and eligibility, contracts, and fees remain provider-controlled.
- Providers compared
- 15 Management and prevention profiles
- Capability criteria
- 19 Using the canonical catalog
- Side by side
- 2–4 Bookmarkable selections
- Dated pricing sources
- 7 Official pages, never estimates
Three rules make the matrix useful
Separate product from access
A provider can document an API or capability without that operation being active in the current Lower Chargeback adapter.
Verify commercial terms
Public prices are dated and linked. Contract pricing, eligibility, sponsor requirements, and external fees must be confirmed with the provider.
Choose by need
Start with the workflow your team needs.
Provider profiles frequently overlap. These counts show how many management and prevention profiles document each workflow; they do not measure quality or active merchant eligibility.
Managed representment
Provider-managed recovery workflows where submission and service terms follow the provider relationship.
Pre-dispute alerts
Alert and deflection services designed to surface eligible cases before a standard chargeback workflow.
Dispute monitoring
Case visibility, evidence review, deadlines, and outcome tracking across connected payment sources.
Fraud prevention
Pre-transaction or order-risk services that reduce fraud exposure rather than representing every dispute.
Interactive comparison
Choose two to four providers.
Start with comparable services, then inspect access, capabilities, action handling, pricing sources, and provider-specific boundaries side by side.
Useful starting sets
Side-by-side matrix
Compare the operating model, not just the feature count.
“Documented” means the capability appears in the canonical provider profile. Only cells explicitly marked as implemented describe current Lower Chargeback adapter coverage.
Service profile
Start with the provider’s role and Lower Chargeback access path before comparing individual features.
| Comparison point |  Chargebacks911 |  Chargeblast |  Chargeflow |  Dispute.com |  Disputifier |  Forter |  Fraud Deflect |  Justt |  Kount Chargeback Management |  Merchanto |  NoFraud |  Ravelin |  Riskified |  Sift |  Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Category | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. | Management and prevention Chargeback management, representment, prevention, and fraud intelligence services. |
| Lower Chargeback access A direct connector is implemented in Lower Chargeback. Other statuses describe the onboarding or external dependency. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider onboarding Catalog profile only until the displayed onboarding path is completed and live access is verified. | Provider agreement required Catalog profile only until the displayed onboarding path is completed and live access is verified. |
| Implemented adapter coverage | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. | No verified adapter The page still compares the provider’s cataloged products and documented access path. |
| Catalog integration | Contract-defined Provider agreement required | API workflow Available to configure | Managed service Available to configure | Managed service Available to configure | Contract-defined Provider agreement required | Contract-defined Provider agreement required | Contract-defined Provider agreement required | Managed service Available to configure | Managed service Available to configure | Contract-defined Provider agreement required | Contract-defined Provider agreement required | Monitoring Available to configure | Contract-defined Provider agreement required | Monitoring Available to configure | Contract-defined Provider agreement required |
| Products | 1 product
| 1 product
| 1 product
| 1 product
| 1 product
| 1 product
| 3 products
| 1 product
| 2 products
| 1 product
| 1 product
| 1 product
| 1 product
| 1 product
| 1 product
|
| Documented capabilities | 7 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 5 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 7 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 7 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 6 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 8 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 12 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 7 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 6 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 5 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 6 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 3 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 7 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 2 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. | 7 cataloged These describe the provider profile and may be broader than the active Lower Chargeback adapter. |
| Public pricing snapshot Only dated official pricing sources are shown. Unlisted pricing is not estimated. | Custom performance-based pricing Chargebacks911 describes performance-based pricing that scales to the merchant. An exact fee schedule is not published. Verified August 7, 2026. | Public per-event and success pricing Ethoca alerts: $29. Visa RDR/CDRN alerts: $19. Recovery: 15% of recovered amounts. Deflection: $14. No setup fee or monthly retainer is listed. Verified August 7, 2026. | Public usage and success pricing Insights: $0. Prevention: $0.20 per scanned transaction with the first 1,000 free. Recovery: 25% of recovered chargebacks. Alerts: $29 per deflected chargeback. Verified August 7, 2026. | Contact provider Dispute.com does not publish a fee schedule. Its API documentation describes plan-dependent usage limits and directs prospective users to sales. Verified August 7, 2026. | Public usage and success pricing Recovery: 20% of recovered revenue, capped at $250 per win. Fraud prevention and order-not-received prevention: $0.05 per order. Alert pricing requires a volume quote. Verified August 7, 2026. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Custom provider pricing Fraud Deflect presents Deflect, Intercept, and Represent through managed onboarding, but does not publish an exact merchant fee schedule on the reviewed official pages. Verified August 7, 2026. | Custom success-based pricing Justt states that merchants pay when a chargeback is won. The success fee and alert pricing are not published. Verified August 7, 2026. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. | Confirm with provider No dated public pricing snapshot is included for this provider. Provider fees remain separate from Lower Chargeback. |
| Lower Chargeback plan | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. | Included on Shopify App Free Provider contracts, external fees, and eligibility remain separate. Direct non-Shopify accounts do not include Provider Hub workflows. |
Connection and coverage
Compare how access is obtained, what the merchant needs, and where the provider profile applies.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Access methods | 3 paths
| 1 path
| 2 paths
| 2 paths
| 2 paths
| 3 paths
| 2 paths
| 2 paths
| 2 paths
| 2 paths
| 2 paths
| 1 path
| 2 paths
| 1 path
| 2 paths
|
| Onboarding | Managed provider onboarding | Self-service provider account | Self-service provider account | Self-service provider account | Managed provider onboarding | Managed provider onboarding | Managed provider onboarding | Self-service provider account | Self-service provider account | Managed provider onboarding | Managed provider onboarding | Self-service provider account | Managed provider onboarding | Self-service provider account | Managed provider onboarding |
| Activation verification | Provider approval | Credential verification | Credential verification | Credential verification | Provider approval | Provider approval | Provider approval | Credential verification | Credential verification | Provider approval | Provider approval | Credential verification | Provider approval | Credential verification | Provider approval |
| Eligibility | Chargebacks911 must approve the merchant, payment sources and delivery method. | The merchant must have an active Chargeblast alert account and API access. | The merchant must authorize its Chargeflow organization and the connected payment accounts. | The merchant must authorize its Dispute.com account and connected payment sources. | Disputifier must approve the merchant organization and connected processors. | Forter must approve the merchant, data exchange and dispute workflow. | Fraud Deflect must approve the merchant, covered payment sources, and enabled Deflect, Intercept, or Represent services. | The merchant must have an active Justt account and API access. | The merchant must have Kount Chargeback Management or Midigator API access. | Merchanto must approve the merchant and provide its white-label integration contract. | The merchant must have an active NoFraud protected-claims agreement and approved API access. | The merchant must have Ravelin API access for its account. | Riskified must approve Dispute Resolve and the merchant's payment-source mapping. | The merchant must have a Sift account and server-side Events API access. | The merchant must have a Signifyd Chargeback Recovery agreement and approved payment-source mapping. |
| Required identifiers | 3 required
| 1 required
| 1 required
| 1 required
| 2 required
| 3 required
| 2 required
| 1 required
| 1 required
| 3 required
| 2 required
| 1 required
| 2 required
| 1 required
| 2 required
|
| Connection settings | No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | 2 fields Only public-safe field labels are shown. Credential values never appear on this page.
| 2 fields Only public-safe field labels are shown. Credential values never appear on this page.
| 2 fields Only public-safe field labels are shown. Credential values never appear on this page.
| No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | 2 fields Only public-safe field labels are shown. Credential values never appear on this page.
| 2 fields Only public-safe field labels are shown. Credential values never appear on this page.
| No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | 1 field Only public-safe field labels are shown. Credential values never appear on this page.
| No public credential form Activation follows the provider, sponsor, managed, or portal path described above. | 2 fields Only public-safe field labels are shown. Credential values never appear on this page.
| No public credential form Activation follows the provider, sponsor, managed, or portal path described above. |
| Geographic coverage | Global | Global | Global | Global | Global | Global | Defined by provider contract | Global | Global | Global | Global | Global | Global | Global | Global |
| Card-network coverage | Defined by provider contract | Depends on the processor of the original transaction | Depends on the processor of the original transaction | Depends on the processor of the original transaction | Defined by provider contract | Defined by provider contract | Visa and Mastercard | Depends on the processor of the original transaction | Depends on the processor of the original transaction | Defined by provider contract | Defined by provider contract | Not card-network specific | Defined by provider contract | Not card-network specific | Defined by provider contract |
Intake and monitoring
How the provider profile describes case intake, event delivery, dispute visibility, and outcome updates.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Case synchronization | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. |
| Webhook ingestion | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Dispute monitoring | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. |
| Outcome synchronization | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. |
Pre-dispute and enrichment
Alert programs and transaction context that can help resolve or clarify a case before representment.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Pre-dispute alerts | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed |
| Alert response | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Transaction enrichment | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Order Insight | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Consumer Clarity | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
Evidence and dispute handling
Cataloged evidence, acceptance, contest, and refund capabilities. A documented capability is not automatically an active Lower Chargeback adapter operation.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Evidence review | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. |
| Evidence submission | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. |
| Accept dispute | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Contest dispute | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Transaction refund | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
Service and prevention
Managed representment, fraud workflows, file delivery, and portal access described by the provider profile.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Managed representment | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. |
| Fraud feedback | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed |
| Fraud prevention | Not listed | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. | Documented Listed in the provider profile; active access depends on the connection path. |
| File exchange | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Documented Listed in the provider profile; active access depends on the connection path. | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
| Portal access | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed | Not listed |
Action execution
The execution path matters as much as the feature name. Every active financial or procedural action remains merchant-confirmed.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Refund | Defined by provider contract Merchant confirmation required. | Not available | Not available | Not available | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Not available | Not available | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. |
| Accept loss | Defined by provider contract Merchant confirmation required. | Not available | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. |
| Contest | Defined by provider contract Merchant confirmation required. | Not available | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. |
| Submit evidence | Defined by provider contract Merchant confirmation required. | Not available | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. |
| Respond to alert | Defined by provider contract Merchant confirmation required. | Not active in Lower Chargeback | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Provider-managed Merchant confirmation required. | Provider-managed Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. | Not available | Defined by provider contract Merchant confirmation required. |
Boundaries and sources
Review the limitations and official source material before selecting or activating a provider.
| Comparison point | Chargebacks911 | Chargeblast | Chargeflow | Dispute.com | Disputifier | Forter | Fraud Deflect | Justt | Kount Chargeback Management | Merchanto | NoFraud | Ravelin | Riskified | Sift | Signifyd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Important limitations | 1 boundary
| 1 boundary
| 1 boundary
| 1 boundary
| 1 boundary
| 1 boundary
| 3 boundaries
| 1 boundary
| 1 boundary
| 1 boundary
| 2 boundaries
| 1 boundary
| 1 boundary
| 1 boundary
| 1 boundary
|
| Official documentation | 1 official source | 1 official source | 1 official source | 1 official source | 1 official source | 1 official source | 2 official sources | 1 official source | 1 official source | 1 official source | 1 official source | 1 official source | 1 official source | 1 official source | 1 official source |
| Full Lower Chargeback profile | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations | Products, settings, actions, and limitations |
Methodology
What each comparison label means.
Provider identity, products, access modes, capabilities, regions, onboarding, settings, action policies, limitations, and documentation come from the same registry used by Provider Hub. Dated pricing snapshots come only from the linked official provider pages.
- Documented
- The capability is present in the provider’s canonical catalog profile. It does not by itself prove active Lower Chargeback execution.
- Implemented
- The capability is declared by a verified adapter currently registered in Lower Chargeback.
- Provider-managed or contract-defined
- The service or action follows the provider relationship rather than a public Lower Chargeback API operation.
- Not listed
- The capability is absent from the current catalog profile. It is not a claim that the provider can never offer it.
Complete provider profiles
Inspect every management and prevention service.
Open a profile for products, settings, onboarding, action handling, limitations, and official documentation. The full Provider Hub contains all 44 catalog entries.
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 Fraud Deflect
Provider agreement required FD.ID Deflect, Intercept, and Represent
- Access
- Provider portal and Managed service
- Coverage
- Defined by provider contract
Case synchronizationPre-dispute alertsDispute monitoring +9 View connector details Close connector details
Management
Fraud Deflect
Connector overview
What Fraud Deflect adds to the hub
This connector profile documents the access and onboarding path for FD.ID Deflect, Intercept, and Represent, including Case synchronization, Pre-dispute alerts, and Dispute monitoring.
Also known as FraudDeflect and FD.ID.
Products and capabilities
Supported provider products
Transaction enrichment, Order Insight, and Consumer Clarity
Case synchronization, Pre-dispute alerts, Alert response, Transaction refund, and Outcome synchronization
Case synchronization, Dispute monitoring, Evidence review, Evidence submission, Managed representment, and Outcome synchronization
Connection profile
Access and coverage
- Access
- Provider portal and Managed service
- Integration
- Contract-defined
- Regions
- North America, Latin America, and Europe
- Card networks
- Visa and Mastercard
- Catalog status
- Provider agreement required
Activation
What the merchant needs
Fraud Deflect must approve the merchant, covered payment sources, and enabled Deflect, Intercept, or Represent services.
- Verification
- Provider approval
- Required identifiers
- Merchant business and Monthly chargeback volume
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 direct Lower Chargeback adapter, public API specification, or public credential contract is documented for this profile.
- Pricing, geographic eligibility, issuer coverage, and payment-source support must be confirmed with Fraud Deflect during managed onboarding.
- Provider-reported performance figures are not guarantees from Lower Chargeback.
Source material
Official documentation
- Fraud Deflect solutions Product overview
- Fraud Deflect managed onboarding Program requirements
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 visual identifiers identify the referenced services and do not imply endorsement, partnership, or a recommendation. This page provides catalog information, not individualized legal, financial, or payment advice.
Monthly service cost calculator
Model provider fees against your sales.
Enter a monthly sales scenario, choose a service with public numeric pricing, and see how order volume, chargeback exposure, and billable outcomes affect the estimated provider fee.
Scenario estimate only, not a quote or invoice. Average sale is used as a proxy for average disputed value, while billable alert and deflection counts are entered separately because chargeback ratio does not determine network eligibility or coverage. Fractional counts are statistical estimates. Each service is modeled independently; do not add estimates together because prevention, alerts, deflection, and recovery can overlap. Results exclude refunds, processor dispute fees, taxes, contractual minimums, enterprise discounts, eligibility, network coverage, integration fees, and Lower Chargeback charges. Disputifier Alerts, Chargebacks911, Justt, Dispute.com, and other services with unpublished or custom pricing remain quote-required and are not estimated.
Comparison questions
Read this before choosing a provider.
Does the provider with the most capabilities automatically win?
No. Capability count does not measure fit, recovery quality, cost, merchant eligibility, service level, or the payment sources your store uses. Start with the workflow and access path your team actually needs.
How do deflection, alert interception, and representment differ?
Deflection uses transaction or order context to try to resolve a dispute before it becomes an alert or chargeback. Alert interception acts after an eligible network alert and may resolve the case through a refund. Representment begins after a formal chargeback and uses evidence to seek recovery. Fraud Deflect’s public solutions overview is one example of this three-stage model; provider coverage, outcomes, and commercial terms still vary.
Does a public API mean the provider is directly connected?
No. “Direct connector” is reserved for an adapter implemented and registered in Lower Chargeback. Public documentation can still require an approved account, contract, credentials, and end-to-end verification.
Why are exact prices shown for only some providers?
Exact prices appear only when an official public source was reviewed and dated. Lower Chargeback does not estimate contract pricing or copy unverified third-party figures.
Is the calculator result a provider quote?
No. It is a sales-volume scenario using dated public rates and the assumptions you enter. It excludes provider eligibility, network coverage, refunds, processor fees, taxes, contractual minimums, discounts, and custom commercial terms.
Are provider fees included in Lower Chargeback?
No. Provider Hub connections are included in the Shopify App Free plan, but provider contracts, external fees, eligibility, sponsors, and commercial terms remain separate.
Does this comparison apply to direct non-Shopify accounts?
The provider-access statuses describe the Shopify Provider Hub catalog. Direct non-Shopify accounts currently provide registration, invoices, business settings, and website liveness tests; they do not automatically include these Provider Hub workflows.
Can I compare payment processors and card-network alert programs too?
Yes. The full Provider Hub covers Shopify Payments, networks, PSPs, acquirers, BNPL services, and management platforms. This page keeps the interactive matrix focused on the management and prevention services that merchants most often evaluate side by side.
Continue with the right access path
Review every connector, or create a direct merchant account.
Shopify merchants can review Provider Hub activation paths. Other e-commerce stores can register for invoices, storefront tests, and business settings.