Use cases

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.

The customer asks in chat

They are signed in, so your app vouches for them: no code to type. They pick the charge and confirm the amount on a card.

  • Identity from your signed-in session
  • Only their own charges, masked
  • Nothing moves until they confirm

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 refunded

Your policy decides

Renewal 2 days ago, inside your 7-day window: refunded and cancelled at once. Renewal 20 days ago: handed to your team with the chat.

  • Refund window and limit per currency
  • Velocity limits per customer
  • The outcome card comes from the record

Refund requests

Published v12 · draft has 1 change

1
Who is asking is verifiedSigned login or email code
On
2
The charge is at most 30 days oldOtherwise: escalate to the team
Edited
3
Up to €100 is refunded automatically$120 · £90 · ₺4,000
On
4
At most 3 refunds per customer in 30 daysAdjustable, never removable
Locked
1 unpublished changeReview and publish
Illustrative example, not real data

Your team sees the whole subscription

Charges, failed renewals, refunds and every case on one page, linked by case number.

  • Subscriptions view
  • Cancel from the panel within policy
  • Every decision explained
A subscription’s page: its status, plan and price, totals per currency, its charges and payment attempts, and the Cancel subscription button.
Illustrative example, not real data

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.

  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