Skip to main content
Qubicweb logo
Trust Notes/Trust note
Trust NoteLowMedium confidence

Verify Payment in Official Platform Records Before Release or Fulfilment

Users should verify payment status only inside the official platform checkout, booking, or escrow record before releasing an item, beginning fulfilment, or marking a service job complete. Screenshots, forwarded receipts, and off-platform messages may be useful context, but should not be treated as final proof of payment.

21 June 2026BuyersSellersService Providers

Pattern detected

General fraud-prevention guidance indicates that payment confirmation can be misrepresented through private screenshots, forwarded receipts, or off-platform messages. The safer pattern is to rely on the authoritative platform payment, booking, checkout, or escrow record.

Why it matters

Releasing goods, starting work, or closing a service job before confirming payment in the official platform record can expose sellers, service providers, and marketplace users to non-payment, chargeback confusion, or social-engineering attempts.

Context

Users should verify payment status only inside the official platform checkout, booking, or escrow record before releasing an item, beginning fulfilment, or marking a service job complete. Screenshots, forwarded receipts, and off-platform messages may be useful context, but should not be treated as final proof of payment.

Who is affected

Marketplace sellers, buyers, service providers, booking participants, escrow users, fulfilment teams, and support operators who rely on checkout, booking, escrow, or payment-status records.

Products

Booking RecordEscrow RecordOfficial Platform Checkout

Channels

CheckoutBookingEscrowOff Platform Messages

Audience

BuyersSellersService ProvidersOperations Reviewers

Observed signals

  • Manual-review guidance submitted under fraud_prevention category.
  • Affected products listed as booking_record, escrow_record, and official_platform_checkout.
  • Affected channels listed as checkout, booking, escrow, and off_platform_messages.
  • Single supplied signal ID: fa7ae178-5c32-482f-b4fa-4282765d209a.
  • Corroboration count supplied as 1; this appears to be general safety guidance rather than evidence of a specific incident.

Recommended action

Before releasing an item, starting fulfilment, handing over access, or marking a job complete, check the official platform checkout, booking, or escrow page. Treat screenshots, forwarded emails, payment-reference numbers, and private chat messages as supporting information only. If the platform record does not show payment as cleared, funded, captured, or otherwise confirmed according to the platform’s rules, do not release or complete the transaction.

  • Before releasing an item, starting fulfilment, handing over access, or marking a job complete, check the official platform checkout, booking, or escrow page. Treat screenshots, forwarded emails, payment-reference numbers, and private chat messages as supporting information only. If the platform record does not show payment as cleared, funded, captured, or otherwise confirmed according to the platform’s rules, do not release or complete the transaction.

Public disclaimer

This note provides general safety guidance and does not accuse any person or organization of wrongdoing. Payment status should be verified according to the official platform’s current records and policies. Screenshots and forwarded messages can be misleading or incomplete.

Back to Trust NotesOpen Trust CentreReport suspicious activity
Verify Payment in Official Platform Records Before Release or Fulfilment - Qubicweb