What is White-Label?
White-Label Connect - your product name, UI and pricing, with Chargeflow ingesting, enriching and submitting merchant disputes end to end. Includes a comparison with EaaS.
Beta
White-Label (previously documented as "Chargeflow Embedded", Connect Path B) is currently in beta. Capabilities and APIs may change; talk to your account manager about availability.
White-Label is the Connect delivery model where disputes become your own product line. Instead of building and maintaining dispute tooling, you delegate the process to Chargeflow, which connects directly to your merchants' PSPs and data sources, enriches disputes automatically, builds evidence packages, and submits them on the merchants' behalf.
Everything carries your product name, your UI and your pricing. Merchants get a seamless experience without knowing Chargeflow powers it - and it runs on the same Public API documented across these docs.
What Chargeflow does automatically
Once a merchant's integrations are configured, Chargeflow:
- Fetches dispute data: connects to the merchant's PSP and pulls dispute details as they arrive.
- Enriches with context: augments disputes with transaction data, order information, subscription history, customer communication, and more.
- Analyzes for strategy: determines the optimal evidence approach based on dispute reason, industry, and historical win patterns.
- Builds evidence packages: produces a compelling, data-driven evidence PDF tailored to the specific dispute.
- Submits to the bank: handles submission on behalf of the merchant within the response deadline.
Steps 4 and 5 run on auto-pilot by default. If your merchants need to approve evidence before it reaches the bank, ask your account manager to configure co-pilot mode for that segment - see Choose your level of autonomy.
Security
White-Label requires your merchants to share PSP and data source credentials with Chargeflow. Credentials are encrypted in transit and at rest and covered by role-based access control with audit logging. Certifications, encryption standards, and data-handling policies are documented in Security & compliance.
When to use White-Label vs EaaS
| White-Label | Evidence-as-a-Service | |
|---|---|---|
| Dispute ingestion | Chargeflow pulls from PSP automatically | Platform provides dispute data via API |
| Evidence generation | Fully automatic | Triggered by platform API call |
| Submission | Chargeflow handles submission | Platform downloads PDF and submits |
| Integration effort | Lower ongoing maintenance | More platform control |
| Best for | Full-service offering with minimal engineering overhead | Platforms and ISVs that want control over the submission workflow |
Choose White-Label if you want Chargeflow to handle the entire dispute process end to end, including connecting to merchant PSPs and data sources.
Choose Evidence-as-a-Service if your platform already handles dispute ingestion and submission, and you want to augment just the evidence drafting step with AI. If you want your brand on Chargeflow's own interface instead of building a UI, see Co-Branded.