# Refund automation features: policy, approvals, audit

> Versioned refund policy, AI reasoning only where rules leave room, Slack and dashboard approvals, Stripe and PayPal execution and a full audit trail. See it all.

- Canonical URL: https://lumtry.com/features
- Last updated: 2026-09-24

Lumtry pairs rules that never drift with reasoning you can inspect, wrapped in durable workflows and a complete audit trail.

## Policy decides, AI advises, people approve

- **Deterministic policy engine**: Author versioned rules that decide the predictable cases the same way every time. Versions are immutable once published, and in-flight refunds pin the policy version they started on, so a rule change never rewrites a decision already in motion.
- **AI-assisted decisioning, always governed**: For the cases policy cannot settle on its own, model-assisted reasoning weighs the context through the typed model router and proposes a disposition, with the rationale attached. A new or changed policy can run in shadow mode alongside the live decision path first, so you see what it would have done before it decides anything.
- **Approvals wherever your team works**: Approve from the dashboard, Slack, Gorgias, Zendesk or a voice call. Every approval is checked against the case first.

## Execution you can audit

- **Stripe and PayPal execution, with compensation**: Approved refunds run as a durable workflow from intake through validation, policy, approval, and execution. If a downstream step fails, an explicit compensation step reverses what already happened, so nothing is left half-done.
- **Audit trail and correlation**: Every decision, signal, and override is append-only and tagged with a correlation ID that follows the case end to end. Auditors get a complete, immutable trail without asking engineering to reconstruct it.
- **Return-receipt gating**: When a refund is contingent on a physical return, execution waits for the return to actually arrive before money moves, closing the gap between approving a refund and paying one out early.
- **Usage-metered billing**: Refund volume is metered against your plan's entitlements, with usage held rather than silently dropped when a limit is reached, so nothing processes without your workspace being able to account for it.
- **Storefront and marketplace intake**: Shopify, WooCommerce and BigCommerce stores, plus Amazon and eBay, feed one case queue with integration health on every connection.

## See it on your own refunds

Connect a store and watch policy and AI handle the volume while your team handles the exceptions.

## Related

- [Home](https://lumtry.com/index.md): Decide refunds by a versioned policy, send the exceptions to your team in Slack or the dashboard, and keep every step on the record. Start free.
- [Pricing](https://lumtry.com/pricing.md): Lumtry plans by case volume and seats, from Free to Enterprise, with add-ons and capped outcome fees. Start free or hear when billing opens.
- [About](https://lumtry.com/about.md): Why Lumtry exists: refunds should be decided by a policy you can defend, reasoning you can inspect and approvals your team controls. Read the story.
- [Privacy](https://lumtry.com/privacy.md): How Lumtry collects, uses, shares and protects personal information, isolates tenant data, records AI rationale and lists sub-processors. Read the policy.
- [Terms](https://lumtry.com/terms.md): The binding terms for using Lumtry: policy plus AI reasoning with a human approval gate, plans and billing, and the limits of liability. Read them in full.
- [Trust](https://lumtry.com/trust.md): How Lumtry secures merchant data, keeps AI inside a deterministic refund policy, lists every sub-processor and explains data flow and retention. Review it.
- [Solutions](https://lumtry.com/solutions.md): Four ways Lumtry puts policy, approvals and an audit trail around the money you give back: refunds, returns and labels, chargebacks, retention and abuse.
- [Demo](https://lumtry.com/demo.md): Run a sample refund through intake, AI signals, policy, approval and audit in your browser. Change a rule, rerun the case and share the link. Try it now.
- [Integrations](https://lumtry.com/connectors.md): Connect Lumtry to Shopify, WooCommerce, BigCommerce, Amazon, eBay, Stripe, PayPal, Slack, Gorgias, Zendesk, EasyPost and Shippo. Browse every integration.
- [Contact](https://lumtry.com/contact.md): Questions about Lumtry, launch pricing, integrations or security? Send a message and the team replies by email. Tell us about your refund volume.
- [Get started](https://lumtry.com/get-started.md): Pick the refund problem to fix first, choose a plan and create your Lumtry account. Start on the Free plan and connect your store when you are ready.
- [Developers](https://lumtry.com/developers.md): Send signed refund webhooks to your tools, call the REST API and let your AI assistant work with Lumtry cases over MCP. Explore the developer tools.
- [Refund cost calculator](https://lumtry.com/calculator.md): Estimate a year of manual refund handling and return abuse leakage from your own numbers, then see which Lumtry plan fits your volume. Run the numbers.
- [Roadmap](https://lumtry.com/roadmap.md): What Lumtry has shipped, what is coming next and what is further out across refunds, returns, disputes and integrations. Get notified when items ship.
- [Compare](https://lumtry.com/compare.md): Lumtry side by side with the tools SMB merchants use for refunds today, built from each vendor's own public pages. Find the right fit for your store.
- [Guides](https://lumtry.com/guides.md): Answer-first guides to refunds, returns, chargebacks, approvals and audit trails for Shopify, WooCommerce and BigCommerce merchants.
- [Glossary](https://lumtry.com/glossary.md): Plain definitions of refund, return, chargeback, RMA, store credit, audit trail, idempotency key, MCP and other refund operations terms.
- [MCP server](https://lumtry.com/developers/mcp.md): Connect an AI assistant or your own agent to your refund workspace through the Model Context Protocol. Read cases and propose actions, never move money.
- [llms.txt](https://lumtry.com/llms.txt)
