The questions merchants ask before they switch it on.

No. The model only reads the request and proposes. The platform checks your published policy against stored facts (the payment, the refundable amount, the customer’s history, your limits) and only then records and sends the action. No tool given to a model can call a payment provider or write to your records.

Each action is recorded with one key per intent before anything is sent, and the provider receives that same key. A retry, a double click or a repeated message reuses the key instead of starting a new refund, and the result is read back from the provider.

Refund velocity per customer and per workspace, an amount limit per currency, a circuit breaker and a kill switch. You tune them in your policy; nobody can disable them, and they apply to your team’s refunds too.

Yes. The kill switch in the panel stops every automated action in your workspace immediately. Requests that arrive meanwhile go to your team.

Nothing waits on a person. Chargeless polls the provider for the outcome with a deadline; if no result arrives in time, the case is handed to your team with everything that happened so far.

With a signed login from your site, a one-time email code or a single-use link to the address on file. No payment detail is shown before that. A From header or a name typed in chat is never proof.

A clear reason written from your policy, never an improvised answer. If the case needs a person, it says so and hands it to your team.

Only if you want to. You can show one offer you choose, such as a pause or a discount, and cancelling always stays one press away. A subscription counts as kept only when its next renewal is paid.

English, Turkish, Spanish, Brazilian Portuguese, French, Arabic and Russian, in the chat and on the help site. The assistant answers in the customer’s language and in the tone you set.

They are handed off with a summary, the payment, the facts and the policy step that stopped them: to the team queue in your panel, your helpdesk or a signed webhook. Once a ticket is with your team, the automation does not reply on it again.

Yes, from a ticket or a payment page, through the same decision path. Going beyond the policy needs the override permission and a second factor, and it is recorded with the limits that applied. The kill switch, velocity limits and the refundable amount are never overridden.

Zendesk is supported directly; any other helpdesk connects through one signed webhook, and an email inbox can be connected too. Replies and handoffs go back to where the ticket came from.

Each dispute reason has an evidence plan. Chargeless gathers what the plan needs from the provider, your payment history and, if you connect one, your own evidence service, computes how strong the package is and submits it before the deadline. Stripe is supported first.

No. Your policy decides whether to contest or accept. The model writes only the argument, from facts prepared by code, and the draft is checked against those facts before it is sent.

It is a card issuer’s report that a payment may be fraudulent, often days before the cardholder disputes it. Refunding it under your rules avoids the dispute fee and keeps your card network ratios down.

Never. Card data stays with your payment provider, and Chargeless never receives card numbers. To help a customer recognise a payment, it only shows the card brand and the last four digits your provider reports.

The customer’s request and the facts needed to answer it, passed as data, not as instructions. It never sees card numbers or secrets, and messages about refunds or cancellations are built from the action records, not written freely.

Every record carries your workspace, every query is scoped to it, and the database enforces the same separation as a second layer. Names, emails and messages are redacted before anything is logged.

Stripe, PayPal, Paddle, FastSpring, Adyen, dLocal, Ecommpay and Nuvei, and your own billing system through one open contract over REST or MCP. Several accounts and providers can run side by side in one workspace.

A checklist in the panel: connect your payment account, publish a policy from a preset, choose where handoffs go, and add one script tag to your site. Your engineers only need the API if you want deeper links with your back office.

Yes. A test workspace connects only to your provider’s test mode, with test keys. You can replay your past requests in the simulator before you go live, and start with low limits.

A monthly fee, a fee per request resolved automatically, and a flat fee per subscription kept and per dispute won, billed in US dollars. During early access, pricing is agreed with each merchant.