E-commerce
July 1, 2026
"The bot doesn't know if I can combine a gift card and credit card." "The AI invents an execution order that is missing from the checkout." "The chatbot doesn't calculate the remaining balance after my store credit." Three failures where a badly calibrated multi-payment cart bot blocks the split tender.
An e-commerce multi-payment cart AI chatbot does not replace MULPAY agents (#987). It reads MULPAY-MAP, quotes split_policy_copy apply_order_copy, remaining_balance_formula and hands off the order split to humans.
This guide #988 covers bot_mulpay_* intents, flow MULPAYBOT MPB-1 to MPB-8 and mulpay_bot KPIs. Bot counterpart of the MULPAY playbook (#987). Usecase: split tender checkout tier 1 widget.
Summary
Why botify the multi-payment shopping cart at checkout?
"Can I pay with my gift card and my credit card?", "how much is left to pay?" and "what amount on each method?" arrive at checkout and post-order. A calibrated bot looks up MULPAY-MAP, cites allowed_methods apply_order without improvising combinations out of register.
What the tier 1 bot resolves
Combinable options: allowed_methods_ref split_policy_copy map
Application order: apply_order_copy map grounded
Remaining balance: remaining_balance_formula_copy calc
Policy limits: min_card_remainder_ref limit cite
Promo stacking: stacking_rules_copy map
Post-purchase lite status: order split handoff if complex
The bot intercepts bot_mulpay_split_explain before an invented combo or reroutes to SPLITPAYbot #776 if split payments are mentioned.
Omnichannel beauty DTC example
Beauty brand gift card + store credit, 7k mulpay_ tickets/month. Bot syncs MULPAY-MAP J-0. mulpay_bot_deflect +34%, mulpay_bot_combo_invent_violation 0 in 6 weeks.
MULPAYBOT #988 vs MULPAY #987, SPLITPAYbot #776, gift card, BNPL
Seven multi-payment bot contents, seven distinct roles.
Quick Matrix
#988 MULPAYBOT: tier 1 bot split tender options limits widget status
MULPAY #987: agents verify transactions ops limit execute
SPLITPAYbot #776: staggered distinct direct debits combined checkout means
STORECREDIT: store credit distinct split tender policy
Pipeline: bot split apply remain limit cite → #987 order split ops handoff execute.
Which bot_mulpay_* intents should be configured?
Eight multi-payment cart intents mapped to mulpay_* typologies #987.
Eight bot_mulpay intents
bot_mulpay_combo_detect: detect mentioned methods gift card credit wallet card
bot_mulpay_split_explain: split_policy_copy allowed_methods map
bot_mulpay_apply_order: apply_order_copy application order map
bot_mulpay_remaining_calc: remaining_balance_formula_copy calc
bot_mulpay_limit_cite: min_card_remainder limit policy map
bot_mulpay_stacking_cite: stacking_rules_copy promo combination map
bot_mulpay_checkout_guide: checkout_help_url combined steps
bot_mulpay_handoff: order split limit ops → #987
Tier 1 auto: combo_detect, split_explain, apply_order, remaining_calc, limit_cite if checkout + MULPAY-MAP + guardrails.
bot_mulpay_handoff, mulpay_order_split_status, mulpay_ops_flag → agents #987 payload mulpay_id order_ref.
How should MULPAY-MAP #987 be consumed?
The bot reads MULPAY-MAP #987: mulpay_id, allowed_methods_ref, split_policy_copy, apply_order_copy, min_card_remainder_ref, stacking_rules_copy, remaining_balance_formula_copy, checkout_help_url, agent_handoff_url.
Lookup grounded split tender
Combo detect: keywords gift card voucher CC wallet → MULPAY-MAP row
Balance API: gift card store credit wallet live balance verify
SPLIT-POLICY-GROUNDED-BOT: split_policy_copy allowed_methods map only
APPLY-ORDER-GROUNDED-BOT: apply_order_copy map only
REMAIN-GROUNDED-BOT: remaining_balance_formula_copy calc map only
NO-COMBO-INVENT-BOT: never promise a combination not in the registry
STACKING-GROUNDED-BOT: stacking_rules_copy map only
Checkout widget: entry "Pay with multiple methods" + detected cart methods.
MULPAYBOT-SUP Policy in six rules
Six rules for a secure multi-payment cart bot.
MULPAY-REGISTRY-GATE : lookup MULPAY-MAP before split response
SPLIT-POLICY-GROUNDED-BOT : split_policy_copy quoted if combo ask
APPLY-ORDER-GROUNDED-BOT : apply_order_copy quoted if order ask
REMAIN-GROUNDED-BOT : remaining_balance_formula calc map only
NO-COMBO-INVENT-BOT : no promise combination outside of allowed_methods
SPLITPAY-REROUTE-BOT : split payments → SPLITPAYbot #776, BNPL → BNPL
Flow MULPAYBOT MPB-1 to MPB-8
Eight-step flow: ingest detect lookup verify answer guide reroute handoff log.
MPB-1 Ingest: multi-payment message gift card store credit credit card balance
MPB-2 Combo detect: bot_mulpay_combo_detect cart methods
MPB-3 Registry lookup: MULPAY-REGISTRY-GATE MULPAY-MAP
MPB-4 Balance verify: gift card store credit wallet live balance
MPB-5 Tier 1 answer: split_explain apply_order remaining_calc limit_cite
MPB-6 Reroute: SPLITPAYbot #776 GIFTCARD solo LCARDbot BNPL
MPB-7 Handoff: order split limit ops → agent #987
MPB-8 Log: deflect split_cite remain_cite KPI
TPL-MULPAY-SPLIT Example
“Combinable methods: {{allowed_methods_ref map}}. {{split_policy_copy map}}. Order: {{apply_order_copy map}}. Remaining balance: {{remaining_balance_formula calc}}.”
TPL-MULPAY templates and touchpoints
Five short templates split tender embed widget checkout cart.
TPL-MULPAY-SPLIT
[allowed_methods_ref map.] [split_policy_copy map.] SPLIT-GROUNDED.
TPL-MULPAY-ORDER
[apply_order_copy map.] Checkout application order. APPLY-GROUNDED.
TPL-MULPAY-REMAIN
[remaining_balance_formula_copy calc.] Cart minus credits. REMAIN-GROUNDED.
TPL-MULPAY-LIMIT
[min_card_remainder_ref map.] [limit policy map.] LIMIT-GROUNDED.
TPL-MULPAY-HANDOFF
[agent_handoff_url.] Request [order_split / limit / ops] transmitted. Policy [mulpay_id]. Delay [handoff_sla].
Touchpoints
"Pay with multiple methods": combo_detect + split_explain
Credit chip checkout: remaining_calc + REMAIN template
"Gift card + Bank card": apply_order + ORDER template
"Combination declined": limit_cite + LIMIT template or handoff
Edge cases: split payment, gift card only, cart calculation, declined payment
Five cases outside tier 1 standard multi-payment bot.
Merchant installment debits: reroute SPLITPAYbot #776
Gift card only no combo: reroute gift card SAV
Third-party financier BNPL: reroute BNPL
Incorrect cart total before credits: reroute calcul panier bot
Complex order split: handoff #987 STATUS no auto dispute bot
Bot does not allow combo outside MULPAY-MAP: handoff #987 registry brief if new frequent payment stack.
Essential mulpay_bot KPIs
Five MULPAYBOT steering metrics and correlation #987.
mulpay_bot_deflect: clarified split tender without mulpay_ ticket
mulpay_bot_split_cite_rate: % sessions split_policy_copy provided tier 1
mulpay_bot_remain_cite_rate: % sessions remaining_calc provided
mulpay_bot_handoff_rate: % order split limit routed #987
mulpay_bot_combo_invent_violation: invented combinations off-map target 0
Target: combo_invent_violation at zero and split_cite_rate above 85% post MULPAY-MAP sync Day-0.
MULPAYBOT anti-patterns
Five common multi-payment basket bot mistakes.
Inventing combinations of methods: SPLIT-GROUNDED allowed_methods only
Improvised application order: APPLY-GROUNDED apply_order_copy only
Guessing remaining balance: REMAIN-GROUNDED formula map calc only
Confusing SPLITPAYbot #776: #988 combined checkout not staggered over time
Auto order allocation: handoff #987 STATUS not bot dispute
MULPAYBOT with Qstomy
Qstomy on Shopify: detect bot_mulpay intent, MULPAY-MAP RAG split index, balance verify API, templates SPLIT ORDER REMAIN LIMIT, handoff #987 ops payload mulpay_id.
Pipeline: #988 bot split apply remain limit → #987 order split ops execute.
Scenario: DTC beauty gift card + store credit. Registry D-0. mulpay_bot_deflect +34%, combo_invent_violation 0.
Explore AI support and request a demo.
Checklist, FAQ and going further
MULPAYBOT Checklist (8 steps)
Sync MULPAY-MAP #987: RAG bot split apply remain index
Policy MULPAYBOT-SUP: 6 rules REGISTRY-GATE SPLIT-GROUNDED NO-COMBO-INVENT
8 intents bot_mulpay_*: flow MPB-1 to MPB-8
5 templates TPL-MULPAY-*: SPLIT ORDER REMAIN LIMIT HANDOFF
Multi-method checkout widget: combo_detect cart entry
Balance API verify: gift card store credit wallet test
Red team 10 combos: invent split order remain out-of-map test
Dashboard KPI: mulpay_bot_* section 9 + delta mulpay_
FAQ
Difference #987?
#987 = agents verify transactions ops limit execute. #988 = bot tier 1 options widget.
Bot invents a combination?
No, out of MULPAY-MAP. NO-COMBO-INVENT-BOT. Handoff if limit.
Difference SPLITPAYbot #776?
#776 = scheduled time debits. #988 = combined checkout methods.
Difference with gift card alone?
Gift card = balance usage. #988 = multi-method combination.
Incorrect remaining balance?
Bot cites formula map + balance API. Persistent → handoff #987.
Go further
This week: sync MULPAY-MAP #987, multi-method checkout widget, templates SPLIT ORDER REMAIN, measure mulpay_bot_deflect.
Enzo
July 1, 2026
