E-commerce
July 1, 2026
"The bot denies my double charge without even asking for my statement." "The AI promises immediate refund before verification." "Chatbot closes ticket without escalating to finance." Three failures where a miscalibrated double charge bot panics the customer, promises a refund, or ignores proof.
An e-commerce double charge AI chatbot does not replace DBLCHRG agents (#789). It reads DBLCHRG-MAP, reassures with sla_response_copy, collects proof_collect_copy, and hands off to finance humans without confirming a duplicate or promising a refund.
This guide #790 covers intents bot_dblchrg_*, flow DBLCHRGbot, and KPI dblchrg_bot. Bot pair of the DBLCHRG playbook (#789). Priority AI use case: collect evidence and reassure tier 1 sensitive incident.
Summary
Why automate double-throughput triage by bot?
"Charged twice", "two identical lines on statement" and "chargeback threat" arrive in the email account widget in a panic. A calibrated bot recognizes the concern, collects proof maps, explains the perceived split auth, and escalates to finance without denying or promising a refund.
What the bot resolves in tier 1 double debit
Calm ack: sla_response_copy CALM-CITE-BOT map
Proof collect: proof_collect_copy statement amount date map
Perceived explain: perceived_explain_copy split auth map
No refund promise: refund_duplicate_policy_copy NO-REFUND-PROMISE-BOT map
Finance handoff: #789 payload proof complete order_ref
Double debits generate chargebacks if denied or misrouted (Chargeback Gurus, 2026 prevention). Without a grounded bot, the AI promises a refund or confuses it with split payment #775.
DBLCHRGbot vs DBLCHRG #789, SPLITPAYbot #776, PCAPNObot #768 and anti-hallucination #123
Six contents, six distinct multiple-debit pathways.
Quick matrix
#790 DBLCHRGbot: tier 1 bot collect evidence reassure without refund promised
#789 DBLCHRG: finance agents lookup refund escalate
SPLITPAYbot #776: deposit balance separate schedule actual duplicate
AUTHCAPbot #774: hold auth separate two identical debits
PCAPNObot #768: debit without order separate duplicate of existing order
Anti-hallucination #123: refund timeframes = whitelist map only
Pipeline: #790 bot collect evidence reassure tier 1 → #789 agents lookup refund escalate.
Which bot_dblchrg_* intents should be configured?
Eight double-charge bot intents mapped to dblchrg_* typologies #789.
Eight bot_dblchrg intents
bot_dblchrg_ack : sla_response_copy CALM-CITE-BOT map
bot_dblchrg_collect : proof_collect_copy guided form map
bot_dblchrg_calm : perceived_explain_copy reassure map
bot_dblchrg_perceived : split auth perceived_explain_copy map
bot_dblchrg_no_refund : refund_duplicate_policy_copy NO-REFUND-PROMISE-BOT map
bot_dblchrg_chargeback_calm : sla_response_copy priority map
bot_dblchrg_order_lookup : order search email API verify split reroute
bot_dblchrg_handoff : finance escalate → DBLCHRG789-HANDOFF-BOT
Tier 1 auto : ack collect calm if DBLCHRG-MAP active + guardrails NO-REFUND-PROMISE-BOT NO-DUPLICATE-ASSUME-BOT.
bot_dblchrg_handoff proof complete → agents #789 payload order_ref amount date screenshot.
How to consume DBLCHRG-MAP #789?
The bot reads DBLCHRG-MAP #789: dblchrg_program_id, true_duplicate_policy_copy, proof_collect_copy, transaction_lookup_steps_copy, refund_duplicate_policy_copy, perceived_explain_copy, auth_hold_explain_copy, sla_response_copy, splitpay_reroute_copy, authcap_reroute_copy, pcapno_reroute_copy.
Lookup grounded
CALM-CITE-BOT: sla_response_copy cite map verbatim reassure
PROOF-COLLECT-BOT: proof_collect_copy guided fields map only
NO-REFUND-PROMISE-BOT: no refund promised bot refund_duplicate_policy_copy map
NO-DUPLICATE-ASSUME-BOT: bot does not confirm duplicate without agents lookup map
ORDER-API-GROUNDED-BOT: order transactions search email API only
SPLITPAY776-REROUTE-BOT: deposit balance → #776 distinct real duplicate
AUTHCAP774-REROUTE-BOT: hold → #774 auth hold distinct capture
DBLCHRG789-HANDOFF-BOT: finance → #789 agents DC-4 lookup refund
Alignment anti-hallucination (#123): refund delay duplicate status = DBLCHRG-MAP whitelist + order API only. Bot does not perform PSP lookup.
DBLCHRGBOT-SUP Policy in six rules
Six bot rules double charge responsible sensitive incident.
DBLCHRG-MAP-GROUNDED-BOT: double charge response from map only
CALM-CITE-BOT: sla_response_copy cite reassure without omission
PROOF-COLLECT-BOT: proof_collect_copy mandatory fields before handoff
NO-REFUND-PROMISE-BOT: no refund promised bot refund_duplicate_policy_copy map
NO-DUPLICATE-ASSUME-BOT: bot does not confirm duplicate without agents TXN-LOOKUP map
FINANCE-HANDOFF-BOT: finance escalate bot_dblchrg_handoff immediate map
Flow DBLCHRGbot DCB-1 to DCB-8
Eight-step flow double charge sensitive incident bot.
DCB-1 Classify: bot_dblchrg_* intent detect widget account email keyword charged twice double charge
DCB-2 Collect: order_ref email amount date bank_proof screenshot proof_collect_copy
DCB-3 DBLCHRG-MAP: duplicate proof refund perceived auth split authcap pcapno sla
DCB-4 Lookup: order transactions search email API verify split auth reroute
DCB-5 Guardrail: CALM PROOF NO-REFUND NO-ASSUME SPLIT776 AUTHCAP774 PCAPNO FINANCE-HANDOFF
DCB-6 Respond: TPL-DBLCHRGbot grounded calm collect perceived max 2 phrases
DCB-7 Handoff or close: finance #789 payload proof complete or close perceived explained
DCB-8 Log: intent dblchrg_program_id tag dblchrg_bot calm_cited handoff Y/N proof_complete
Example TPL-DBLCHRGbot-ACK
"We understand the concern regarding the double charge. [sla_response_copy map.] To verify: [proof_collect_copy map.] Finance search in progress. NO-REFUND-PROMISE-BOT CALM-CITE-BOT."
TPL-DBLCHRGbot and touchpoints templates
Four essential double charge incident templates.
TPL-DBLCHRGbot-ACK
Double charge reported: [sla_response_copy map.] We are prioritizing this. CALM-CITE-BOT.
TPL-DBLCHRGbot-COLLECT
For finance lookup: [proof_collect_copy map.] Masked statement amount date descriptor email. PROOF-COLLECT-BOT.
TPL-DBLCHRGbot-PERCEIVED
Not a double charge: [perceived_explain_copy map.] [auth_hold_explain_copy or splitpay_reroute_copy map.] NO-DUPLICATE-ASSUME-BOT.
TPL-DBLCHRGbot-NOREFUND
Refund: [refund_duplicate_policy_copy map.] Pending transactions verification before decision. NO-REFUND-PROMISE-BOT.
Touchpoints
Keyword charged twice: bot_dblchrg_ack bot_dblchrg_collect trigger instant
Keyword double charge statement: bot_dblchrg_collect proactive embed
Keyword urgent refund: bot_dblchrg_no_refund trigger
Keyword chargeback dispute: bot_dblchrg_chargeback_calm FINANCE-HANDOFF-BOT
No post-purchase embed for general dispute: payment incident or BNPL depending on intent.
Edge cases and reroutes
Five cases outside tier 1 bot double standard charge.
Deposit balance split API: SPLITPAY776-REROUTE-BOT #776 distinct calendar real duplicate
Hold authorization imprint: AUTHCAP774-REROUTE-BOT #774 distinct release capture
Orphan debit without order: PCAPNO768-REROUTE-BOT #768 distinct duplicate order
PSP lookup refund execute: DBLCHRG789-HANDOFF-BOT agents #789 finance only bot does not lookup
Two orders created: duplicate order distinct duplicate payment
Bot to collect evidence to reassure tier 1. Lookup refund execute → agents #789 only.
Essential dblchrg_bot KPIs
Five DBLCHRGbot steering metrics.
dblchrg_bot_proof_complete_rate: proof_collect_copy complete before handoff / total bot
dblchrg_bot_calm_cite_rate: CALM-CITE-BOT / bot_dblchrg ack chargeback
dblchrg_bot_refund_promise_violations: bot target audit refund promise 0
dblchrg_bot_perceived_deflect: split auth explained without agent / total perceived
dblchrg_bot_handoff_rate: finance escalate / total dblchrg bot
Target: dblchrg_bot_refund_promise_violations 0 and dblchrg_bot_proof_complete_rate greater than 80%.
DBLCHRGbot anti-patterns
Five common errors double debit bot sensitive incident.
Denying double debit bot : CALM-CITE-BOT sla_response_copy ack map immediate
Promising refund bot : NO-REFUND-PROMISE-BOT refund_duplicate_policy_copy map only
Confirming duplicate without lookup : NO-DUPLICATE-ASSUME-BOT agents #789 TXN-LOOKUP only
Route split payment : SPLITPAY776-REROUTE-BOT perceived_explain_copy map
Uncollected proof handoff : PROOF-COLLECT-BOT proof_collect_copy before FINANCE-HANDOFF
DBLCHRGbot with Qstomy
Qstomy on Shopify: detect bot_dblchrg intent widget account email, DBLCHRG-MAP RAG grounded, CALM-CITE guardrail, PROOF-COLLECT form, handoff #789 finance tier 2.
Pipeline: #790 bot collect proof reassure tier 1 → #789 agents lookup refund escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
DBLCHRGbot Checklist (8 steps)
Sync DBLCHRG-MAP #789: RAG bot email account widget double charge
Policy DBLCHRGBOT-SUP: 6 rules CALM PROOF NO-REFUND NO-ASSUME FINANCE-HANDOFF
8 intents bot_dblchrg_*: flow DCB-1 to DCB-8
4 templates TPL-DBLCHRGbot-*: ACK COLLECT PERCEIVED NOREFUND
Proof collect form sync: amount date descriptor screenshot test
Red team 10 prompts: deny charge promise refund confirm duplicate no proof route split
Chargeback keyword escalate: bot_dblchrg_chargeback_calm FINANCE-HANDOFF instant
Dashboard KPI: dblchrg_bot_* section 9 proof_complete refund_violations handoff
FAQ
Difference #789?
#789 = agents lookup refund escalate. #790 = bot tier 1 collect proof reassure without confirming duplicate.
Does the bot confirm double charge?
No. NO-DUPLICATE-ASSUME-BOT agents #789 transaction_lookup_steps_copy map.
Does the bot promise a 24-hour refund?
No. TPL-DBLCHRGbot-NOREFUND NO-REFUND-PROMISE-BOT refund_duplicate_policy_copy map.
Difference with SPLITPAYbot #776?
#776 = deposit balance calendar. #790 = two identical charges or double checkout attempt.
Going further
This week: deploy DBLCHRG-MAP RAG widget double charge embed, red team refund_promise_violations audit, sync proof collect form scenario two identical statement lines handoff test #789.
Enzo
July 1, 2026
