E-commerce
July 1, 2026
"Pending line on my statement but not debited." "My bank reserved €89, where did my money go?" "Abandoned cart, authorization hold still visible." Three tickets where a poorly explained temporary bank hold generates panic and chargebacks.
The ecommerce visible non-debited bank hold support covers statement holds, impact on available balance, and bank release times. Distinct from merchant auth capture (#773): here, customer education on what the bank displays before the final debit.
This guide #791 covers policy TMPHOLD-SUP, flow TH-1 to TH-8, and matrix TMPHOLD-MAP. Future customer service pair bot TMPHOLD (#792).
Summary
Why do temporary bank authorizations generate tickets?
The customer sees a "pending" or "reservation" line on their bank statement. The agent denies the authorization hold, promises an immediate refund, or directs a double charge. Without a pedagogical SOP, support confuses temporary reservations with final debits or P1 incidents.
Five typical bank reservation frictions
Visible line not debited: statement reservation is not card capture
Reduced available balance: impact on card limit map
Unclear release timeframe: when bank releases 3-7d map
Checkout abandonment: hold remains after cart is abandoned map
Double charge panic: reservation + debit perceived twice map
Banks display reservations before final debit, with variable release times (ECB, card payments 2026). Without TMPHOLD-MAP, agents improvise timeframes and statement status.
TMPHOLD #791 vs AUTHCAP #773, DBLCHRG #789, PCAPNO #767 and bot #792
Six contents, six distinct authorization hold statement experiences.
Quick matrix
#791 TMPHOLD: visible reservation, not charged, customer bank education
AUTHCAP #773: merchant flow auth capture expiration void distinct bank display
DBLCHRG #789: two identical distinct charges temporary reservation
PCAPNO #767: charge captured without order distinct incident hold pending
Declined payment: blocked card distinct visible reservation
#792 TMPHOLDbot: bot explaining authorization hold without panic tier 1
#791 = what the customer sees on their bank statement. #773 = Shopify merchant capture settings.
Which tmphold_* typologies should be classified?
Eight temporary bank hold ticket scenarios.
Eight tmphold typologies
tmphold_statement_visible: hold line visible on statement map
tmphold_not_debited: reserved amount not yet debited map
tmphold_release_delay: when bank release occurs map
tmphold_balance_impact: available balance reduced map
tmphold_abandoned_checkout: hold after abandoned cart map
tmphold_vs_debit: difference between hold and final debit map
tmphold_bank_display: bank pending label in progress map
tmphold_panic_chargeback: panic dispute threat map
Tags: tmphold, bank_hold, payment_pedagogy. HOLD-CITE: hold_explain_copy not_debited_copy map only.
How should the TMPHOLD-MAP matrix be structured?
The TMPHOLD-MAP matrix documents bank hold training for agents and the future bot #792.
TMPHOLD-MAP Columns
tmphold_program_id: bank hold map program identifier
hold_explain_copy: what is bank hold map
not_debited_copy: bank statement visible not final debit map
release_delay_copy: bank release period 3-7 days map
statement_display_copy: pending statement labels map
available_balance_copy: available balance impact map
abandoned_checkout_copy: authorization hold after abandoned checkout map
vs_debit_copy: difference between authorization hold and capture map
authcap_reroute_copy: merchant flow capture distinct from standard hold map
dblchrg_reroute_copy: double debit distinct from hold map
bot_intent_map: bot_tmphold_* #792 mapping
Sync helpdesk macros, bank_hold payment_pedagogy tags and agent training HOLD-CITE before RELEASE-CITE.
Policy TMPHOLD-SUP in six rules
Six temporary bank reservation support rules.
TMPHOLD-MAP-GROUNDED: hold response from map only
HOLD-CITE: hold_explain_copy not_debited_copy cite map verbatim
RELEASE-CITE: release_delay_copy cite map only
NO-PANIC: calm, educational tone, no accusation merchant map
AUTHCAP773-REROUTE: merchant capture → #773 distinct simple bank display
DBLCHRG789-REROUTE: two identical charges → #789 distinct temporary reservation
Flow TMPHOLD TH-1 to TH-8
Flow agent eight steps temporary bank reservation.
TH-1 Intake: tmphold_* intent + order_ref amount date bank_statement screenshot
TH-2 TMPHOLD-MAP: hold not_debited release statement balance abandon vs_debit authcap dblchrg
TH-3 Statement verify: label pending reservation in progress verify
TH-4 Classify: visible not_debited release balance abandon vs_debit panic
TH-5 Triage: HOLD RELEASE NO-PANIC AUTHCAP773 DBLCHRG789 PCAPNO767
TH-6 Respond: macro TMPHOLD grounded hold_explain release_delay calm
TH-7 Guide: vs_debit_copy statement_display_copy education statement
TH-8 Close: tag tmphold_resolved hold_cited release_cited panic_calmed Y/N
SLA: tmphold_statement_visible answered with HOLD-CITE hold_explain_copy and RELEASE-CITE in one interaction.
Essential TMPHOLD macros
Four macro temporary bank reservation agents.
TMPHOLD-HOLD-01
"Bank reservation: [hold_explain_copy map.] [not_debited_copy map.] Release if canceled: [release_delay_copy map.] HOLD-CITE RELEASE-CITE."
TMPHOLD-NOTDEBIT-01
"Not yet debited: [not_debited_copy map.] [statement_display_copy map.] Available balance: [available_balance_copy map.] HOLD-CITE."
TMPHOLD-RELEASE-01
"Bank release: [release_delay_copy map.] [abandoned_checkout_copy map if abandoned.] RELEASE-CITE."
TMPHOLD-VSDEBIT-01
"Reservation vs debit: [vs_debit_copy map.] [authcap_reroute_copy map if merchant capture.] NO-PANIC."
Edge cases: merchant auth capture, double charge, orphan transaction, and cart abandonment
Five cases outside of standard bank reservation macro.
Scheduled merchant capture: AUTHCAP773-REROUTE #773 trigger distinct ship hold simple
Two identical charges: DBLCHRG789-REROUTE #789 distinct pending reservation
Captured charge without order: #767 incident P1 distinct hold pending
Abandoned checkout hold: abandoned_checkout_copy release_delay_copy map
Chargeback panic: NO-PANIC HOLD-CITE before finance escalation
Hold pending statement = HOLD-CITE RELEASE-CITE. Merchant capture = AUTHCAP773-REROUTE.
Essential tmphold KPIs
Five TMPHOLD management metrics.
tmphold_hold_cite_rate: HOLD-CITE / total tmphold statement not_debited
tmphold_release_cite_rate: RELEASE-CITE / total tmphold release abandon
tmphold_panic_deflect_rate: closed ticket without escalation / total tmphold_panic
tmphold_authcap_misroute_rate: AUTHCAP tickets despite simple hold / total
tmphold_csat: CSAT bank reservation segment post map education
Target: tmphold_hold_cite_rate 100% and tmphold_panic_deflect_rate increasing post TMPHOLD-MAP.
Anti-patterns TMPHOLD
Five common errors in bank reservation support.
Denying statement footprint: HOLD-CITE hold_explain_copy not_debited_copy map
Promising normal hold refund: NO-PANIC release_delay_copy not refund map
Double charge route: DBLCHRG789-REROUTE verify two distinct captures hold
Ignoring release delay: RELEASE-CITE release_delay_copy mandatory map
Confusing merchant capture: AUTHCAP773-REROUTE vs simple client hold map
TMPHOLD with Qstomy
Qstomy on Shopify: detect tmphold intent, TMPHOLD-MAP RAG grounded, statement classify, HOLD-CITE guardrail, handoff #792 bot tier 1 or finance if incident.
Pipeline: #792 bot pedagogy authorization hold without panic tier 1 → #791 agents AUTHCAP DBLCHRG escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
TMPHOLD Checklist (8 steps)
TMPHOLD-MAP v1: hold not_debited release statement balance abandon vs_debit authcap dblchrg
Policy TMPHOLD-SUP: 6 rules HOLD RELEASE NO-PANIC AUTHCAP773 DBLCHRG789
8 tmphold_* typologies: tags helpdesk bank_hold payment_pedagogy
4 TMPHOLD-* macros: HOLD NOTDEBIT RELEASE VSDEBIT
FR bank statement labels: pending ongoing reservation map test
30-min agent training: HOLD-CITE before double charge accusation
Abandon checkout runbook: release_delay_copy abandoned_checkout test
KPI Dashboard: tmphold_* section 9 hold_cite panic_deflect authcap_misroute
FAQ
Difference AUTHCAP #773?
#773 = merchant flow auth capture void expiration. #791 = what the bank displays to the customer on their statement.
Reservation = charge?
No. TMPHOLD-NOTDEBIT-01 not_debited_copy hold_explain_copy map.
When is the cart abandonment release?
TMPHOLD-RELEASE-01 release_delay_copy abandoned_checkout_copy map.
Relation to #792 bot?
#792 = bot explain footprint without panic tier 1. #791 = agents escalate AUTHCAP DBLCHRG.
Going Further
This week: index TMPHOLD-MAP release_delay by FR top 5 bank, sync bank_hold tags, test TMPHOLD-HOLD-01 macro on scenario pending row 89 € cart abandonment.
Enzo
July 1, 2026
