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
Reference

Glossary

Term Meaning
Workspace One business in Chargeless: its connections, policy, team, tickets and settings.
Policy Your published rules for what the automation may do on its own. Every version is kept.
Decision Chargeless's verdict on a request: allowed, declined or handed off, recorded with the policy version and the facts.
Action A refund or cancellation Chargeless decided on, with its status at the provider.
Case Everything about one request: its decisions, actions and timeline. Numbered per workspace.
Handoff Passing a case to your team (team queue, webhook or helpdesk) because the automation should not finish it.
Ticket A conversation with a customer by email, form, chat handoff or helpdesk. The automation answers first; after a handoff it is your team's.
Refundable remainder What is left to refund on a charge: the original amount minus refunds that succeeded or are under way.
Velocity limit A cap on how many refunds a customer, or how much your workspace, can get in a period.
Circuit breaker A safety limit that hands refunds to your team when they run far above your usual hourly rate.
Kill switch / emergency stop Turns every automatic money action into a handoff, at once.
Override A team member's refund or cancellation beyond the policy, with an authenticator code. Never past the safety limits.
Step-up Confirming it's you (authenticator code or password) before a sensitive action.
Early fraud warning (EFW) A card network's warning that a charge may be fraudulent, usually before a chargeback.
Dispute / chargeback A customer contesting a charge with their bank. An inquiry is a dispute's early stage.
Payment connection A link to a Stripe account or to your own payment system.
Merchant-hosted provider Your own payment system, connected through the merchant-provider/v1 contract.
Settlement currency The currency a connection pays out in.
Main currency Your workspace's currency: your policy's amounts start in it. Limits in your other currencies are added beside it.
Signed token A short-lived token your server signs to tell the widget who the signed-in customer is.
Email code (OTP) A six-digit code sent to the customer's email to prove who they are.
Matched level A lighter identity level for helpdesk and email tickets on merchant-hosted systems: identifiers in the ticket instead of a proof.
Simulator Replays a draft policy over your history without changing anything.
Conformance kit (providercheck) The tool that tests your own payment system against the contract.

The engineering glossary is in docs/glossary.md.