E-commerce
July 1, 2026
"Why two charges on one order?" "When is the next debit?" "Amount different from what I expected." Three tickets where a poorly explained merchant split payment generates a double charge accusation and bank dispute.
The e-commerce multi-payment order support covers the payment schedule, deposit balance, and installment status for a single order. Distinct from BNPL Klarna: here, multiple scheduled merchant debits for a single order.
This guide #775 covers policy SPLITPAY-SUP, flows SP-1 to SP-8, and the matrix SPLITPAY-MAP. Support pair of the future bot SPLITPAY (#776).
Summary
Why do multiple withdrawals generate tickets?
The customer sees multiple statement lines for one order. The agent denies installment plans, confuses them with BNPL Klarna, or promises a single charge. Without a SOP, support routes this as a double charge or declined payment instead of explaining the merchant's schedule.
Five typical split payment friction points
Opaque schedule: direct debit dates are not mapped
Perceived double charge: deposit and balance read as a double charge map
Unexpected amount: installment amount different from cart map
Failed installment: one failed debit, not all map
Unclear status: how much remains to be paid map
An order may charge a deposit at checkout and the balance upon shipment (Shopify, 2026 payments). Without SPLITPAY-MAP, agents improvise schedules and amounts.
SPLITPAY #775 vs BNPL, AUTHCAP #773, double charge on mixcart and bot #776
Six contents, six distinct direct debit pathways.
Quick Matrix
#775 SPLITPAY: multiple merchant debits, one order, schedule, amounts
BNPL Klarna: third-party financier, distinct schedule, merchant debits
BNPL declined #785: declined scoring, distinct active schedule
AUTHCAP #773: two-step auth capture, distinct multiple installments
Mixed cart: mixcart, double charge, distinct subscription, scheduled split
#776 SPLITPAYbot: calendar bot, tier 1 status
#775 = scheduled merchant debits, one order. BNPL = Klarna Alma financier contract.
Which splitpay_* typologies should be classified?
Eight scenarios for multiple direct debit tickets per order.
Eight splitpay typologies
splitpay_schedule_explain: why multiple direct debits map
splitpay_calendar: dates of next direct debits map
splitpay_amount_mismatch: unexpected installment amount map
splitpay_double_perceived: double debit perceived for one order map
splitpay_failed_installment: one installment declined map
splitpay_deposit_balance: deposit balance explain map
splitpay_status_lookup: order payments status map
splitpay_refund_partial: refund of one installment map
Tags: splitpay, split_payment, installment_merchant. SCHEDULE-CITE: payment_schedule_copy map only.
How should the SPLITPAY-MAP matrix be structured?
The SPLITPAY-MAP matrix documents the multiple direct debit response for agents and future bot #776.
SPLITPAY-MAP Columns
splitpay_program_id: split payment map program identifier
payment_schedule_copy: explanation of direct debit schedule map
installment_amounts_copy: amounts per installment map
installment_dates_copy: direct debit dates map
split_trigger_copy: deposit trigger ship milestone map
failed_installment_policy_copy: declined installment what to do map
refund_installment_policy_copy: partial installment refund map
double_charge_explain_copy: deposit remaining balance not double map
bnpl_reroute_copy: Klarna Alma distinct merchant map
bot_intent_map: bot_splitpay_* #776 mapping
Sync helpdesk macros, split_payment order tags, and agent training SCHEDULE-CITE before AMOUNT-CITE.
SPLITPAY-SUP policy in six rules
Six rules supporting multiple debits per order.
SPLITPAY-MAP-GROUNDED: split response from map only
SCHEDULE-CITE: payment_schedule_copy cites map verbatim
AMOUNT-CITE: installment_amounts_copy cites map only
ORDER-LOOKUP-FIRST: transaction order before response
NO-BNPL-CONFUSE: bnpl_reroute_copy Klarna Alma distinct merchant map
BNPL785-REROUTE: BNPL scoring refusal → #785 distinct active calendar
SPLITPAY flow SP-1 to SP-8
Flow agent eight steps multiple withdrawals.
SP-1 Intake: splitpay_* intent + order_ref amount date bank_statement
SP-2 SPLITPAY-MAP: schedule amounts dates trigger failed refund double bnpl
SP-3 Transaction lookup: order payments transactions status verify
SP-4 Classify: schedule calendar amount double failed deposit status refund
SP-5 Triage: SCHEDULE AMOUNT NO-BNPL BNPL785 AUTHCAP773 FAILED REFUND
SP-6 Respond: macro SPLITPAY grounded payment_schedule_copy amounts
SP-7 Execute: retry failed refund partial finance escalate
SP-8 Close: tag splitpay_resolved schedule_cited installment_status Y/N
SLA: splitpay_schedule_explain answered with SCHEDULE-CITE payment_schedule_copy and AMOUNT-CITE in one interaction.
Essential SPLITPAY macros
Four macro multi-collection agents.
SPLITPAY-SCHEDULE-01
« Order #[order_ref map] : [payment_schedule_copy map.] Amounts : [installment_amounts_copy map.] Dates : [installment_dates_copy map.] SCHEDULE-CITE AMOUNT-CITE. »
SPLITPAY-CALENDAR-01
« Next collections: [installment_dates_copy map.] [split_trigger_copy map.] Remaining balance to pay: [installment_amounts_copy map.] »
SPLITPAY-DOUBLE-01
« No double debit: [double_charge_explain_copy map.] Deposit balance same order map. SCHEDULE-CITE. »
SPLITPAY-FAILED-01
« Failed installment: [failed_installment_policy_copy map.] [installment_dates_copy next map.] »
Edge cases: BNPL, AUTHCAP, mixed cart, and partial refund
Five cases outside the standard macro split payment.
Klarna Alma BNPL: NO-BNPL-CONFUSE BNPL distinct financier merchant debits
Refusal BNPL checkout: BNPL785-REROUTE #785 distinct scoring active installment
Simple auth capture: AUTHCAP #773 two distinct steps multiple
Double charge mixed subscription: mixcart distinct scheduled split
Refund of one installment: refund_installment_policy_copy finance partial map
Merchant split = SCHEDULE-CITE. BNPL financier = NO-BNPL-CONFUSE reroute.
Essential splitpay KPIs
Five SPLITPAY steering metrics.
splitpay_schedule_cite_rate: SCHEDULE-CITE / total splitpay schedule calendar
splitpay_bnpl_misroute_rate: BNPL tickets while merchant split / total splitpay
splitpay_failed_resolve_rate: resolved declined installment / total splitpay_failed
splitpay_double_escalation_rate: double chargeback received / total splitpay_double
splitpay_csat: CSAT multiple direct debits segment post-explanation map
Target: splitpay_schedule_cite_rate 100% and splitpay_bnpl_misroute_rate decreasing post SPLITPAY-MAP.
SPLITPAY anti-patterns
Five common mistakes regarding multiple debits support.
Confusing BNPL Klarna: NO-BNPL-CONFUSE bnpl_reroute_copy distinct merchant
Agent-invented schedule: SCHEDULE-CITE payment_schedule_copy map verify transactions
Invented amounts: AMOUNT-CITE installment_amounts_copy map only
Accusing double charge: double_charge_explain_copy deposit balance map
Order lookup ignored: ORDER-LOOKUP-FIRST transactions before responding
SPLITPAY with Qstomy
Qstomy on Shopify: detect splitpay intent, SPLITPAY-MAP RAG grounded, order transactions lookup, SCHEDULE-CITE guardrail, handoff #776 bot tier 1 or finance failed retry.
Pipeline: #776 bot calendar status tier 1 → #775 agents failed refund partial escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
SPLITPAY Checklist (8 steps)
SPLITPAY-MAP v1: schedule amounts dates trigger failed refund double bnpl
Policy SPLITPAY-SUP: 6 rules SCHEDULE AMOUNT ORDER-LOOKUP NO-BNPL BNPL785
8 typologies splitpay_*: tags helpdesk split_payment installment_merchant
4 macros SPLITPAY-*: SCHEDULE CALENDAR DOUBLE FAILED
Split payment programs sync: deposit balance ship trigger test
Agent training 30 min: NO-BNPL-CONFUSE before SCHEDULE-CITE
Transaction lookup runbook: finance order payments monthly test
KPI Dashboard: splitpay_* section 9 schedule_cite bnpl_misroute failed_resolve
FAQ
Difference BNPL Klarna?
BNPL = third-party financier credit contract. #775 = scheduled merchant debits for an order.
Two charges = double debit?
No. SPLITPAY-DOUBLE-01 double_charge_explain_copy deposit balance map.
Failed installment?
SPLITPAY-FAILED-01 failed_installment_policy_copy map retry.
Relation #776 bot?
#776 = tier 1 status calendar bot. #775 = agents failed refund partial escalate.
Going further
This week: index SPLITPAY-MAP payment_schedule by program, sync tags split_payment order, test macro SPLITPAY-SCHEDULE-01 deposit balance scenario.
Enzo
July 1, 2026
