E-commerce

How to handle customer questions about payment receipts

How to handle customer questions about payment receipts

July 1, 2026

"I need a payment receipt for my accounting." "Where is the proof that I paid?" "Is the order confirmation enough as proof of debit?" Three tickets where an insufficiently explained payment receipt generates invoice confusion and expense report blockages.

The e-commerce payment receipt support covers proof of debit, document resentment, and the distinction between receipt vs. tax invoice. Distinct from invoice not found (#359): here, proof of customer account payment, not a VAT tax document.

This guide #795 covers policy PRCPT-SUP, flows PR-1 to PR-8, and the PRCPT-MAP matrix. Pair support of the future PRCPT bot (#796).

Summary

Why do payment receipt requests generate tickets?

The customer has paid and is looking for a proof of purchase for accounting, expense reports, or employer reimbursement. The agent sends a Shopify confirmation or tax invoice to the wrong place. Without a SOP, support routes the invoice as not found or VAT instead of explaining the payment receipt.

Five typical payment receipt frictions

  • Receipt not found: customer does not know where to download map

  • Receipt/invoice confusion: proof of debit vs. tax document map

  • Bank debit proof: employer statement requires map document

  • Guest checkout: no customer history account map

  • PayPal Apple Pay: wallet receipt distinct from map confirmation

Shopify sends a native order confirmation, payment receipt depending on the app or template (Shopify, order management 2026). Without PRCPT-MAP, agents confuse administrative documents.

PRCPT #795 vs invoice #254, invoice not found #359, proforma and bot #796

Six contents, six distinct payment document paths.

Quick Matrix

#795 = proof of payment. #254/#359 = compliant tax invoice.

Which prcpt_* typologies should be classified?

Eight scenarios for payment receipt received.

Eight prcpt typologies

  1. prcpt_request: general payment receipt request map

  2. prcpt_vs_invoice: confusion between receipt and tax invoice map

  3. prcpt_resend: resend receipt email map

  4. prcpt_proof_debit: bank debit proof accounting map

  5. prcpt_expense_report: employer expense report map

  6. prcpt_paypal_wallet: distinct PayPal Apple Pay receipt map

  7. prcpt_guest_checkout: guest no account history map

  8. prcpt_wrong_document: confirmation sent instead of receipt map

Tags: prcpt, payment_receipt, proof_payment. RECEIPT-CITE: receipt_explain_copy map only.

How should the PRCPT-MAP matrix be structured?

The PRCPT-MAP matrix documents the payment receipt response for agents and future bot #796.

PRCPT-MAP Columns

  • prcpt_program_id: map payment receipt program identifier

  • receipt_explain_copy: what is the map payment receipt

  • receipt_vs_invoice_copy: difference between map receipt and tax invoice

  • receipt_where_find_copy: where to find map email account receipt

  • receipt_resend_policy_copy: resend map email policy receipt

  • proof_debit_copy: proof of map amount date debit

  • order_confirmation_copy: confirmation can serve as map proof

  • paypal_receipt_copy: PayPal receipt activity wallet map

  • invoice_reroute_copy: need map tax invoice

  • missing_inv_reroute_copy: map PDF invoice not found

  • bot_intent_map: bot_prcpt_* #796 mapping

Sync helpdesk macros, payment_receipt proof_payment tags and agent training RECEIPT-CITE before VS-INVOICE-CITE.

PRCPT-SUP six-rule policy

Six payment receipt support rules.

  1. PRCPT-MAP-GROUNDED: response received from map only

  2. RECEIPT-CITE: receipt_explain_copy cites map verbatim

  3. VS-INVOICE-CITE: receipt_vs_invoice_copy cites if map confusion

  4. ORDER-LOOKUP-FIRST: lookup paid order before sending map document

  5. INV254-REROUTE: VAT tax invoice → #254 distinct payment receipt

  6. MISSING359-REROUTE: PDF invoice not found → #359 distinct debit proof

Flow PRCPT PR-1 to PR-8

Flow agent eight-step payment receipt.

  1. PR-1 Intake: prcpt_* intent + order_ref email payment_method document_needed

  2. PR-2 PRCPT-MAP: receipt vs_invoice where_find resend proof confirmation paypal invoice missing

  3. PR-3 Order lookup: Shopify order paid payment_method transactions verify

  4. PR-4 Classify: request vs_invoice resend proof expense paypal guest wrong_doc

  5. PR-5 Triage: RECEIPT VS-INVOICE RESEND PROOF INV254 MISSING359 CONFIRM

  6. PR-6 Respond: macro PRCPT grounded receipt_explain receipt_where_find

  7. PR-7 Send: receipt_resend_policy_copy portal link order status

  8. PR-8 Close: tag prcpt_resolved receipt_cited document_sent Y/N

SLA: prcpt_request answered with RECEIPT-CITE receipt_where_find_copy in one interaction.

Essential PRCPT macros

Four macro agents payment receipt.

PRCPT-EXPLAIN-01

"Receipt payment: [receipt_explain_copy map.] Where to find it: [receipt_where_find_copy map.] Proof of debit: [proof_debit_copy map.] RECEIPT-CITE."

PRCPT-VSINV-01

"Receipt vs invoice: [receipt_vs_invoice_copy map.] Need tax invoice: [invoice_reroute_copy map.] VS-INVOICE-CITE."

PRCPT-RESEND-01

"Order #[order_ref map]: [receipt_resend_policy_copy map.] Link: [order_status_url map.] Check spam. RECEIPT-CITE."

PRCPT-PROOF-01

"Proof of payment: [proof_debit_copy map.] [order_confirmation_copy map.] PayPal: [paypal_receipt_copy map.] Amount date method map."

Edge cases: tax invoice, PayPal, confirmation, and guest

Five cases outside major standard payment receipts.

Proof of debit = RECEIPT-CITE. Tax document = INV254 or MISSING359 reroute.

Essential perception KPIs

Five PRCPT management metrics.

  • prcpt_receipt_cite_rate: RECEIPT-CITE / total prcpt request

  • prcpt_resend_success_rate: document sent post-macro / total prcpt_resend

  • prcpt_vs_invoice_misroute_rate: invoice sent instead of receipt / total prcpt

  • prcpt_first_contact_resolve: closed without escalation / total prcpt

  • prcpt_csat: CSAT segment receipt of payment post document map

Target: prcpt_receipt_cite_rate 100% and prcpt_vs_invoice_misroute_rate decreasing post PRCPT-MAP.

PRCPT anti-patterns

Five common payment received support errors.

  1. Sending invoice as receipt: VS-INVOICE-CITE receipt_vs_invoice_copy map

  2. Confusing confirmation with receipt: order_confirmation_copy may suffice as proof map

  3. No order lookup: ORDER-LOOKUP-FIRST paid verify before sending

  4. Invoice route not found: MISSING359-REROUTE only if tax invoice requested

  5. Ignoring PayPal wallet: paypal_receipt_copy PayPal activity distinct from confirmation map

PRCPT with Qstomy

Qstomy on Shopify: detect prcpt intent, PRCPT-MAP RAG grounded, order lookup classify, RECEIPT-CITE guardrail, handoff #796 bot tier 1 or finance if invoice.

Pipeline: #796 bot retrieve resend tier 1 → #795 agents INV254 MISSING359 escalate.

Explore AI support and request a demo.

Checklist, FAQ and going further

PRCPT Checklist (8 steps)

  1. PRCPT-MAP v1: receipt vs_invoice where_find resend proof confirmation paypal invoice missing

  2. Policy PRCPT-SUP: 6 rules RECEIPT VS-INVOICE ORDER-LOOKUP INV254 MISSING359

  3. 8 typologies prcpt_*: tags helpdesk payment_receipt proof_payment

  4. 4 macros PRCPT-*: EXPLAIN VSINV RESEND PROOF

  5. Order status page sync: receipt_where_find link test guest

  6. 30-min Agent Training: VS-INVOICE-CITE before sending invoice

  7. PayPal receipt runbook: paypal_receipt_copy activity wallet test

  8. Dashboard KPI: prcpt_* section 9 receipt_cite misroute first_contact

FAQ

Difference invoice #254?
Invoice = VAT tax document. #795 = payment receipt proof of debit client accounting.

Is confirmation enough?
Often yes for expense reports. PRCPT-PROOF-01 order_confirmation_copy proof_debit_copy map.

Client wants a tax invoice?
INV254-REROUTE #254 distinct receipt.

Relation to #796 bot?
#796 = bot to find, resend, explain tier 1. #795 = agents escalate invoice.

Go further

This week: index PRCPT-MAP receipt_where_find by guest account channel, sync tags payment_receipt, test macro PRCPT-VSINV-01 client scenario requests receipt receives explanation invoice reroute.

Enzo

July 1, 2026

Convert over 2,000 customers on average per month with Qstomy.

The world’s 1st Shopify AI dedicated to customer conversion

Empowering 200+ e-commerce merchants

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.