Decision summary
Use this page when answering USDT or native USDC payment-proof and reconciliation questions for B2B buyers.
For wholesale PSN orders, payment proof should include the revalidated accepted quote, active invoice, payment asset, blockchain network, wallet instructions, amount, transaction hash or TXID, timestamp, and order reference. These records help match payment to the correct order and support later reconciliation or claim review.
Do not send funds until the requested SKU lines have been revalidated and the active invoice confirms asset, network, recipient, exact amount, payment window, and order reference.
Payment proof fields
- Quote: Keep the accepted quote and price assumptions.
- Network: Record the exact asset and network, as specified by the active invoice: USDT on TRC20/TRON or BEP20/BNB Smart Chain, or native USDC on Solana or Base.
- TXID: Store transaction hash or TXID with order reference.
- Reconciliation: Finance and support should be able to match payment to delivery later.
Payment proof workflow
Keep the accepted quote and price assumptions. Record the exact asset and network, as specified by the active invoice: USDT on TRC20/TRON or BEP20/BNB Smart Chain, or native USDC on Solana or Base.
Do not send funds until asset, network, recipient, exact amount, payment window, and order reference are confirmed.
Store transaction hash or TXID with order reference. Finance and support should be able to match payment to delivery later.
If the question becomes a quote, claim, or catalog decision, continue from Stablecoin payment guide and keep product type, region, payment proof, delivery timestamp, and batch context consistent.
Payment proof record before funds move
This record separates quote review from transaction evidence. Keep it with the order record; do not place wallet details or raw-code data in a public listing or a broad support thread.
Record requested product type, region, wallet-credit denomination, quantity, and quote reference. The ordering sequence is owned by How it works.
Check that the active invoice names the accepted asset, network, wallet instruction, amount, and order reference before any payment is sent. Use the Stablecoin payment guide for the payment owner.
Retain the TXID or transaction hash, amount, network, timestamp, and invoice reference. The Payment proof template provides the record fields.
Payment proof supports matching; it does not replace confirmation. Delivery follows payment confirmation and required checks. Retain the delivery timestamp, approved recipient, and batch ID under the One-time delivery note.
Payment record mistakes
- Do not reduce this to a generic "PSN code" note; the useful record needs product type, region, wallet-credit denomination, quantity, and order context.
- Do not keep the decision only in a chat thread. A buyer-side record should connect quote, payment proof, delivery, batch ID, and any claim or support notes.
- Do not scale volume until the buyer can answer this question without reconstructing the order from screenshots, separate messages, or memory.
FAQ
Is a wallet screenshot enough?
A screenshot can help, but the TXID, network, amount, timestamp, and quote are more useful for matching payment.
Why does network matter?
Sending the right asset on the wrong network can delay or prevent order matching.
Where should payment proof be stored?
Store payment proof with quote, delivery timestamp, batch ID, and support thread.
Related pages
Trust context
PSN Wholesale is operated by PSN NETWORK LTD, company number 16191822. PlayStation, PSN, and PS Plus are trademarks of Sony Interactive Entertainment Inc. PSN Wholesale is independent and is not affiliated with, endorsed by, or sponsored by Sony Interactive Entertainment Inc.
Last updated: 2026-10-18