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 support that resolves itself.

Chargeless answers your customers’ payment questions, confirms who they are and refunds or cancels at your payment provider when your policy allows it. It answers disputes with evidence and refunds fraud warnings early. Everything else reaches your team, already written up.

Request early accessSee how it works
  • The model never moves money
  • Every decision on record
  • No card numbers stored
Case cs_7Hq2 · Chat on your site
  1. Customer asked“I was charged twice for order #4821. Can I get my money back?”14:02:07
  2. Identity verifiedEmail code to j•••@example.com14:02:31
  3. Payment foundVisa •• 4242 · €29.00 · 14 Oct · duplicate of 13 Oct14:02:32
  4. Policy v17 allowed itEach step checked in orderKill switch offWithin 30 daysUp to €1003 refunds / 30 days14:02:32
  5. Refund executed€29.00 back to Visa •• 4242, after the customer confirmed14:02:40
Executed at Stripekey chat:s_81f2:refund:ch_3PqK
Example case. Names and amounts are illustrative.
8 + 1Payment providers, plus your own billing system
3Outcomes only: executed, denied with a reason, or handed off
1Recorded action per intent, sent with the same key on every retry
0Card numbers stored. Card data stays with your payment provider
Refunds, cancellations and disputes at

The payment requests your team answers today, handled end to end.

Each of these runs on its own, inside the limits you publish. When a case falls outside them, it lands in your team’s queue with everything they need.

Automatic refunds and cancellations

Duplicate charges, unwanted renewals, cancelled orders. Settled in chat or email, at your provider, in seconds.Learn more

Automatic dispute responses

Evidence assembled from the provider, your history with the customer and your own records, then submitted before the deadline. Stripe first, more providers to follow.Learn more

Early fraud warning management

When a card issuer reports fraud, the payment is refunded under your rules before it turns into a chargeback and a dispute fee.Learn more

Payment analytics

Approval rates, decline reasons, countries, issuers and card network programme standing, with alerts when something moves.Learn morePayment Analytics in the merchant panel: approval rate, declines, dispute rate and the daily chart.

The model reads the request. Your policy makes the decision.

Every request takes the same path, in the same order, and ends in exactly one of three outcomes. Pick a case below or watch them run.

05 / 05

One outcome, on record

Executed at your provider once, handed to your team with the case written up, or denied with a reason the customer reads.

Executed

€29.00 refunded to Visa •• 4242

Example cases. Amounts are illustrative.

Automation your finance team can sign off on.

These rules are built into the platform. They hold for every request, every channel and every payment connection, including actions your own team takes.

  • The model proposes, the platform decides

    No tool given to a model calls a payment provider or writes to your records.

  • Identity before any detail

    A signed login, an email code or a one-time link binds the customer before a payment is shown.

  • One action per intent

    Each refund is recorded with its own key before it is sent; a retry reuses that key instead of starting a new refund.

  • Every decision on record

    Policy version, facts and outcome are kept for each request, and can be replayed in the simulator.

  • Limits that cannot be switched off

    Refund velocity per customer and workspace, a circuit breaker and a kill switch. You tune them; nobody disables them.

  • No card numbers, ever

    Card data stays with your payment provider; we only show a card’s brand and last four digits. Names, emails and messages are redacted before anything is logged.

Security

Works with the providers and tools you already use.

Connect each payment account in Settings, run several accounts in one workspace, or connect your own billing system through one open contract.

Where your customers ask

  • Chat widgetOne script tag, under 50 KB
  • Help siteOn your own domain
  • EmailReplies in your name
  • Your web formRequests from your site
  • ZendeskTickets in, replies out
  • WebhookAny other helpdesk
ChargelessYour policy decides. Every action is recorded once, then sent to the provider of the payment.

Where money moves

What each connection does

  • Refunds, subscription cancellations, dispute evidence with Visa CE 3.0, early fraud warnings and guest payments.

    RefundsSubscriptionsDisputesFraud warnings

  • Refunds, cancellations read back, disputes accepted or answered with evidence, an hourly account feed.

    RefundsSubscriptionsDisputes

  • Refunds and webhooks for card processing.

    RefundsWebhooks

  • Merchant of record. Refunds, cancellations and order line items, connected with one paste.

    RefundsSubscriptions

  • Merchant of record. Refunds, cancellations and order line items.

    RefundsSubscriptions

  • Refunds read back, Nuvei subscriptions cancelled, first chargebacks and fraud reports handled.

    RefundsSubscriptionsFraud reports

  • Refunds across local payment methods, with payments read back.

    RefundsLocal payment methods

  • Refunds and the go-live history import through its Data API.

    RefundsHistory import

  • Implement one open contract over REST or MCP, and check it with the providercheck kit before going live.

    RESTMCPConformance kit

All integrations

You pay for what gets resolved.

Three parts, each on a monthly statement you can check line by line. Model costs are included; there is no separate bill for model usage.

  • Platform

    A monthly fee

    For your workspace, your team’s accounts and every channel.

  • Resolutions

    Per request resolved automatically

    A refund, a cancellation or an answer that needed no one from your team.

  • Outcomes

    Per subscription kept and dispute won

    A flat fee, charged only when the renewal is paid or the dispute is won.

Billed in US dollars. During early access, pricing is set per merchant.Talk to us about pricing

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