Refund batch rejected: UK acquirer recovery runbook

Acquirer-specific rejection patterns

Step 1: read the rejection code

Acquirer dashboards return rejection codes that tell you which path to take:

• insufficient_balance: the most common; just wait or top up
• batch_threshold or daily_limit: refund total exceeded daily cap; split into smaller batches or call account manager
• risk_review: the acquirer is flagging the refund pattern; needs support contact and evidence
• refund_window_closed: too long since the original transaction (typically 180 days max in UK)
• different_card: attempting to refund to a card other than the original; not allowed by most UK acquirers
• technical_failure: retry; if persistent, support ticket

Step 2: check the balance

Most UK acquirers refund from pending balance. Two distinct balances to know:

• Pending balance: transactions processed today, not yet settled. Cannot fund refunds.
• Cleared balance: settled funds, available for payouts and refunds.

If the cleared balance does not cover the refund batch, three options:

1. Wait for the next settlement to clear. Usually 1-3 business days.
2. For Stripe: ensure the linked bank account has enough; Stripe will pull the shortfall.
3. For SumUp / Square: deposit funds via bank transfer to the acquirer-linked balance (not all acquirers support this; check first).

Step 3: re-submit

Once the balance covers the batch, most acquirers auto-retry. Stripe retries every 24 hours for up to 5 days. SumUp and Square require manual re-submission. Dashboard path:

• Stripe: Dashboard > Refunds > auto-retry, or Refund again button
• SumUp: Transactions > locate transaction > Refund again
• Square: Transactions > locate > Refund
• Dojo: Hub > Transactions > Refund
• Adyen: Customer Area > Transactions > Refund

Step 4: customer-side communication

Refund delays are the most common driver of chargebacks. While the acquirer side resolves, communicate to the customer:

• Confirm the refund is being processed and there is a temporary delay
• Provide an estimated landing date (cleared balance + 5-10 business days for issuer credit)
• Offer the ARN code (Acquirer Reference Number) so the customer's bank can trace it
• Document the conversation in your support tool to defend any chargeback that follows

Customers who receive proactive communication chargeback far less often than those left in silence.

Step 5: alternative refund routes

If the acquirer cannot process the refund or the timeline is unacceptable to the customer, alternatives:

• Bank transfer: direct to customer's bank account. Fast, no chargeback risk. Requires customer's sort code and account number.
• Open Banking link: Tide, Starling and similar UK banks let you send a payment link (refund). Customer authorises and funds clear immediately.
• PayPal: if customer has PayPal. Same-currency, often free.
• Cash (in-person retail / hospitality): hand it back at the counter. Document on the till.

Document the alternative refund clearly in your records as a credit against the original transaction. If the customer later chargebacks the original transaction, your evidence pack must include the alternative refund.

If the rejection is risk-flagged

Risk-review rejections need a support ticket plus evidence. Common patterns and what to send:

• Sudden refund-rate spike: explanation of cause (faulty product line, mass cancellation event), customer correspondence, plan for normalising the refund rate
• Refund to different card: almost always rejected. Acquirer needs proof the original card is closed (issuer letter) before allowing a different-card refund
• High-value refund (single): invoice, customer correspondence, reason for the refund, dispute prevention rationale
• Refunds to high-risk geographies: evidence of legitimate customer relationship

When to escalate to the FOS

If the acquirer rejects without justification, fails to respond, or causes a refund to be permanently lost, the route runs:

1. Formal complaint to the acquirer in writing.
2. 8-week resolution window under PSR 2017.
3. FOS escalation if unresolved.

FOS can order the acquirer to process the refund, plus compensation.

Pre-empt the next batch failure

1. Hold a 7-day cleared-balance buffer. Refunds clear from cleared balance; running tight means batch failures.
2. Process refunds promptly. Refunds within 48 hours of customer request reduce chargeback rate by ~40% in UK SMB merchant data.
3. Set up Open Banking link as backup. Tide, Starling and most challenger banks include this free.
4. Track refund rate weekly. Above 5% refund rate, expect acquirer attention. Above 10%, expect risk review.
5. Use the same card for refunds as the original. Always.