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
Payment providers

Not built for just one payment provider.

Stripe, PayPal, Paddle, FastSpring, Adyen, dLocal, Ecommpay, Nuvei and your own billing system, side by side in one workspace.

Request early accessRead the guide
Integrations settings in the merchant panel listing payment, helpdesk and webhook connections.
Illustrative example, not real data

Go live on Stripe with your history in place.

Connect one or more accounts. Up to a year of history comes in at go-live, so the first decision already knows it.

  • Several accounts
  • 30 to 365 days of history
  • Start in test mode

History import

365 days · customers, charges, refunds, disputes

Customers2,481
Charges18,904
Refunds1,122
Disputes37
✓ Imported
Illustrative example, not real data

Bring your own payment infrastructure.

Implement one open contract over REST or MCP. Chargeless reads your data and requests only approved actions.

  • REST or MCP
  • Signed requests
  • A conformance kit
# merchant-provider/v1
POST /v1/refunds
X-SupportRoute-Timestamp: 1761210000
X-SupportRoute-Signature: v1=9f2c…e41a
Idempotency-Key: 01a1…:chat:7f3c…:refund:tx_88

{
  "transaction_ref": "tx_88",
  "amount": { "amount_minor": 2900, "currency": "EUR" },
  "reason": "duplicate",
  "dry_run": false
}
Illustrative example, not real data

Limits per currency, never our own exchange rate.

Set every limit per currency. A payment is compared in its currency or its recorded settlement amount, or handed off.

  • Limits per currency
  • Totals per currency
  • Provider settlement amounts

Up to €100 is refunded automatically

EUR€100.00
USD$120.00
GBP£90.00
TRYTRY 4,000.00
Illustrative example, not real data

Frequently asked questions

Can’t find your question?

See every question merchants ask, or ask us when you request access.

All questionsRequest early access
01Which payment providers are supported?

Stripe, PayPal, Paddle, FastSpring, Adyen, dLocal, Ecommpay and Nuvei, and any system implementing our provider contract. Using another one? Tell us when you request access.

02Can I connect multiple accounts?

Yes. A workspace supports up to ten payment connections, with provider accounts and your own systems side by side.

03What happens when a connection is disabled?

Requests for its payments are escalated to your team. No action is ever executed on a disabled connection or one that is not yet live.

Related

Start with low limits. Raise them when the record shows it works.

Start in test mode, run your policy against your own history, and go live when the results meet your standards.

Request early accessHow it works
  1. 1A test workspace on your provider’s test mode
  2. 2Your past requests replayed against your policy
  3. 3Live with low limits, raised as the record allows