E-commerce
July 1, 2026
“I paid, why is my order pending?” “3DS blocked, order created but not shipped.” “Wire transfer sent yesterday, status still Pending.” Three tickets where a poorly explained pending payment status generates anxiety, follow-ups, and premature shipping promises.
The e-commerce pending payment order support covers Shopify Pending status, incomplete 3DS, ongoing wire transfers, and banking delays. Distinct from payment refused: here, the order is created but payment is not finalized or is undergoing validation.
This guide #763 covers policy PNDPAY-SUP, flows PD-1 to PD-8, and matrix PNDPAY-MAP. Future customer service pair bot PNDPAY (#764).
Summary
Why do pending payment orders generate tickets?
The customer sees a confirmed order email but the status is pending, or 3DS was interrupted. The agent promises immediate shipment, ignoring the SEPA delay or confusing Pending with rejected payment.
Five typical frictions during payment pending
Opaque Pending status: customer does not understand progress map
Incomplete 3DS: bank authentication not finalized map
Transfer in progress: SEPA 1-3 days before credit map
Card auth not captured: pre-authorization pending map
BNPL being validated: Klarna Afterpay approval pending map
Shopify distinguishes financial status Pending Paid Refunded (Shopify, order statuses 2026). Without PNDPAY-MAP, support and finance diverge on the customer's next steps.
PNDPAY #763 vs transfer #322, payment declined, refund #370, and bot #764
Six contents, six distinct payment status pathways.
Quick matrix
#763 PNDPAY: Pending 3DS status transfer bank delay next steps
Transfer #322: WIRE-PROOF distinct reconciliation general Pending status
Payment declined: blocked card distinct Pending order created
Refund #370: pending refund distinct incoming payment
Net terms #234: deferred post-delivery payment distinct upfront Pending
#764 PNDPAYbot: bot status next steps tier 1
#322 = detailed transfer playbook. #763 = Pending status hub all payment methods.
Which pndpay_* typologies should be classified?
Eight scenarios for tickets with orders pending payment.
Eight pndpay typologies
pndpay_status_why: why order pending map
pndpay_3ds_pending: incomplete 3DS authentication map
pndpay_wire_pending: wire transfer sent awaiting credit map
pndpay_auth_hold: uncaptured card pre-authorization map
pndpay_bnpl_pending: BNPL Klarna validation in progress map
pndpay_manual_pending: manual payment Mark as Paid expected map
pndpay_bank_delay: bank processing delay explain map
pndpay_expedite_request: shipment before payment confirmed map
Tags: pndpay, pending_payment, order_status. STATUS-CITE: pending_status_policy_copy map only.
How should the PNDPAY-MAP matrix be structured?
The PNDPAY-MAP matrix documents each payment method and Pending status response for agents and future bot #764.
PNDPAY-MAP Columns
pndpay_program_id: payment pending program identifier map
payment_method: card wire bnpl paypal manual map
pending_status_policy_copy: meaning of Pending for this method map
expected_delay_copy: normal validation delay map
next_steps_copy: customer actions to unblock map
no_ship_before_paid_copy: shipping policy before Paid map
escalation_finance_copy: when finance should Mark as Paid map
wire_reroute_copy: bank transfer playbook link #322 map
exclusions_copy: pre-order Net terms out of scope map
bot_intent_map: bot_pndpay_* #764 mapping
Sync helpdesk macros, METHOD-CITE agent training, and finance runbook Pending queue.
PNDPAY-SUP policy in six rules
Six rules support orders pending payment.
PNDPAY-MAP-GROUNDED: status response from map only
STATUS-CITE: pending_status_policy_copy cite map verbatim
METHOD-CITE: payment_method order verify before map response
NO-SHIP-PROMISE: no shipment promised before Paid map
WIRE322-REROUTE: wire detail → #322 WIRE-PROOF distinct hub Pending
DECLINED-REROUTE: declined card → declined payment distinct Pending created
Flow PNDPAY PD-1 to PD-8
Flow agent eight steps orders pending payment.
PD-1 Intake: pndpay_* intent + order_ref payment_method financial_status screenshot
PD-2 PNDPAY-MAP: method policy delay next_steps no_ship escalation wire
PD-3 Order lookup: financial_status payment_gateway verify METHOD-CITE
PD-4 Classify: status 3ds wire auth bnpl manual bank_delay expedite
PD-5 Triage: STATUS METHOD NO-SHIP NEXT-STEPS WIRE322 DECLINED FINANCE
PD-6 Respond: macro PNDPAY grounded pending_status_policy_copy
PD-7 Execute: finance Mark as Paid 3DS retry wire match escalate
PD-8 Close: tag pndpay_resolved status_cited paid_confirmed Y/N
SLA: pndpay_status_why answered with STATUS-CITE pending_status_policy_copy and next_steps_copy in one interaction.
Essential PNDPAY macros
Four macro-agents orders pending payment.
PNDPAY-STATUS-01
"Order [order_ref map] [payment_method map]: [pending_status_policy_copy map.] Standard delay: [expected_delay_copy map.] STATUS-CITE."
PNDPAY-3DS-01
"3DS Authentication: [next_steps_copy map.] Finalize bank validation or retry payment. NO-SHIP-PROMISE before Paid map."
PNDPAY-WIRE-01
"Pending wire transfer: [expected_delay_copy map.] [wire_reroute_copy map WIRE322.] Proof: playbook #322."
PNDPAY-NEXT-01
"Next steps: [next_steps_copy map.] Shipment after confirmed Paid status: [no_ship_before_paid_copy map.]"
Edge cases: pre-order, net terms, fraud and duplicate order
Five cases outside the standard waiting-for-payment macro.
Product pre-order: exclusions_copy awaiting shipment distinct from awaiting payment
B2B Net terms: exclusions_copy #234 deferred payment distinct from Pending upfront
Shipment before Paid VIP: escalation_finance_copy documented exception map only
Wire proof fraud: WIRE322-REROUTE #322 WIRE-PROOF validation
Pending duplicate order: cancel duplicate distinct payment status
Pending payment = STATUS-CITE + next_steps. Pre-order or Net terms = distinct reroute playbooks.
Essential pndpay KPIs
Five PNDPAY steering metrics.
pndpay_status_cite_rate: STATUS-CITE / total pndpay pending
pndpay_paid_convert_rate: Pending → Paid after ticket / total pndpay map
pndpay_ship_promise_violations: promised shipment before Paid audit target 0
pndpay_misroute_wire_rate: processed at hub without #322 on wire low target
pndpay_finance_escalation_rate: Mark as Paid finance / total pndpay manual wire map
Target: pndpay_status_cite_rate higher than 95% and pndpay_ship_promise_violations at 0.
PNDPAY Anti-patterns
Five common support errors for orders awaiting payment.
Shipment promised before Paid: NO-SHIP-PROMISE no_ship_before_paid_copy map
Confusing declined payment: DECLINED-REROUTE blocked card distinct Pending
Unidentified method: METHOD-CITE payment_method before diagnosis
Wire transfer without #322: WIRE322-REROUTE WIRE-PROOF detailed playbook
Agent-invented delay: STATUS-CITE expected_delay_copy map only
PNDPAY with Qstomy
Qstomy on Shopify: detect pndpay intent, PNDPAY-MAP RAG grounded, order financial_status lookup, status cite, handoff #764 bot tier 1 next steps.
Pipeline: #764 bot status next steps tier 1 → #763 finance agents Mark as Paid escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
PNDPAY Checklist (8 steps)
PNDPAY-MAP v1 : method policy delay next_steps no_ship wire escalation exclusions
Policy PNDPAY-SUP : 6 rules STATUS METHOD NO-SHIP WIRE322 DECLINED
8 typologies pndpay_* : tags helpdesk pending_payment order_status
4 macros PNDPAY-* : STATUS 3DS WIRE NEXT
Order financial_status lookup : card wire bnpl manual test agents
Agent training 30 min : METHOD-CITE before STATUS PNDPAY-FLOW
Sync finance Pending queue : Mark as Paid SLA test wire 3DS
Dashboard KPI : pndpay_* section 9 status_cite ship_promise paid_convert
FAQ
Difference bank transfer #322?
#322 = WIRE-PROOF detailed reconciliation. #763 = Pending status hub for all payment methods including bank transfer.
Can an agent promise shipping?
No. NO-SHIP-PROMISE no_ship_before_paid_copy map before Paid.
3DS blocked, what to do?
PNDPAY-3DS-01 next_steps_copy map. Customer completes bank auth.
Relationship with #764 bot?
#764 = bot for next steps status tier 1. #763 = finance agents Mark as Paid escalate.
Going further
This week: index PNDPAY-MAP card wire bnpl, sync financial_status lookup, test macro PNDPAY-STATUS-01 3DS Pending scenario.
Enzo
July 1, 2026
