A customer wants cash after receiving store credit: reconcile both settlements

Retrieve the original return decision, store-credit issuance and every later use of that credit. Confirm the customer's current balance and currency before agreeing to another settlement. The amount initially issued may no longer be available because the customer has spent part of it. Also distinguish the credit connected to this return from unrelated promotional or purchased value in the same account.

Shopify documents separate actions to issue and decrease store credit, with changes recorded in the customer timeline. Use that history alongside the order and refund records. A manual balance decrease and a payment refund are separate actions that need a common case reference and an approved sequence.

Have the responsible team establish whether the customer is entitled to a cash refund or whether the business is offering a discretionary accommodation. Applicable consumer rights and original terms govern that decision. Finance should receive the approved amount and reason, not make a policy decision by moving the customer balance into whichever account is easiest to clear.

Suppose a hypothetical customer received $100 of return-related credit and then used $35 on another order. Only $65 of that original credit remains. Agreeing to replace the unspent amount with a $65 refund is different from refunding the original $100 while leaving the later purchase untouched. Any broader remedy needs its own commercial approval and accounting review.

Check whether another support agent has already requested the refund or adjusted the credit. Assign the case to one owner, and record the intended result before either action begins. This is especially useful when the store account and payment provider have different employee permissions.

Use the platform's supported adjustment and refund processes. Record the amount removed from available credit and the refund submitted against the eligible original payment. If one action fails, retain an explicit exception and tell support what the customer can currently use. Do not close the case merely because one screen shows the desired amount.

Coordinate timing so the customer cannot spend the same value while the replacement refund is being processed. Any temporary restriction must follow the business's approved process and applicable obligations. Protect customer access to unrelated balances. Where a platform cannot distinguish credit origins, maintain an external case calculation and obtain the required review before making a manual adjustment.

Match the credit adjustment, completed processor refund and accounting entries to the same approved amount. Confirm that the remaining customer balance includes only value that should still be available. Review connector behavior so a store-credit debit does not create a second revenue adjustment on top of the original return and the replacement payment event.

Keep evidence of the customer's revised settlement and the final transaction references. At month end, list conversions with credit already removed but refunds still pending, plus refunds completed while credit remains available. Those two exceptions require different actions. Repeated cases may indicate that the original return flow needs clearer customer choices and better coordination between account-credit and payment permissions.