Payment Proof Run Sheet
Bevisa betalningskedjan utan att överdriva sandbox-läget
Den här ytan visar exakt vad som krävs för att kalla Flow-betalningar produktionsbevisade: start, paid, failure, retry, refund, dispute och reconciliation.
Decision
Proof-ready eller provider-blocked
Flow kan vara kodmässigt redo, men extern proof kräver riktig provider reference. Om Playground eller merchant-lane saknar marknad/valuta/recurring ska caset markeras provider-blocked.
6
lanes
5
rules
0
fake claims
Proof lanes
Vad finance, support och sälj måste kunna visa
Checkout start
Buyer starts checkout from the correct Flow plan, signed proposal or booking deposit.
- Order ID
- Tenant ID
- Plan/proposal reference
- Kustom mode
- Checkout URL or controlled provider error
Success proof
A paid reference can be tied back to tenant, proposal/booking and revenue reporting.
- Payment reference
- Paid timestamp
- Amount/currency
- Proposal or booking ID
- Reconciliation row
Failure + retry
Failed payments show safe customer copy, retry path and internal provider diagnostics.
- Failure code mapping
- Customer-safe message
- Retry event
- Recovery owner
- Final state
Refund or adjustment
Refunds and manual adjustments are traceable without breaking booking/proposal state.
- Adjustment ID
- Reason
- Owner
- Amount
- Linked order/proposal
Dispute / chargeback
Disputes have status, deadline, evidence pack and customer communication owner.
- Dispute ID
- Deadline
- Evidence checklist
- Owner
- Escalation state
Publish decision
Sales can use payment proof only when the provider reference and reconciliation are real.
- Approved claim
- Screenshot/export
- Redaction check
- Internal-only blocker if real reference is missing
Acceptance