Support operations · design partners

Resolve the ticket. Respect the refund limit.

A focused next workflow for commerce and SaaS support: let agents prepare bounded refunds, while your payment system enforces where the money goes and how much can be returned.

A narrow starting point

Refund a supported captured payment to its original payment method, in the original currency, within its remaining refundable amount. Requests above the approved limit go to a human.

No arbitrary destinations, cross-currency transfers or unbounded payouts in the initial scope.

Evidence tied to the payment

Connect the original charge, policy version, approval and provider response. Preserve pending or unknown outcomes until reconciliation establishes what happened.

Repeated requests must not create duplicate refunds. Concurrent requests must share trusted remaining-balance state.

Availability

This is a design-partner workflow, not a released refund connector. The local policy tools are available for evaluation today; they do not perform refunds or verify a provider’s transaction state.

We are looking for a support team with one provider and a clearly bounded refund process to validate before expanding.

Discuss a refund pilot