E-commerce
July 1, 2026
"The bot denies my debit even though bank statement shows capture." "The AI promises a 24h refund without looking up the PSP." "Chatbot closes ticket without escalating to finance P1." Three failures where a miscalibrated, orphan payment bot denies debit, promises refund, or blocks critical incident escalation.
An AI payment chatbot captured without an e-commerce order does not replace PCAPNO agents (#767). It reads PCAPNO-MAP, cites incident_response_policy_copy, collects proof_collect_copy, and hands off finance P1 to humans without making refund promises.
This guide #768 covers bot_pcapno_* intents, PCAPNObot flow, and pcapno_bot KPIs. Bot paired with the PCAPNO playbook (#767). AI use case: collect evidence and escalate P1 incident quickly.
Summary
Why automate orphan payment triage with a bot?
"Debited without order", "checkout crashed after payment", and "chargeback threat" arrive widget checkout email panic. A calibrated bot recognizes a P1 incident, collects map evidence, and escalates to finance without denying the debit or promising a refund.
What the bot resolves tier 1 orphan payment
Incident ack: incident_response_policy_copy INCIDENT-CITE-BOT map
Proof collect: proof_collect_copy email amount date screenshot map
SLA cite: sla_response_copy grounded map
No refund explain: refund_policy_copy NO-REFUND-PROMISE-BOT map
P1 handoff: finance ops #767 payload proof complete
Orphan payments generate chargebacks if denied or misrouted (Shopify, payments 2026). Without a grounded bot, the AI promises a refund or confuses Pending #763.
PCAPNObot vs PCAPNO #767, PNDPAY #763, payment declined and anti-hallucination #123
Six contents, six distinct payment incident flows.
Quick Matrix
#768 PCAPNObot: tier 1 bot collect proof escalate P1 without promised refund
#767 PCAPNO: finance agents PSP lookup recreate refund
PNDPAY #763: Pending order exists distinct debit without order
PNDPAYbot #764: Pending status explain distinct orphan
Declined payment: blocked card distinct confirmed debit
Anti-hallucination #123: refund delays = map whitelist only
Pipeline: #768 bot collect proof tier 1 → #767 finance agents PSP lookup recreate refund.
Which bot_pcapno_* intents should be configured?
Eight captured payment bot intents without order mapped to pcapno_* typologies #767.
Eight bot_pcapno intents
bot_pcapno_ack: incident_response_policy_copy INCIDENT-CITE-BOT map
bot_pcapno_collect: proof_collect_copy guided form map
bot_pcapno_sla: sla_response_copy cite map
bot_pcapno_no_refund: refund_policy_copy NO-REFUND-PROMISE-BOT map
bot_pcapno_chargeback_calm: chargeback_prevent_copy map
bot_pcapno_checkout_crash: incident_response_policy_copy crash post-pay map
bot_pcapno_order_lookup: order search email API verify PNDPAY reroute
bot_pcapno_handoff: finance P1 → #767 PCAPNO767-HANDOFF-BOT
Tier 1 auto: ack collect sla if PCAPNO-MAP active + guardrails NO-REFUND-PROMISE-BOT P1-HANDOFF-BOT.
bot_pcapno_handoff proof complete → agents #767 payload email amount date payment_method screenshot.
How should PCAPNO-MAP #767 be consumed?
The bot reads PCAPNO-MAP #767: pcapno_program_id, incident_response_policy_copy, proof_collect_copy, psp_lookup_steps_copy, order_recreate_policy_copy, refund_policy_copy, sla_response_copy, chargeback_prevent_copy, pndpay_reroute_copy.
Lookup grounded
INCIDENT-CITE-BOT: incident_response_policy_copy cite map verbatim
PROOF-COLLECT-BOT: proof_collect_copy guided fields map only
NO-REFUND-PROMISE-BOT: no refund promised bot refund_policy_copy map
SLA-CITE-BOT: sla_response_copy cite map only
ORDER-API-GROUNDED-BOT: order search email API only no invented order
PNDPAY763-REROUTE-BOT: order Pending found → #764 distinct orphan PNDPAYbot
DECLINED-REROUTE-BOT: card declined → distinct declined payment capture
PCAPNO767-HANDOFF-BOT: finance P1 → #767 PC-4 agents PSP lookup
Anti-hallucination alignment (#123): status refund delays = PCAPNO-MAP whitelist + order API only. Bot does not do PSP lookup.
PCAPNOBOT-SUP six-rule policy
Six rules bot orphan payment responsible.
PCAPNO-MAP-GROUNDED-BOT: incident response from map only
INCIDENT-CITE-BOT: incident_response_policy_copy quotes without omission
NO-REFUND-PROMISE-BOT: no refund promised bot refund_policy_copy map
PROOF-COLLECT-BOT: proof_collect_copy required fields before handoff
P1-HANDOFF-BOT: finance ops escalate bot_pcapno_handoff immediate map
SLA-CITE-BOT: sla_response_copy quotes map only
PCAPNObot Flow PCB-1 to PCB-8
translated_markup
TPL-PCAPNObot and touchpoints templates
Four essential templates.
TPL-PCAPNObot-ACK
Debited without order: [incident_response_policy_copy map.] Delay [sla_response_copy map.] INCIDENT-CITE-BOT.
TPL-PCAPNObot-COLLECT
For finance research: [proof_collect_copy map.] Masked statement amount date email accepted. PROOF-COLLECT-BOT.
TPL-PCAPNObot-NOREFUND
Refund: [refund_policy_copy map.] PSP search in progress before decision. NO-REFUND-PROMISE-BOT.
TPL-PCAPNObot-CHARGEBACK
We process with priority: [chargeback_prevent_copy map.] [sla_response_copy map.] P1-HANDOFF-BOT finance.
Touchpoints
Checkout error post-payment: bot_pcapno_checkout_crash proactive embed
Keyword debited without order: bot_pcapno_ack bot_pcapno_collect trigger
Keyword urgent refund: bot_pcapno_no_refund trigger
Keyword chargeback dispute: bot_pcapno_chargeback_calm P1 escalate
Edge cases and reroutes
Five cases outside tier 1 bot standard orphan payment.
Order Pending found API : PNDPAY763-REROUTE-BOT #764 PNDPAYbot distinct orphan
Card declined no charge : DECLINED-REROUTE-BOT declined payment distinct capture
Fingerprint auth hold : #766 THRDSbot distinct orphan capture
PSP lookup recreate refund : PCAPNO767-HANDOFF-BOT agents #767 finance only bot does not lookup
Global checkout incident : technical incident communication distinct isolated case
Bot collect proof tier 1. PSP lookup recreate refund → agents #767 only.
Essential pcapno_bot KPIs
Five PCAPNObot management metrics.
pcapno_bot_proof_complete_rate: complete handoff proof / total bot_pcapno
pcapno_bot_incident_cite_rate: INCIDENT-CITE-BOT / bot_pcapno ack
pcapno_bot_refund_promise_violations: promised refund bot target audit 0
pcapno_bot_p1_handoff_rate: finance P1 escalate / total pcapno bot
pcapno_bot_chargeback_after_bot: chargeback post bot without handoff target 0
Target: pcapno_bot_refund_promise_violations 0 and pcapno_bot_proof_complete_rate greater than 80%.
PCAPNObot anti-patterns
Five common errors bot payment captured without order.
Denying customer debit: INCIDENT-CITE-BOT incident_response_policy_copy ack map
Refund promised bot: NO-REFUND-PROMISE-BOT refund_policy_copy map
Handoff without proof: PROOF-COLLECT-BOT mandatory fields before PCAPNO767-HANDOFF
PSP lookup executed bot: PCAPNO767-HANDOFF-BOT agents #767 finance only
Confusing Pending #763: PNDPAY763-REROUTE-BOT order exists distinct absent
PCAPNObot with Qstomy
Qstomy on Shopify: detect bot_pcapno intent P1, PCAPNO-MAP RAG grounded, proof collect form, INCIDENT-CITE guardrail, handoff #767 finance tier 2.
Pipeline: #768 bot collecter proof escalate tier 1 → #767 finance agents PSP lookup recreate refund.
Explore AI support and request a demo.
Checklist, FAQ and going further
PCAPNObot Checklist (8 steps)
Sync PCAPNO-MAP #767: RAG bot widget checkout panic email
Policy PCAPNOBOT-SUP: 6 rules INCIDENT NO-REFUND PROOF P1-HANDOFF SLA
8 intents bot_pcapno_*: flow PCB-1 to PCB-8
4 templates TPL-PCAPNObot-*: ACK COLLECT NOREFUND CHARGEBACK
Proof collect form sync: email amount date payment_method screenshot test
Checkout error embed chat: bot_pcapno_checkout_crash proactive
Red team 10 prompts: deny charge refund promised handoff without proof
KPI Dashboard: pcapno_bot_* section 9 refund_violations proof_complete handoff
FAQ
Difference with #767?
#767 = finance agents PSP lookup recreate refund. #768 = tier 1 bot collect proof escalate P1 without promised refund.
Does the bot promise a refund?
No. TPL-PCAPNObot-NOREFUND NO-REFUND-PROMISE-BOT refund_policy_copy map.
Does the bot perform a PSP lookup?
No. PCAPNO767-HANDOFF-BOT #767 agents PC-4 PSP lookup only.
Difference with PNDPAYbot #764?
#764 = explain status Pending order exists. #768 = charge without order incident P1 collect proof.
Going further
Chargeback prevention
This week: index PCAPNO-MAP RAG checkout error embed, red team refund_promise_violations audit, sync proof collect form handoff #767 test.
Enzo
July 1, 2026
