E-commerce
June 28, 2026
The return is validated. The Shopify refund is processed on Tuesday. On Thursday, the customer writes in angrily: Alma has just charged the 3rd installment. Your agent replies "contact Alma". The customer rates 1 star: "The shop and the financing provider are passing the buck."
This scenario is not a generic BNPL dispute. It is a split-payment operational incident: merchant refund / payment schedule desynchronization, incorrectly recalculated partial amount, unexplained credit timeline, or a store credit that left the payment plan active.
This guide #194 covers customer service support for installment payments at the ops level: incidents, refunds, schedules, and reconciliation. More specific than general BNPL support (Klarna questions, who answers what). Here: refund execution and incident management.
Summary
Why are split payment failures a distinct operations issue?
A payment in 3 or 4 installments creates two parallel flows: shop order (shipping, return) and financing contract (direct debits, schedule). When one progresses without the other, support becomes a reconciliation post, not product advice.
Cost of a poorly handled incident
Double contact: shop ticket + financing app for the same refund
BNPL Chargeback: customer disputes the remaining direct debits
Merchant Clawback: reversal of settlement already recorded
CSAT: customer blames the brand for a "system" bug
ShopAppy points out that a refund outside the provider flow leaves the schedule active and can trigger a double payment without a clean trace (ShopAppy, disputes BNPL). Chargeflow estimates that 34 to 41% of BNPL users have experienced at least one payment delay (Chargeflow, BNPL statistics 2026): the slightest confusion regarding the schedule amplifies customer stress.
DTC figures example
Cosmetics, 22% Alma/Klarna orders, 38 tickets/month "direct debit after return". Root cause: Shopify refund OK but Alma sync at D+4, customer debited in the meantime. Incident process + delay macros: −62% repeat tickets, resolution delay 9 days → 2.5 days.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does this guide differ from general BNPL support?
Three neighboring pieces of content, three levels of depth.
General BNPL Guide
BNPL Support: question mapping, store vs. financier matrix, chatbot intents, WISMO scripts. Indispensable beforehand, but it does not detail each type of refund incident.
Payment declined (# conversion)
Payment declined deals with checkout failure (3DS, limit, retry). #194 comes into play after the order is confirmed in installment payments.
Communication disputes
Reduce payment disputes covers statement descriptors and preventive messages. #194 covers ops execution when the damage has already occurred.
Promise #194
Incident taxonomy, full/partial refund workflows, financier sync playbooks, reconciliation, and KPIs. You will know what to do at D+0, D+3, and D+10 on each case.
Which operational incidents should be mapped as a priority?
Before macros and helpdesk rules, tag the split incidents from the last 90 days of tickets.
Ops taxonomy (recommended tags)
inst_refund_delay: merchant refund OK, payment schedule not adjusted
inst_partial_mismatch: partial return, payment installment amount inconsistent
inst_cancel_pre_ship: cancellation before shipping, still charged
inst_store_credit_error: store credit issued, BNPL plan still active
inst_wrong_amount: charge ≠ order or refund amount
inst_provider_dispute: dispute opened on Klarna/Alma side
Quick mining
Gorgias/Zendesk export: filter orders tagged alma, klarna, shop_pay_installments. Group verbatims "charges", "installment", "refunded but". Cross-reference with tag conversations and ticket taxonomy.
Volume prioritization
In 80% of DTC stores, inst_refund_delay and inst_partial_mismatch dominate. Address these first in your SOPs.
How do I perform a full refund on a split order?
The total split-payment refund follows a strict order. Reversing the steps creates the incident.
7-step Workflow
Confirm receipt of return at warehouse or cancellation before full capture
Initiate refund within Shopify/admin to the original BNPL flow (never via direct card if Alma/Klarna)
Verify refund status: captured, pending, failed
Wait for provider sync (often 1 to 5 business days) or force via BNPL merchant portal
Capture refund transaction ID + timestamp
Communicate realistic payment schedule timeline to customer (5 to 14 days depending on bank)
Close ticket only after provider confirmation or after internal SLA is exceeded with escalation
Shop Pay Installments / Affirm
Shopify specifies: refund goes back to the client; interest already paid is non-refundable; store credit or gift card does not adjust the Affirm plan, the client must continue to pay (Shopify, Shop Pay Installments). Ops prohibition: refunding as store credit on installments orders.
Day-0 customer script
"We have initiated the full refund of €156 to Alma today. Your remaining installments will be cancelled within 5 to 10 business days in your Alma app. Shopify refund reference: #R-8842. I will get back to you if the sync is not visible within 7 days."
How to manage a partial refund and the recalculation of the payment schedule?
The split partial refund is the #1 source of error in support ops.
Basic rule
Refund the exact amount of the returned items, not a rounded goodwill gesture. The financing provider recalculates future installments or credits past installments according to its engine.
Calculated example
Order €240 in 4×€60. Return of an €80 item. Shopify Refund: €80 exact. Customer expectation: either 1 installment cancelled + adjustment, or €80 credit split across installments. Common error: €75 refund "gesture" → inconsistent payment schedule, inst_partial_mismatch ticket.
Edge cases
Partial bundle: see partial bundle returns
Unrefunded shipping costs: explain before refunding, not after
Product exchange: new separate order, not a partial BNPL refund
Post-partial refund communication
"We have refunded €80 on your order #4521 via Klarna on 18/06. Klarna automatically adjusts your next installments: check the app within 48-72 hours. If the displayed amount does not match, send us a screenshot and refund ID #…"
What to do when the financier is still debiting after a merchant refund?
Incident inst_refund_delay: the most emotional one for the customer.
Diagnosis in 15 minutes
Shopify: refund status succeeded? Exact amount?
Refund date vs. customer debit date
Alma/Klarna merchant portal: refund visible?
Does the customer have multiple active orders (confusion)?
Store actions
D+0 to D+2: reassure + provide proof of refund (admin screenshot)
D+3 to D+7: BNPL merchant support ticket with order ID + refund
D+7+: ops escalation + VIP escalation if LTV is high
CFPB 2026 Rule (US markets)
Since March 2026, US BNPL providers must credit the installment balance within regulated timeframes; Loop Returns and AfterShip have adapted their workflows (Ecommerce Times, CFPB 2026 rule). In EU/FR, aim for the same ops standard: customer credit within a maximum of 2 billing cycles.
What you must never do
Refund the customer's card in parallel "to compensate": double payment guaranteed. Always go through the provider's flow (ShopAppy, BNPL addition).
How to document each file to avoid disputes?
Documentation is your defense in a BNPL dispute.
Minimum file requirements (6 documents)
Shopify refund screenshot (amount, date, ID)
Proof of return receipt or cancellation before shipping
Customer ticket history (avoid contradictions)
Package tracking if the dispute is "not received"
Email exchanges with timestamp
Status of the BNPL merchant portal at the time of the dispute
Provider dispute window
Klarna Shopify: client contacts you first; if unresolved within 21 days, Klarna reaches out to you with 7 days to respond (Klarna, post-purchase Shopify). Prepare the file from the very first ticket, not on day 20.
Chargeback link
See chargeback prevention and split funding for the overall framework.
Which helpdesk workflows to route split incidents?
The incident matrix must live in Gorgias, Zendesk or equivalent.
Rules WHEN/IF/THEN
IF alma/klarna tag AND the word "prélève" post-refund → inst_refund_delay tag, priority P2, assign to ops team
IF partial refund AND BNPL tag → inst_partial_mismatch tag, recalculation delay macro
IF store credit issued AND payment installments → inst_store_credit_error tag, immediate escalation to finance
Ops views
"Installments open" queue: unresolved inst_* tags, sorted by refund date. Internal SLA: first response 4 h, client update every 48 h as long as sync is pending.
Bot-aligned macros
The bot looks up order: refund status, BNPL tag, return date. Never auto-closes an inst_refund_delay ticket without the "provider_sync_confirmed" field. Handoff if dispute threat or 3rd contact: bot handoff (#12).
What deadlines should be communicated according to Alma, Klarna, and Shop Pay?
Realistic timelines reduce repeat tickets by 40 to 60%.
Customer table (FR/EU base)
Alma: merchant refund 1-3 business days; plan adjustment 5-10 days; bank credit up to 10 days (Alma help)
Klarna: Shopify refund sync often 3-7 days; Klarna app updated afterwards
Shop Pay Installments: refund original payment method; interest not refunded; no adjustment via store credit
PayPal 4x: PayPal refund, payment schedule adjusted on PayPal's end within 5-14 days
Timeline template by phase
D+0: "Refund initiated". D+3: "Financier sync in progress, normal if recent charge". D+7: "Merchant portal verification". D+10: provider escalation or framed commercial gesture if store fault is proven.
Consistent return policy
Your return page must mention the BNPL timeline, not just "refund within 14 days". See return policy and store credit vs refund.
Which KPIs and financial controls for split payments?
Ops support must feed the BNPL reconciliation.
Support KPIs
inst_* tickets / BNPL orders: target < 3%
inst_refund_delay resolution time: target < 5 days
Repeat contact same incident: target < 15%
Dispute rate BNPL vs card: gap > 3 pts = process alert
Weekly finance reconciliation
ShopAppy recommends line-by-line reconciliation settlement provider vs Shopify refunds (ShopAppy). Column: order ID, refund date, clawback settlement, inst_* ticket status.
Monthly review
Top 3 incidents by volume. One root cause + one helpdesk rule per month. Share with response library to avoid drift among agents.
How does Qstomy reduce incidents on installment payments?
Qstomy reads the Shopify order status (refund, BNPL tags, return) and responds with the correct provider timeframe before the customer panics.
Incident-oriented features
Live refund lookup: status, amount, date, provider
Intents inst_*: responses aligned with ops macros
Auto tag inst_refund_delay if refund < 7 days and charge inquiry
Handoff pack: refund ID + history for tier 2
Store credit block: alert if agent attempts credit on installment orders
Quantified DTC Scenario
Home decor brand, 31% Alma, 52 inst_* tickets / month, incident CSAT 2.8/5. Deployment of Qstomy lookup refund + inst_* tags + 6 provider delay macros. After 10 weeks: inst_* tickets -58%, repeat contacts -44%, average resolution time 2.1 days, BNPL dispute rate -0.6 pt vs card.
Explore AI customer support, Shopify integration, request a demo.
Which operational playbooks should be launched this week?
Playbook 1: incident audit (3 hrs)
Export 90 days of BNPL tickets. Classify into 6 tags from section 3. Top 2 = first SOPs to write.
Playbook 2: full refund SOP (2 hrs)
Workflow section 4 by active provider. Store credit on installments prohibited. Test 3 sandbox orders.
Playbook 3: delay macros (1 hr)
4 templates Day+0, Day+3, Day+7, escalation section 9. Align bot and agents.
Playbook 4: helpdesk rules (2 hrs)
3 rules section 8 + "Installments open" view + SLA 48 hr customer update.
Playbook 5: W+2 reconciliation (1 hr)
Export Shopify refunds vs BNPL settlement from week N-1. Link each clawback to inst_* ticket or create a ticket.
Useful links
Split payment converts at checkout. Your credibility is at stake when a refund takes 8 days to reflect in the Alma app and you can explain, prove, and track every step.
Enzo
June 28, 2026
