Chargeflow API

Name: Chargeflow API API
Brand: Chargeflow API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey25 EndpointsREST

For Agents

Pull disputes and alerts, upload evidence and order context, record outcomes, manage webhooks, and process data subject requests on behalf of an e-commerce merchant. Useful for chargeback ops and platform finance agents.

Quickstart

Get started with Chargeflow API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list and respond to chargeback disputes"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Chargeflow API API.

List and inspect chargeback disputes through /public/2025-04-01/disputes and /disputes/{disputeId}, with PATCH to update fields

Attach order, subscription, and free-form evidence to a dispute via the disputes/{disputeId}/evidence, /order, and /subscription sub-endpoints

Pull pre-dispute alerts and post outcomes back through /alerts and /alerts/{alertId}/outcome

Submit captured customer communication to support a representment case using POST /customer-communication

GET STARTED

Start building with Chargeflow API API

Explore with Jentic

View OpenAPI Document

Use for: List all open chargeback disputes for the account, Get the details of a specific dispute by ID, Attach order metadata to a dispute as evidence, Pull all unresolved pre-dispute alerts for review

Not supported: Does not handle payment authorisation, refund issuance through the acquirer, or fraud scoring of new transactions — use for chargeback dispute representment, evidence handling, and alert outcomes only.

Chargeflow is an automated chargeback management platform that fights disputes on behalf of merchants by assembling evidence and submitting representment to issuers. The 2025-04-01 API exposes the full dispute lifecycle: pulling disputes and alerts, attaching evidence and order or subscription context, recording alert outcomes, capturing customer communication, managing webhooks, and handling data subject requests. It is built for e-commerce merchants and platforms that need to outsource chargeback representment without losing visibility into each case.

Use Cases

Patterns agents use Chargeflow API API for, with concrete tasks.

★ Automated Chargeback Representment

Merchants pull each new chargeback via /public/2025-04-01/disputes and attach order details, subscription history, and customer communication so Chargeflow can compile a representment package and submit it to the issuer. Posting evidence through /disputes/{disputeId}/evidence, /order, and /subscription gives Chargeflow the structured signals it needs to build a winning case without merchant staff drafting documents manually.

GET /public/2025-04-01/disputes for new entries, then POST /disputes/{disputeId}/order with the matching order JSON for each

Pre-Dispute Alert Resolution

Some Chargeflow accounts also receive pre-dispute alerts from networks like Verifi and Ethoca. The merchant pulls /alerts and /alerts/{alertId} for context and posts the resolution to /alerts/{alertId}/outcome — for example marking the alert as refunded — so the dispute does not progress to a chargeback.

List /alerts with status=open, fetch details for each, and POST /alerts/{alertId}/outcome with refund decisions where applicable

Real-Time Dispute Webhooks

Risk and finance teams subscribe to dispute events through POST /public/2025-04-01/webhooks so an internal system reacts the moment a chargeback is opened, updated, or resolved. The webhook endpoint can be deleted via DELETE /webhooks/{id} when an integration is decommissioned, keeping the subscription list clean.

POST /public/2025-04-01/webhooks with the merchant's callback URL and the dispute.* event types, then GET /webhooks to verify

Multi-Tenant Platform Operations via Jentic

Platforms that manage Chargeflow on behalf of sub-merchants use POST /accounts to provision tenants and PATCH /accounts/{accountId} to manage settings. An agent operating through Jentic can create new accounts, attach disputes, and pull dispute status across the entire tenant graph from a single intent — without ever holding the parent platform's API key directly.

Search Jentic for 'create chargeflow account', POST /accounts for the new tenant, then GET /disputes scoped to that account

Key Endpoints

25 endpoints — chargeflow is an automated chargeback management platform that fights disputes on behalf of merchants by assembling evidence and submitting representment to issuers.

METHOD

PATH

DESCRIPTION

GET

/public/2025-04-01/disputes

List chargeback disputes

GET

/public/2025-04-01/disputes/{disputeId}

Retrieve a single dispute

POST

/public/2025-04-01/disputes/{disputeId}/evidence

Attach evidence to a dispute

POST

/public/2025-04-01/disputes/{disputeId}/order

Attach order context to a dispute

POST

/public/2025-04-01/alerts/{alertId}/outcome

Record an alert outcome

POST

/public/2025-04-01/webhooks

Subscribe to dispute and alert events

POST

/public/2025-04-01/data-subject/removal

Submit a data subject removal request

GET

/public/2025-04-01/disputes

List chargeback disputes

GET

/public/2025-04-01/disputes/{disputeId}

Retrieve a single dispute

POST

/public/2025-04-01/disputes/{disputeId}/evidence

Attach evidence to a dispute

POST

/public/2025-04-01/disputes/{disputeId}/order

Attach order context to a dispute

POST

/public/2025-04-01/alerts/{alertId}/outcome

Record an alert outcome

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Chargeflow uses an x-api-key header for authentication. Jentic stores the key encrypted in the MAXsystem vault and gives the agent only a scoped execution token, so the merchant's master key never appears in agent prompts or logs.

Intent-based discovery

Agents query Jentic with intents like 'list chargeback disputes' or 'attach order data to a dispute', and Jentic returns the matching Chargeflow operations with the dispute ID and evidence schema resolved.

Time to first call

Direct Chargeflow integration: 3-5 days to handle disputes, evidence uploads, alerts, and webhooks. Through Jentic: under an hour — search, load, execute against the right dispute IDs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Chargeblast API

Chargeblast focuses on pre-dispute alert deflection; Chargeflow specialises in representment of disputes that have already posted.

Choose Chargeblast to prevent disputes from posting; choose Chargeflow to fight chargebacks once they have.

Complementary

Sift API

Sift scores transactions for fraud risk pre-authorisation; Chargeflow handles the post-auth chargeback lifecycle.

Use Sift up-front to reduce fraudulent authorisations and Chargeflow to manage the disputes that still arrive.

Complementary

Stripe API

Stripe is the payment processor whose disputes Chargeflow contests on the merchant's behalf.

Pair Stripe and Chargeflow when the agent needs to pull the original payment intent and stitch its data into a Chargeflow dispute.

FAQs

Specific to using Chargeflow API API through Jentic.

What authentication does the Chargeflow API use?

Chargeflow uses an API key passed in the x-api-key header on every request. You can validate the key against /public/2025-04-01/health-check/access-key. Through Jentic, the key stays encrypted in the MAXsystem vault and is injected only at execution time.

Can I attach order data to a dispute as evidence with the Chargeflow API?

Yes. POST /public/2025-04-01/disputes/{disputeId}/order with the structured order JSON, including line items, ship address, and tracking. The same dispute can also receive subscription context via /subscription and free-form evidence via /evidence.

How do I subscribe to dispute events with the Chargeflow API?

Call POST /public/2025-04-01/webhooks with your callback URL and the event types you care about. List active subscriptions via GET /public/2025-04-01/webhooks and remove them with DELETE /public/2025-04-01/webhooks/{id} when no longer needed.

What are the rate limits for the Chargeflow API?

Chargeflow does not publish a fixed public rate limit. Treat it as a workflow API: pull disputes on a schedule, batch evidence uploads where the API supports it, and back off on HTTP 429 responses.

How do I list new chargeback disputes through Jentic?

Install jentic with pip install jentic, search for 'list chargeback disputes', load the schema for GET /public/2025-04-01/disputes, and execute. Sign up at https://app.jentic.com/sign-up to get an agent API key.

Does the Chargeflow API support multi-tenant platforms?

Yes. Use POST /public/2025-04-01/accounts to provision a sub-merchant account and PATCH /public/2025-04-01/accounts/{accountId} to update its settings. List managed tenants via GET /public/2025-04-01/accounts.