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

A queue that shows what needs a reply first.

Your team works handed-over requests here: awaiting a reply first, the conversation and the payment side by side.

Request early accessTickets: Overview

The queue and the ticket, side by side

Queue, conversation and customer in one view on a wide screen. Each ticket shows its channel, status, response target and who handles it: Automation, Team or External.

  • Split pane from 1024 px
  • Automation, Team or External
  • Notified when a ticket arrives
Ticket queue in the merchant panel with a handed-off chat open, the reason it reached the team and the customer’s payment.
Illustrative example, not real data

Ready-made views and your own

Awaiting a reply, New, Team queue, Assigned to me and more. Filter, then save a view for yourself or share it with the team.

  • Ready-made views
  • Saved views, private or shared
  • Six statuses, four priorities

Needs a reply

SubjectWhy it came to youChannelDue
Refund after 45 daysOutside windowChat2 h
Charged in two currenciesNeeds a conversionEmail5 h
Talk to a person pleaseRequested a personZendesk7 h
Refund €240 headphonesOver auto limitChat1 d
Illustrative example, not real data

Assignment, notes and macros

Assign, reply by email or leave an internal note from one composer. Macros insert a saved reply with placeholders; they never send or move money.

  • Replies by email
  • Internal notes
  • Macros never send

Ticket #1182 · Refund €240 headphones

The headphones stopped working after six weeks. Can I get a refund?

Sorry about that. I have refunded the full amount to your card.

Refund €240.00 · beyond policyExecuted

Second factor confirmed · recorded

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