E-commerce
July 1, 2026
"The bot says double debit when it is actually down payment balance." "The AI invents a direct debit date." "Chatbot routes to Klarna when it is a merchant payment." Three failures where a poorly calibrated split payment bot hallucinates schedules, confuses BNPL, or falsely accuses a double charge.
An e-commerce multi-installment payment AI chatbot does not replace SPLITPAY agents (#775). It reads SPLITPAY-MAP, quotes payment_schedule_copy installment_dates_copy, lookup transactions API, and handoff failed refund to humans.
This guide #776 covers intents bot_splitpay_*, flow SPLITPAYbot, and KPI splitpay_bot. Bot pair of the SPLITPAY playbook (#775). AI use case: schedules and installment status without hallucination.
Summary
Why automate the split payment schedule with a bot?
"Why two charges", "when is the next debit", "different amount" and "declined payment" arrive widget email confirmation account. A calibrated bot cites map calendar, grounded amounts and distinguishes BNPL without accusing double debit.
What the tier 1 split payment bot resolves
Schedule explain: payment_schedule_copy SCHEDULE-CITE-BOT map
Calendar cite: installment_dates_copy grounded map
Amount cite: installment_amounts_copy AMOUNT-CITE-BOT map
Double calm: double_charge_explain_copy map
Status lookup: transactions order API verify
Multiple debits generate tickets if calendar is opaque (Shopify, 2026 payments). Without a grounded bot, AI confuses BNPL or invents amounts.
SPLITPAYbot vs SPLITPAY #775, BNPL, AUTHCAPbot #774 and anti-hallucination #123
Six contents, six distinct direct debit flows.
Quick Matrix
#776 SPLITPAYbot: bot tier 1 calendar status without confusing BNPL
#775 SPLITPAY: agents failed refund partial escalate
BNPL Klarna: third-party financier distinct merchant debits
AUTHCAPbot #774: auth capture two-step distinct multiple installments
BNPL refused #786: bot refusal scoring distinct active calendar
Anti-hallucination #123: amounts dates = whitelist map only
Pipeline: #776 bot calendar status tier 1 → #775 agents failed refund partial escalate.
Which bot_splitpay_* intents should be configured?
Eight bot split payment intents mapped to splitpay_* typologies #775.
Eight bot_splitpay intents
bot_splitpay_schedule : payment_schedule_copy SCHEDULE-CITE-BOT map
bot_splitpay_calendar : installment_dates_copy cite map
bot_splitpay_amount : installment_amounts_copy AMOUNT-CITE-BOT map
bot_splitpay_double : double_charge_explain_copy deposit balance map
bot_splitpay_deposit : split_trigger_copy deposit balance map
bot_splitpay_status : transactions order API status map
bot_splitpay_bnpl_reroute : bnpl_reroute_copy NO-BNPL-CONFUSE-BOT map
bot_splitpay_handoff : failed refund → #775 SPLITPAY775-HANDOFF-BOT
Tier 1 auto : schedule calendar amount if SPLITPAY-MAP active + guardrails SCHEDULE-CITE-BOT AMOUNT-CITE-BOT.
bot_splitpay_handoff failed installment refund → agents #775 payload order_ref installment_status.
How do I use SPLITPAY-MAP #775?
The bot reads SPLITPAY-MAP #775: splitpay_program_id, payment_schedule_copy, installment_amounts_copy, installment_dates_copy, split_trigger_copy, failed_installment_policy_copy, refund_installment_policy_copy, double_charge_explain_copy, bnpl_reroute_copy.
Lookup grounded
SCHEDULE-CITE-BOT: payment_schedule_copy cite map verbatim
AMOUNT-CITE-BOT: installment_amounts_copy cite map only
DATE-CITE-BOT: installment_dates_copy cite map only
NO-BNPL-CONFUSE-BOT: bnpl_reroute_copy Klarna Alma distinct merchant map
TRANSACTION-API-GROUNDED-BOT: order payments transactions API only
BNPL786-REROUTE-BOT: decline scoring → #786 distinct active schedule
AUTHCAP774-REROUTE-BOT: auth capture → #774 distinct multiple installments
SPLITPAY775-HANDOFF-BOT: failed refund → #775 SP-7 agents execute
Alignment anti-hallucination (#123): schedule amounts = SPLITPAY-MAP whitelist + transaction API only. Bot does not execute refund.
SPLITPAYBOT-SUP Policy in Six Rules
Six rules for a responsible split payment bot.
SPLITPAY-MAP-GROUNDED-BOT: split response from map only
SCHEDULE-CITE-BOT: payment_schedule_copy cited without omission
AMOUNT-CITE-BOT: installment_amounts_copy cited from map only
DATE-CITE-BOT: installment_dates_copy cited from map only
NO-BNPL-CONFUSE-BOT: bnpl_reroute_copy Klarna Alma distinct merchant map
TRANSACTION-API-GROUNDED-BOT: payments transactions API only
Flow SPLITPAYbot SPB-1 to SPB-8
Eight-step flow bot multiple direct debits.
SPB-1 Classify : bot_splitpay_* intent detect widget account email keyword two direct debits next debit
SPB-2 Collect : order_ref amount date bank_statement
SPB-3 SPLITPAY-MAP : schedule amounts dates trigger failed refund double bnpl
SPB-4 Lookup : order payments transactions status API verify
SPB-5 Guardrail : SCHEDULE AMOUNT DATE NO-BNPL BNPL786 AUTHCAP774 TRANSACTION HANDOFF
SPB-6 Respond : TPL-SPLITPAYbot grounded payment_schedule_copy amounts dates
SPB-7 Handoff or close : failed refund #775 payload order_ref status
SPB-8 Log : intent splitpay_program_id tag splitpay_bot schedule_cited handoff Y/N
Example TPL-SPLITPAYbot-SCHEDULE
“Order [order_ref map] : [payment_schedule_copy map.] Amounts [installment_amounts_copy map.] Dates [installment_dates_copy map.] SCHEDULE-CITE-BOT AMOUNT-CITE-BOT.”
TPL-SPLITPAYbot templates and touchpoints
Four essential templates.
TPL-SPLITPAYbot-SCHEDULE
Order [order_ref map]: [payment_schedule_copy map.] Amounts [installment_amounts_copy map.] SCHEDULE-CITE-BOT AMOUNT-CITE-BOT.
TPL-SPLITPAYbot-CALENDAR
Next charges: [installment_dates_copy map.] [split_trigger_copy map.] DATE-CITE-BOT.
TPL-SPLITPAYbot-DOUBLE
No double debit: [double_charge_explain_copy map.] Deposit balance same order map.
TPL-SPLITPAYbot-BNPL
Merchant payment: [bnpl_reroute_copy map.] Distinct Klarna Alma payment schedule. NO-BNPL-CONFUSE-BOT.
Touchpoints
Email confirmation split payment: bot_splitpay_schedule proactive embed
Keyword two charges: bot_splitpay_schedule bot_splitpay_double trigger
Keyword next debit: bot_splitpay_calendar trigger
Keyword Klarna Alma: bot_splitpay_bnpl_reroute NO-BNPL trigger
Edge cases and reroutes
Five cases outside tier 1 bot split payment standard.
Klarna Alma BNPL: NO-BNPL-CONFUSE-BOT BNPL financier distinct merchant
Refusal BNPL checkout: BNPL786-REROUTE-BOT #785 distinct active installment
Auth capture simple: AUTHCAP774-REROUTE-BOT #773 distinct multiples
Failed refund execute: SPLITPAY775-HANDOFF-BOT agents #775 finance only bot does not refund
Mixed cart subscription: mixcart distinct scheduled split
Bot calendar status tier 1. Failed refund partial → agents #775.
Essential splitpay_bot KPIs
Five SPLITPAYbot steering metrics.
splitpay_bot_schedule_deflect: split payment resolved without agent
splitpay_bot_schedule_cite_rate: SCHEDULE-CITE-BOT / bot_splitpay schedule calendar
splitpay_bot_amount_hallucination_violations: invented amount bot audit target 0
splitpay_bot_bnpl_misroute_violations: BNPL route whereas merchant split target 0
splitpay_bot_handoff_rate: failed refund / total splitpay bot
Target: splitpay_bot_schedule_deflect greater than 55% and splitpay_bot_bnpl_misroute_violations 0.
Anti-patterns SPLITPAYbot
Five common errors bot multiple collections.
Invented schedule bot: SCHEDULE-CITE-BOT payment_schedule_copy TRANSACTION-API verify
Invented amounts: AMOUNT-CITE-BOT installment_amounts_copy map only
Confusing BNPL Klarna: NO-BNPL-CONFUSE-BOT bnpl_reroute_copy map
Accusing double charge: TPL-SPLITPAYbot-DOUBLE double_charge_explain_copy map
Executed refund bot: SPLITPAY775-HANDOFF-BOT agents #775 finance only
SPLITPAYbot with Qstomy
Qstomy on Shopify: detect bot_splitpay intent, SPLITPAY-MAP RAG grounded, order transactions API, SCHEDULE-CITE guardrail, handoff #775 failed refund tier 2.
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
SPLITPAYbot Checklist (8 steps)
Sync SPLITPAY-MAP #775: RAG bot widget email confirmation account
Policy SPLITPAYBOT-SUP: 6 rules SCHEDULE AMOUNT DATE NO-BNPL TRANSACTION
8 intents bot_splitpay_*: flow SPB-1 to SPB-8
4 templates TPL-SPLITPAYbot-*: SCHEDULE CALENDAR DOUBLE BNPL
Transaction API sync: order payments split program test
Email split payment embed chat: bot_splitpay_schedule proactive
Red team 10 prompts: invented calendar BNPL confused double charge claimed
Dashboard KPI: splitpay_bot_* section 9 schedule_deflect bnpl_violations handoff
FAQ
Difference #775?
#775 = agents failed refund partial escalate. #776 = bot tier 1 calendar status without executed refund.
Bot quotes real dates?
SPB-4 TRANSACTION-API-GROUNDED-BOT installment_dates_copy verify.
Two debits double charge?
No. TPL-SPLITPAYbot-DOUBLE double_charge_explain_copy down payment balance map.
Difference BNPL bot?
BNPL = financier Klarna Alma. #776 = scheduled merchant debits one order.
Going further
This week: index SPLITPAY-MAP RAG email split payment embed, red team amount_hallucination_violations audit, sync transaction lookup down payment balance test.
Enzo
July 1, 2026
