Who uses Chargeless, and for what.
Six example businesses and the payment requests they no longer answer by hand. The businesses are illustrative; every step is something Chargeless does today.
- 1Verify the customer
- 2Decide on your policy
- 3Refund or cancel once, or hand to your team
A subscriber wants out, and last month back.
A project tool bills monthly through its payment provider. “I forgot to cancel” used to wait a day in the queue.
Requests it settles
- “Cancel my plan”, with one offer you choose shown first
- A renewal charged after the customer forgot to cancel
- A duplicate charge on a plan change
- Which plan they are on and when it renews
A policy to start with
- Refund window
- 14 days from the renewal
- Automatic up to
- €50 · $55 · £45
- Cancellation
- At period end, after one offer
- Last renewal
- Refunded when unused
Example values; you set your own.
I forgot to cancel and got charged €19 again.
Your Pro plan renewed on 1 Nov and has not been used since. I can cancel it now and refund the €19.00 to Visa •• 4242.
Cancelled and refundedLeft to your team
- Annual plans above your limit
- A customer refunded already this month
Charged twice, or the order never arrived.
An online fashion store. After every campaign, the inbox fills with payment questions.
Requests it settles
- Charged twice for one order
- A cancelled order that was still charged
- “My order never arrived”, with tracking from your system
- Chargebacks answered with the delivery evidence
A policy to start with
- Refund window
- 30 days from payment
- Automatic up to
- €100
- Reasons
- Duplicate, cancelled order, not received
- Guest checkout
- Verified with an email code
Example values; you set your own.
I was charged twice for order #4821.
I found two charges of €29.00, on 13 and 14 Oct. Shall I refund the second one to Visa •• 4242?
RefundedLeft to your team
- Returns that need the item back first
- Orders above your limit
Small payments, fraud warnings by the dozen.
A game studio sells credits on the web. Stolen cards arrive as early fraud warnings.
Requests it settles
- Early fraud warnings on stolen cards
- Credits bought by mistake and not used
- Repeated refund requests from one account
- Disputes on small purchases
A policy to start with
- Fraud warnings
- Refunded automatically up to €150
- Automatic up to
- €20 per request
- Per customer
- At most 2 refunds in 30 days
- Circuit breaker
- Stops refunds on an unusual spike
Example values; you set your own.
I bought 1,000 credits by mistake.
Your €9.99 purchase on 12 Nov is unused, so I can refund it to the PayPal account you paid with.
RefundedA student wants the guarantee honoured.
An online course platform offers a 14-day money-back guarantee. Requests peak when a cohort starts.
Requests it settles
- The money-back guarantee, as a rule
- Cancelling the rest of an instalment plan
- Requests sent to your support inbox
- Students writing in their own language
A policy to start with
- Guarantee
- 14 days from enrolment
- Automatic up to
- The full course price
- Instalments
- Remaining payments cancelled
- Channels
- Chat and your email inbox
Example values; you set your own.
The course is not for me. Can I get my money back?
You enrolled on 3 Nov, inside the 14-day guarantee. I can refund the €149.00 to Mastercard •• 5100.
RefundedLeft to your team
- Requests after the guarantee period
- Invoiced or corporate enrolments
Large amounts, where a person should decide.
A tour operator takes deposits and full payments. Most requests are clear; some are large.
Requests it settles
- Duplicate deposit charges
- Refunds for bookings you cancelled
- Large refunds prepared for your team
- Tickets in Zendesk with the case written up
A policy to start with
- Automatic up to
- €100
- Reasons
- Duplicate deposit, cancelled booking
- Above the limit
- To your team, written up
- Helpdesk
- Zendesk, with response targets
Example values; you set your own.
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 teamMany accounts, many currencies, one policy.
A retailer runs one payment account for Türkiye in TRY and one for Europe in EUR.
Requests it settles
- Refunds on a TRY account and a EUR account from one chat
- The right account chosen by the payment itself
- Limits stated in each currency
- Payment analytics per market
A policy to start with
- Connections
- One per payment account
- Limits
- ₺2,000 · €100 · $110
- Conversion
- None: each charge in its own currency
- Disabled account
- Its requests go to your team
Example values; you set your own.
Siparişimin parasını iki kez çektiniz.
₺749,00 tutarındaki ödemenin iki kez alındığını gördüm. İkincisini Troy •• 3301 kartınıza iade edeyim mi?
Refunded, in the customer’s languageLeft to your team
- A charge in a currency with no limit
- Requests on a disabled connection
Frequently asked questions
See every question merchants ask, or ask us when you request access.
All questionsRequest early access01Are these real customers?
No. They are example businesses that show how the product works. Every feature on these pages exists today.
02Which payment providers can I use?
Stripe, PayPal, Paddle, FastSpring, Adyen, dLocal, Ecommpay and Nuvei, and your own billing system through one open contract over REST or MCP.
03Can I start with one kind of request?
Yes. Start with a narrow policy, for example small refunds in chat, and every other request goes to your team.
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.
- 1A test workspace on your provider’s test mode
- 2Your past requests replayed against your policy
- 3Live with low limits, raised as the record allows