DocsRequest early access
Product
Refunds in chatVerify the customer, find the payment, resolve it.Disputes & fraud warningsPrevent chargebacks, respond to disputes on time.Refund policy & simulatorClear rules, tested before you publish.Safety & auditWhy the AI can never move money.Payment analyticsApprovals, declines and alerts at a glance.TicketsYour team’s queue after the automation.CasesEvery request with its decision, step by step.
Solutions
Subscription softwareCancellations and forgotten renewals.Online storesDouble charges, deliveries, chargebacks.Digital goods & gamesFraud warnings and refund abuse.Online educationGuarantee refunds, by chat or email.Travel & bookingsLarge amounts, decided by people.Several countriesSeveral accounts, several currencies.Payment providersStripe, PayPal, Paddle, Adyen and more.Your own payment systemOne open contract over REST or MCP.Helpdesk teamsZendesk, webhook intake and email.
Developers
The Chargeless APIWebhooksAPI referenceYour own billing systemEvidence serviceprovidercheck
Resources
How it worksFrom customer request to resolution.IntegrationsProviders, channels and helpdesks.SecurityHow money and data are protected.FAQAnswers to the common questions.
DocsPricing
Request early accessSign in

Developers

Chargeless decides every refund and cancellation with the policy a merchant publishes, and executes it at the payment provider. These guides are for the engineers who connect a merchant's own systems to it. An integration goes one of three ways, and most use the first two.

Call Chargeless from your servers

The Chargeless API lets your backend verify a customer, look up their charges and subscriptions, submit refunds and cancellations that your policy decides, send requests from your own support form, and read the policy, the actions, the cases, refunds, disputes and fraud warnings. It is JSON over HTTPS (the Connect protocol), authenticated with an API key: sr_live_…, or sr_test_… from a test workspace that connects only test-mode payment accounts.

Hear what happened

Webhooks tell your systems when an action executes or fails, a case is handed to your team, a ticket changes or a request is decided: signed HTTPS POSTs with retries.

Let Chargeless call your billing system

When your customers, charges and subscriptions live in your own system, you expose merchant-provider/v1: a small contract Chargeless calls to read facts and to execute the refunds and cancellations its policy approved. It comes in two bindings with the same operations and rules: REST endpoints, or MCP tools over Streamable HTTP. The providercheck conformance kit proves either one against your sandbox before you go live.

Back your disputes with your own records

When a customer disputes a charge, Chargeless answers the bank with the evidence it has. Your evidence service, merchant-evidence/v1, adds what only you know: where the purchase came from, what the customer accepted, used and received. It is one signed HTTPS endpoint that Chargeless asks while it builds a dispute's evidence, whatever your payment provider. Your answer is sent as evidence and never stored.

  • Your evidence service: the request, the answer field by field, what answers which claim, and a complete server in Node.

What there is, and what there is not

  • An API key acts within the policy, the safety limits and the emergency stops. It cannot sign in to the panel, publish the policy, change settings, the team or keys, or read and answer tickets.
  • In the MCP binding, your system is the MCP server and Chargeless is the client. Chargeless does not run an MCP server of its own for AI assistants to connect to, and no language model ever calls your tools: the calls come from Chargeless's own code, after a recorded decision.
  • No client library is published. Generate one from the OpenAPI documents below, or from the protos with Buf (see the API guide).

Downloads

The merchant guide, for the people who run Chargeless day to day, is at /docs.