ActaSeal

Find the refunds that broke your rules, and the money they cost.

Drop a refunds export from Razorpay or Shopify and see which refunds went past your limit, were paid twice on one order, were bigger than the order or came after your return window, with the money each one cost. Your file stays in your browser.

For D2C and e-commerce brands, quick commerce and fintechs that issue refunds, by people or by AI agents. When an agent issues them, the same rules can check each refund before the money moves.

The check is free, in your browser, and nothing is uploaded. The full audit is run by us under NDA, in five working days. Or check a sample record yourself.

Refunds with no GST credit note lose that GST after 30 November →

Refund check · made-up data

4 of 50 refunds broke your rules

INR 25,598

  • Problems across orders and customersINR 4,418
  • Accepted, still not paidINR 450
  • Refunded with no GST credit noteINR 3,250
Run it on your own export →

What the check shows

Fifty made-up refunds from a company that does not exist: four broke the written rule, six more problems show only across orders and customers, two accepted refunds are still unpaid, and three orders were refunded with no GST credit note. Each comes with the money involved.

The top of the refund check on made-up refunds: the money each kind of problem cost, and the refunds that broke the written rule.

See the full sample, or run it on your own export. Made-up data, not a real company.

When an AI agent issues your refunds

It decides before the money moves.

Each payment your agent attempts is checked against rules you set, before it runs. It goes ahead, is stopped, or is sent to a person for approval.

So a refund that breaks your rules is caught before it is paid, not found at month end.

It leaves a record nobody can quietly change.

What was decided, and why, is written down in a form that shows any later change.

So when a dispute or an audit comes, the answer is already written down, not rebuilt from logs.

Your customer can check it without you.

They do not need your account, your software, your word or ours.

So a disputed refund is settled on the record, not on whose word is believed.

Start with a refund audit

Send an export of your recent refunds and your written refund rules. Within five working days you get a report of which refunds fell outside the rules and how much money was at issue. Nothing connects to your systems. What the audit finds

  1. 1

    Refund audit

    Five working days, on an export. Shows what already went out.

  2. 2

    Paid pilot

    Three weeks in your test environment. Each refund or payment is checked before the money moves.

  3. 3

    In production

    The same checks on every refund or payment your agent makes.

After the audit, a paid pilot checks each refund or payment before the money moves. Scope is agreed on a call.

Check a record yourself

Open a sample payment record and check it in your browser, the way your customer, their bank or their auditor would: no account, no call, no software from us.

Check a sample record yourself

Building the agent that issues the refunds?

If you build AI support or payment agents for brands, those brands will ask why the agent paid what it paid. Talk to us about giving them an answer they can check themselves. sales@actaseal.com

What regulators are asking now

Talk it through

Twenty minutes on what your agent does with money, and whether an audit or a pilot fits.

Book a 20-min call
Check your refunds now