E-commerce
July 1, 2026
"The bot says refund tomorrow into my account." "The AI promises credit in 24 hours while Shopify is pending." "Invented 3-day delay, my bank says 10." Three failures where a non-grounded bank delay bot overpromises a date or ignores Shopify refund_status.
An AI bank refund delay chatbot does not replace BANKREF agents (#519). It reads BANKREF-MAP, cites bank_delay_days min max range, explains authorization hold vs credit, and hands off the ARN if the threshold is exceeded.
This guide #520 covers intents bot_bank_ref_*, flowchart BANKREFbot, and KPI bankref_bot. Bot pair to the BANKREF playbook (#519). New AI use case: reassuring post-refund without inventing an exact date.
Summary
Why automate bank delays with a bot?
The "where is my bank refund?" follow-up arrives D+1 to D+15 post Shopify success. A calibrated bot reads refund_status and BANKREF-MAP in seconds, without promising credit tomorrow.
What the bot solves tier 1
Bank delay range: bank_delay_days_min max map
Refund status cite: pending success failed Shopify
Auth hold explain: auth_hold_release_days imprint
Too early educate: days_since vs bank_delay_min
Statement descriptor: statement_descriptor map
Shopify documents 5 to 10 business days bank credit post-refund (Shopify, refunds 2026). The bot intercepts bot_bank_ref_not_visible before chargeback.
BANKREFbot vs BANKREF #519, ref_stat #370 and REF-EXP #369
Four contents, four refund timeline layers.
Quick matrix
#520 BANKREFbot: bot bank delay range auth tier 1
#519 BANKREF: agents ARN finance escalate
Bot ref_stat #370: general refund status lookup
#369 REF-EXP: failed refund expired card IBAN
Pipeline: #370 ref_stat status → #520 bank delay if success waiting bank → #519 ARN if > escalate_threshold.
Which bot_bank_ref_* intents should be configured?
Eight bot bank delay intents.
Eight bot_bank_ref intents
bot_bank_ref_not_visible: Shopify refunded nothing on statement
bot_bank_ref_how_long: how many days bank credit
bot_bank_ref_auth_hold: authorization still visible
bot_bank_ref_too_early: follow-up before bank_delay_min
bot_bank_ref_paypal: PayPal wallet delay distinct
bot_bank_ref_bnpl: Klarna payment schedule adjusted handoff
bot_bank_ref_descriptor: statement descriptor explain
bot_bank_ref_arn_handoff: threshold exceeded → #519 ARN
Tier 1 auto: not_visible, how_long, auth_hold, too_early, descriptor if refund lookup + BANKREF-MAP row.
Intent bot_bank_ref_arn_handoff, failed refund and bnpl dispute → agents #519 or #369 with payload order_id, refund_status, days_since.
How to consume BANKREF-MAP #519?
The bot reads BANKREF-MAP #519: payment_method, shopify_refund_status, bank_delay_days_min, bank_delay_days_max, statement_descriptor, auth_hold_release_days, arn_available, escalate_threshold_days, customer_action.
Lookup grounded
Order refund API: refund_status amount date payment_method
Days since calc: today minus refund_date business days
BANKREF-MAP row: payment_method + refund_status branch
Delay range cite: min max business days only
Threshold gate: arn handoff if days > escalate_threshold
Alignment anti-hallucination (#123): delays = BANKREF-MAP whitelist only.
BANKREFBOT-SUP policy in six rules
Six bot rules for a safe banking delay.
NO-EXACT-DATE: min-max range of business days only
BANKREF-MAP-GROUNDED: never delay out of map
VERIFY-REFUND-STATUS: pending vs success before bank timeline
AUTH-VS-REFUND: authorize hold explain if auth_hold intent
NO-24H-PROMISE: never tomorrow credit guaranteed
ARN-HANDOFF: days > threshold → #519 do not invent ARN
Flow BANKREFbot BRB-1 to BRB-8
Eight-step bank delay bot flow.
BRB-1 Classify: bot_bank_ref_* intent
BRB-2 Order lookup: refund_status amount date method
BRB-3 Days calc: days_since_refund business days
BRB-4 BANKREF-MAP: delay range descriptor auth rules
BRB-5 Guardrail: NO-EXACT-DATE VERIFY-REFUND-STATUS
BRB-6 Respond: TPL-BANKREFbot grounded range
BRB-7 Deescalate: chargeback threat timeline cite
BRB-8 Log handoff: delay_cited tag bankref_bot ARN if needed
TPL-BANKREFbot-TIMELINE Example
"Refund of [amount] € initiated on [refund_date] status [refund_status]. Bank credit within [bank_delay_days_min] to [bank_delay_days_max] business days. Statement descriptor: [statement_descriptor]. Follow up after [bank_delay_days_max] days if missing."
TPL-BANKREFbot and touchpoints templates
Four essential templates.
TPL-BANKREFbot-TIMELINE
Refund [amount] € on [date]. Bank: [min] to [max] business days. Descriptor: [descriptor].
TPL-BANKREFbot-AUTH
Authorization [amount] € can remain [auth_hold_release_days] days without debit. Refund credits available balance.
TPL-BANKREFbot-TOO-EARLY
Initiated [days_since] days ago. Normal: [min] to [max] business days. Patience recommended before contacting bank.
TPL-BANKREFbot-PENDING
Pending processor status. Bank credit after Shopify success. Typical timeframe: [min] to [max] business days post-success.
Touchpoints
Post-refund success email: auto TPL-BANKREFbot-TIMELINE
Order status refund chip: bot_bank_ref_how_long entry
Post-return D+3 proactive: bot_bank_ref_too_early prevent
Help center FAQ bank processing time: bot embed range grounded
Edge cases and reroutes
Five cases outside tier 1 bot.
Refund not started: #370 ref_stat_not_started
Refund failed expired: #369 REF-EXP handoff IBAN
Partial amount: #368 partial explain
BNPL schedule: installment adjust handoff #519
Chargeback menace P1: deescalate then handoff #519 finance
Bot does not contact customer bank: handoff #519 ARN if days > escalate_threshold_days map.
Essential bankref_bot KPIs
Five BANKREFbot steering metrics.
bankref_bot_auto_resolve: % tier 1 without agent
bankref_bot_delay_grounded_rate: BANKREF-MAP compliant answers
bankref_bot_exact_date_violation: NO-EXACT-DATE, target 0
bankref_bot_deescalate_rate: % chargeback threat calmed
bankref_bot_handoff_arn: sessions → #519 threshold
Monthly red team: 10 prompts "credit tomorrow guaranteed", "24 h promised", "exact date March 15". Date out of range = NO-EXACT-DATE violation.
Anti-patterns BANKREFbot
Six common mistakes.
Exact date promised: NO-EXACT-DATE violation
24 h credit guaranteed: NO-24H-PROMISE
Timeline if pending: VERIFY-REFUND-STATUS
Invented timeframe: BANKREF-MAP-GROUNDED
Duplicate entire ref_stat #370: bank delay focus
Invented ARN: ARN-HANDOFF #519 only
BANKREFbot with Qstomy
Qstomy on Shopify: detect bank_ref intent, BANKREF-MAP RAG, refund API lookup, TPL-BANKREFbot timeline widget, proactive post-refund e-mail, handoff #519 ARN threshold payload.
Pipeline: #370 ref_stat router → #520 bank delay → #519 ARN → AI governance #142 audit delay claims.
Explore AI support and request a demo.
Checklist, FAQ and going further
BANKREFbot Checklist (8 steps)
Sync BANKREF-MAP #519: RAG bot whitelist only
Policy BANKREFBOT-SUP: 6 NO-EXACT-DATE rules
8 intents bot_bank_ref_*: flow BRB-1 to BRB-8
4 templates TPL-BANKREFbot-*: TIMELINE AUTH TOO-EARLY PENDING
Refund API sync: status amount date method
Post-refund e-mail auto: TPL-BANKREFbot-TIMELINE
Red team 10 prompts: tomorrow guaranteed 24 h exact date
Dashboard KPI: bankref_bot_* section 9
FAQ
Difference #519?
#519 = ARN agents finance escalate. #520 = bot tier 1 delay range reassure.
Difference ref_stat #370?
#370 = general refund status. #520 = bank delay post-success focus.
Does bot promise exact date?
No. Min max range business days only.
ARN provided by bot?
No. Handoff #519 if > escalate_threshold.
Going further
p: Playbook BANKREF (#519)
This week: index BANKREF-MAP in bot corpus, test red team "credit tomorrow guaranteed", measure bankref_bot_delay_grounded_rate. Enable auto post-refund success e-mail.
Enzo
July 1, 2026
