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
Tickets

Every channel lands in the same queue.

Chat, the widget form, email or your helpdesk. Automation answers first; once your team has a ticket, it stops.

Request early accessTickets: Overview

Chat handoffs

The ticket arrives with the masked transcript, the verified customer, the case and the reason. The chat closes, and your team replies by email.

  • The masked transcript attached
  • Your team replies by email
  • Acknowledged in their language
↪

Refund asked 45 days after purchase

Outside the 30-day refund window

High

Transcript · 6 messages

Reply due in 2 h
With your team
Illustrative example, not real data

Email inboxes, the widget form and web forms

Forwarded support addresses and forms open tickets. Replies go out from your inbox and answers thread back. Automatic replies are capped per sender each day.

  • Replies thread back
  • Widget contacts confirmed by code
  • Daily cap per sender

From: [email protected]

Re: Your request [#1182]

Thanks! Could you also cancel my plan?

↳ Threaded into ticket #1182

✓ Identity proven by email link

Illustrative example, not real data

Zendesk and any helpdesk

Connect Zendesk from the panel, or any helpdesk through a signed connector. As soon as an agent replies, automation stops writing.

  • Zendesk from the panel
  • A signed connector for others
  • An agent’s reply takes over

Zendesk ticket #18320

Customer: Where is my refund for #4821?

Chargeless: Your refund of €29.00 was issued on 16 Oct.

Agent replied · automation stepped back

Illustrative example, not real data

Where handoffs go

The team queue, a signed webhook, both, or your helpdesk. No request ever waits for approval.

  • Queue, webhook or helpdesk
  • Signed webhooks
  • No approval queue
Integrations settings in the merchant panel listing payment, helpdesk and webhook connections.
Illustrative example, not real data

More in Tickets

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