ScenarioD2C Fashion Retailer

Faster, Trackable Refunds for a D2C Brand

An illustrative D2C fashion retailer moves refunds off a manual net-banking process: online payments are refunded against the original payment, cash-on-delivery refunds go out as payouts to verified accounts, and support can see every refund's status.

Illustrative scenario, not a customer case study. It shows how this kind of business could set up its payments; which capabilities LILPE provides for your business is confirmed during onboarding. No measured results are claimed.

The challenge

Refunds were the top source of customer complaints

As orders grew, so did returns and cancellations. Every refund was keyed into a bank's net-banking portal and matched by hand against the order, which took days and produced a steady stream of 'where's my refund?' tickets that support couldn't answer without asking finance.

The approach

Refunds tied to payments, and one status for everyone

The brand separates refunds by how the customer paid, and ties each refund to its order and payment.

Online payments refunded against the original payment, back to the same card or UPI account
Cash-on-delivery orders refunded by payout to the customer's verified bank account or UPI ID
Partial refunds for multi-item returns, calculated per item
Refund status sent to the support tool by webhook, so agents can answer immediately

What this setup changes

Refunds that can be traced and explained

How quickly money reaches the customer still depends on the payment method and the customer's bank. What changes is that the brand can always say where a refund is. Which refund and payout features LILPE provides for your business is confirmed during onboarding.

Every refund references its order and payment, so its status can be looked up directly
Support can answer refund questions without escalating to finance
Cash-on-delivery refunds no longer need bank details typed by hand

Decisions to make

What a brand like this has to decide

When is a refund triggered?: On cancellation before dispatch, on return pickup, or on return received and inspected. Earlier refunds please customers; later ones prevent refunding items that never come back.
Full or partial?: Multi-item orders need per-item partial refunds, including any shipping or discount rules. Write them down so every agent applies them the same way.
How are cash-on-delivery refunds paid?: There's no original payment to reverse, so they go out as payouts. Verify the customer's account or UPI ID before paying.
What does the customer see?: A refund reference and a realistic timeline for their method, sent when the refund is issued.

Watch out for

Where refunds go wrong

Refunding by bank transfer when the original payment was by card, which creates two records that don't match.
Refunding the same order twice because two agents acted on the same ticket; refund requests should be idempotent.
COD refunds paid to unverified details typed from a phone call.
A refund policy on the website that differs from what agents actually do.

Go deeper: Refunds handbook · Payouts handbook · Bank verification

Products in this setup

The products this scenario uses

Want refunds you can always explain?

Talk to LILPE about transaction-linked refunds and payouts for cash-on-delivery returns.

Talk to sales All scenarios