A shopper returns a $16 kettle from a $40 purchase, paid with $25 on a prepaid card and $15 in cash. The math alone does not identify which tender should receive the $16. That route depends on the merchant’s approved return policy, payment processor and the original transaction record. First decide whether the item is returnable; then decide where the money can go. Don’t start with a guessed split.

Use the link the system already has

Open the original sale and verify item, amount, eligible tax adjustment, tender breakdown and any previous returns. Follow the approved linked-refund flow; let the system show which amount it routes to which tender. If the screen cannot link a return across lanes, stores or channels, involve the lead authorized for exceptions rather than issuing a second or unrelated refund. Keep any non-sensitive reference in the approved process so another shift can check the same record.

The Adyen documentation on referenced refunds illustrates why developers link a refund to the original payment and why acknowledgment of a request does not necessarily mean completion. Stripe’s refund destination guidance is another example: it routes refunds to the original payment method. Neither document settles what a different register may allow for a specific split-tender purchase.

If the original card isn’t available

“That card was replaced” does not automatically mean “refund another card” or “pay out cash.” Explain that you need the store’s approved return route and ask the lead to verify how this processor handles the original reference. Do not promise that the issuer will move the funds to a particular card or on a particular day. Offer only a confirmed receipt or reference through approved methods.

A useful closing sentence is precise: “We submitted the $16 refund through the original sale. This record shows it is pending.” That’s different from “It’s already on your card.” If the original sale itself was never completed, use the payment-state guide before creating any refund record.