E-commerce
July 5, 2026
"I transferred the money yesterday, why is my order still pending?" "Here is the proof of bank transfer, can you ship it?" "Is your bank details correct, the transfer bounced back?" Bank transfers reassure B2B buyers and high-value orders, but they create a grey area for support: the order exists, payment is promised, and shipping is waiting for a manual validation that no one has documented.
Cartly Pro reminds that with Shopify manual payment, the order remains in Pending status until you mark it as Paid after verification in your bank account (Cartly Pro, bank deposit 2026). Google Payments requires for any proof: executed status, amount, date, payer's name, recipient's IBAN, and reference (Google, proof of payment 2026).
This guide #322 covers customer support for bank transfer payments: delays, proofs, follow-ups, reconciliation. Distinct from proforma (#321) and Net terms (#234): here we deal with bank transfer as a payment method at checkout.
Summary
Why does a bank transfer generate more tickets than a credit card?
A card payment is binary: authorized or declined in seconds. A bank transfer is asynchronous: the customer pays, your bank credits, your team reconciles, Shopify switches to Paid, the warehouse ships. Every step can become a ticket.
Four structural frictions
Interbank delay: Instant SEPA or 1-3 business days depending on the bank
Missing reference: bank transfer without an order number = reconciliation impossible
Insufficient proof: blurry screenshot vs. valid bank confirmation
Shopify Pending status: customer believes that paying = shipping (Cartly Pro, manual payments 2026)
Typical volume
On a store with bank transfer enabled (B2B, high average order value, export), 8% to 20% of payment tickets concern delays, proof, or bank details. Shopify France ranks bank transfer among the most common manual payment methods in France (Shopify France, payments 2026).
Principle #322
WIRE-LOOP Pipeline: Pending order → clear instructions → funds received → WIRE-MATCH → Mark as Paid → customer confirmation.
How does it differ from proforma #321, Net terms #234, and bot #323?
Four payment contents, four moments of the flow.
Proforma (#321)
Proforma (#321): document before agreement, accounting validation. The #322: transfer completed or in progress, Shopify order reconciliation.
Net terms (#234)
Net terms (#234): deferred payment post-delivery, overdue invoice. The #322: upfront payment by bank transfer at checkout, order blocked in Pending.
VAT invoice (#160)
VAT (#160): tax mentions. The #322: payment and shipping status, not the invoice content.
Payment bot (#323)
Payment bot (#323): automated APAY-FLOW execution of #322 policies. The #322 sets after-sales policy, WIRE-PROOF, and reminders that the bot executes.
Promise #322
WIRE-INTENT, WIRE-POLICY, WIRE-PROOF, WIRE-MATCH, WIRE-CHASE, macros, finance ops, transfer KPI.
What WIRE-INTENT taxonomy should be used to route transfer tickets?
The WIRE-INTENT taxonomy classifies bank transfer requests before opening the case.
10 bank transfer intents
wire_instructions: Bank details (RIB, BIC), description, processing timewire_sent_pending: "I have transferred the money, order still pending"wire_proof_submit: sending proof for reconciliationwire_wrong_reference: incorrect description, partial amountwire_returned: bank transfer rejected or returned by bankwire_wrong_iban: incorrect details on the customer sidewire_partial: deposit received, balance expectedwire_duplicate: double bank transfer for the same orderwire_expedite_request: shipment request before credit is visiblewire_chase_overdue: unpaid customer reminder (Net terms + mixed bank transfer)
Prioritization
P1: wire_proof_submit with urgent order or limited stock. P2: wire_sent_pending. Separate bank_transfer tag from card_declined for analytics.
What must the WIRE-POLICY document contain?
The WIRE-POLICY document is the single source of truth for support, finance, and checkout.
14 policy blocks
Eligibility: validated B2B, cart > €X, authorized countries
Bank details: IBAN, BIC, account holder, bank (dated version)
Mandatory reference: format "CMD-{order_num}" or "{company_name} {order_num}"
Currency: EUR only or multi-currency with dedicated account
Announced credit processing time: SEPA 1-2 business days, instant if offered
Reconciliation SLA: account check 2×/business day, max 24 hours after credit
Mark as Paid SLA: within 4 business hours after confirmed WIRE-MATCH
Accepted WIRE-PROOF: see section 5, no unmasked full bank statement
Shipping before credit: never except for documented VIP accounts
Partial payment: deposit vs. balance rule
Transfer fees: OUR/SHA, who pays interbank fees
Pending cancellation: auto-cancel delay if unpaid by D+7
Fraud: fake receipt = cancellation + report
Owner: finance reconciles, support collects proof
Shopify Checkout
Payment method instructions: IBAN + "Please strictly indicate {order_name} as reference" + shipping delay post-validation. Wholesale Helper: instructions on order confirmation (Wholesale Helper, B2B wire 2026).
How to validate a proof with the WIRE-PROOF protocol?
The WIRE-PROOF protocol defines what proof support accepts to accelerate WIRE-MATCH without risk of fraud.
6 mandatory proof fields
Executed status: transaction confirmed, not "pending" (Google 2026)
Amount: equal to order total tax incl. (or documented partial payment)
Value date: past date, not future
Payer name: visible on confirmation
Beneficiary IBAN: your coordinates, not a third party
Reference: legible order or invoice number
Accepted / rejected documents
Accepted: bank transfer confirmation PDF, banking app screenshot with the 6 fields. Rejected: unmasked full bank statement, RIB alone, unexecuted transfer order. Fenige: download confirmation from transactions history (Fenige, proof 2026). Springlane: copy of transfer + order details by email (Springlane, payment not found 2026).
Agent decision tree
Proof received → verify 6 fields → search bank credit → if match: Mark as Paid + WIRE-CONFIRM macro → if not yet credited: WIRE-WAIT macro with delay stated in policy.
How do you reconcile an order and a bank transfer with WIRE-MATCH?
The WIRE-MATCH workflow links bank receipts and pending Shopify orders.
5 reconciliation steps
Export incoming bank transfers (minimum 2×/business day)
Primary match: description reference = {order_name}
Secondary match: amount + payer name + date ± 3 days of order
Tertiary match: WIRE-PROOF customer proof + manual search
Mark as Paid Shopify + note "Bank transfer received {date}, ref {bank_ref}"
Special cases
Partial amount: if deposit policy, tag partial, follow up for balance
Overpayment: credit note or refund depending on policy
One bank transfer, N orders: allocate manually, never Mark as Paid in bulk blindly
Bank transfer without order: create draft or refund after identification
Security
Cartly Pro: verify funds on bank portal, do not rely solely on customer PDF. Fake proof of payment = do not ship, escalate to finance.
Which WIRE macros should be used depending on the intent?
Standard WIRE macros standardize delays and waiting times. Prefix WIRE- in Gorgias/Zendesk.
8 essential macros
WIRE-INSTR: IBAN, BIC, account holder, label "CMD-{order}", credit time {sla}
WIRE-WAIT: "Transfer received pending bank credit (1-2 business days SEPA). Shipping upon Mark as Paid."
WIRE-PROOF-OK: "Proof received, reconciliation in progress within {sla_match}."
WIRE-PROOF-BAD: "Please send bank confirmation with amount, date, reference CMD-{order}."
WIRE-CONFIRM: "Payment confirmed on {date}. Shipping preparation within {fulfillment_sla}."
WIRE-REF-FIX: "Missing reference: please resend {amount} with label CMD-{order}."
WIRE-RETURNED: "Transfer returned to bank. Please check IBAN/BIC and resend with the correct label."
WIRE-CHASE: unpaid outstanding follow-up D+3, D+7 (section 8)
Variables
{order_name}, {amount_ttc}, {iban_masked}, {sla_credit}, {bank_ref}. Link to templates (#34), prioritization (#26).
How should WIRE-CHASE follow-ups and announced deadlines be structured?
The WIRE-CHASE protocol covers customer reminders (unpaid) and delay communication (paid, not yet credited).
Reminders for unpaid Pending orders
D+0: order confirmation email + bank details + mandatory reference description
D+3: friendly reminder if still Pending, link to bank details
D+7: final reminder, auto-cancellation if policy applies
D+8: cancel order + stock release
Post-transfer customer communication
Plane recommends waiting until the end of the business day before escalating if the status is "paid on customer side" (Plane, payment delayed 2026). WIRE-WAIT macro with policy delay, no same-day shipping promise unless instant SEPA is confirmed by the bank.
Net terms + bank transfer
Shipped order, past due invoice: WIRE-CHASE D-7, D+0, D+7, D+14 post-due date. Cross-reference with Net terms (#234). Proof of transfer received before its due date: reconcile invoice, not Pending order.
Reminders forbidden
Threatening shipment without bank credit. Accepting screenshots without portal verification. Restlessly chasing before the announced SEPA delay.
Which B2B playbooks for France, export, and high average order value DTC?
The priority transfer intents vary by segment.
B2B Metropolitan France
Standard SEPA, reference CMD-{order}. Peak wire_sent_pending on Monday morning (weekend transfers). Shopify B2B corporate account: transfer + coexisting Net terms (Wholesale Helper, pay later 2026).
Non-SEPA Export
SWIFT, delivery times 3-5 days, OUR/SHA fees. Frequent wire_wrong_iban intent (SWIFT vs IBAN). WIRE-INSTR with dedicated EUR account. Link export proforma (#321).
High-Value DTC Cart
Transfer threshold enabled > €500 or €1000. Customer relatively unfamiliar: over-explain Pending status and processing times. Card payment link option as an alternative in case of urgency.
Local Authorities / Administration
Long administrative payment terms (30-60 days). Separate policy: production starts after purchase order, not after transfer. Account manager escalation.
Fraud
High-value cart + disposable email + Photoshop proof: do not Mark as Paid. Link Fraud support (#).
Which KPIs should be measured on the wire transfer flow?
Measure reconciliation delay and proof quality, not raw Pending volume.
Monthly KPIs
wire_match_sla: % of wire transfers reconciled under SLA policy
wire_time_to_paid: hours between bank credit and Mark as Paid
wire_ticket_rate: WIRE-INTENT tickets / wire orders
wire_proof_reject_rate: rejected / received proofs
wire_no_ref_rate: wire transfers without order reference
wire_cancel_unpaid: cancelled orders D+7 unpaid
wire_expedite_denied: shipping requests before credit (frictional track)
wire_fraud_flag: fake proof cases
Typical DTC Objectives
wire_match_sla > 95%. wire_time_to_paid < 4 business hours. wire_no_ref_rate < 15% (improving checkout instructions). Weekly finance x support review: top WIRE-PROOF-BAD reasons.
How does Qstomy accelerate proof collection and transfer tracking?
Qstomy does not replace finance bank reconciliation, but automates WIRE-PROOF collection and delay communication.
Capabilities
Intent
wire_instructions: bank details (RIB) and label from WIRE-POLICYIntent
wire_proof_submit: 6-field form + PDF uploadPending order status explained with SEPA policy delay
Finance escalation with structured payload (order, amount, ref)
WIRE-CONFIRM customer notification upon Mark as Paid webhook
Automated WIRE-CHASE follow-ups at D+3 unpaid
Quantified DTC Scenario
Light B2B brand, 340 wire transfer orders/month. Before #322: 62 wire tickets/month, wire_match_sla 78%, median wire_time_to_paid 11 h, 23% proofs rejected. After WIRE-POLICY + Qstomy: tickets 38/month, wire_match_sla 96%, wire_time_to_paid 2.5 h, rejected proofs 9%.
See AI support, sales agent, Shopify, demo. Interlinking: payments bot (#323).
Which playbooks to deploy WIRE-LOOP in four weeks?
Playbook 1: 90-day Pending Audit (4 h)
Export Bank Transfer Pending orders. Measure Mark as Paid delay, top verbatims, % without reference.
Playbook 2: WIRE-POLICY + checkout (1 d)
14 blocks section 4. Update Shopify payment method instructions. Email confirmation template WIRE-INSTR.
Playbook 3: WIRE-PROOF + macros (4 h)
8 macros section 7. Train agents on WIRE-MATCH tree. Finance process 2×/day.
Playbook 4: WIRE-CHASE Klaviyo (2 h)
Flows D+0, D+3, D+7 Pending unpaid. Full customer journey test.
Playbook 5: monthly review (60 min)
KPI section 10. Adjust checkout wording if wire_no_ref_rate is high.
Useful internal links
This week: open your last 20 Pending wire transfer orders and note how many had the order number in the bank reference field. If this rate is below 70%, your WIRE-INSTR checkout instructions are not yet visible early enough.
Enzo
July 5, 2026
