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
Use cases

Large amounts, where a person should decide.

A tour operator takes deposits and full payments. Most requests are clear; some are large.

Request early accessUse cases: Overview

Automate the small and clear

Below your limit, refunds run on their own. Above it, the ticket reaches your team with the chat, the payment and the reason.

  • An automatic limit per currency
  • The handoff reason in plain words
  • Refund from the ticket within policy

The tour on 2 Nov was cancelled. I need the €640 back.

This is above the amount I can refund on my own, so I have passed it to the team with your booking and payment. They will reply by email.

Handed to your team

Work in Zendesk

Handoffs open a Zendesk ticket. Your agents never leave the tool they already use.

  • One Zendesk ticket per handoff
  • Signed webhook as an alternative
  • Exceptions need an authenticator code

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

Answer on time

Response targets per channel notify your team before a ticket goes late. They never act on their own.

  • SLA targets
  • Ticket analytics
  • Notifications, never actions
Ticket analytics, SLA targets: first reply and resolution targets met, next reply breaches, targets by priority and tickets due soon or overdue.
Illustrative example, not real data

More in Use cases

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