Live B2B order facts
Know the evidence required to leave each order state
The quote flow does not treat an inquiry, a browser preview, an invoice, a detected transfer, and a paid order as the same event. Use the lifecycle below to keep purchasing, finance, delivery, and support on one record.
| State | Evidence on the record | Move forward or hold |
|---|---|---|
| Access requested | Business email and request timestamp. | Move forward only through the email-bound magic link; a request is not a quote or stock reservation. |
| Workspace opened | Signed session and delivery email shown in the workspace. | Hold if the delivery identity is wrong or the link is expired. |
| Quote calculated | SKU, region, denomination or duration, quantity, discount inputs, current stock check, and quote version. | Recalculate after any basket change; the browser preview is not a payable instruction. |
| Invoice waiting for payment | Order ID, exact USDT amount, selected TRC20 or BEP20 network, destination, and invoice expiry. | Hold on any network, amount, destination, or expiry mismatch and create a current instruction instead of reusing an old one. |
| Payment confirmed | Matching TXID, network, exact amount, confirmation record, and paid timestamp. | Only a matched payment moves the order to paid; a detected unmatched transfer does not release delivery. |
| Delivery note sealed | Paid order ID, delivery email, note creation timestamp, and batch reference. | The note stays tied to the paid order and email until the authorized recipient opens it. |
| Delivery note opened or destroyed | Open timestamp and the buyer's controlled inventory handoff record. | Save the codes during the one-time viewing window; the note cannot be treated as reusable storage. |
| Claim or reorder review | Quote, payment, delivery, listing, error, account-region, and outcome evidence. | This is a buyer/support review, not an automatic runtime status. Close with a recorded outcome before scaling or reordering. |
Order flow from magic link to delivery
Open secure access
Submit your business email and open the magic link. The quote builder loads with that email as the signed-in delivery address.
Build the quote
Select available SKUs, denominations, quantities, and USDT network. The builder blocks out-of-stock items and orders below the 15-card minimum.
Pay exact USDT
Create a TRC20 or BEP20 invoice and send the exact amount shown. Different amounts are not accepted for automatic payment confirmation; review the USDT payment guide before choosing a network.
One-time delivery
After payment confirmation, the delivery email receives a secure note that can be opened once to reveal the purchased codes.
Keep records for support
Save the quote, exact invoice, TXID, delivery timestamp, batch reference, and customer error evidence. Those records define what can be reviewed if a claim occurs.
Buyer-side order record
The PSN Wholesale order flow works best when the buyer keeps a single record from quote access request to post-delivery review. This is especially important for resellers, marketplaces, and distributors that need finance and support teams to reconcile the same order later.
| Step | Buyer should save | Why it matters |
|---|---|---|
| quote access request | Target region, product type, volume, business channel, and contact owner. | Prevents a quote from being interpreted as a generic global offer. |
| Quote approval | Region, denomination or duration, quantity, price, quote validity, MOQ, and delivery expectation. | Keeps purchasing, catalog, and support aligned on the same assumptions. |
| Payment | Asset, network, wallet instruction, amount, quote reference, and TXID. | Allows finance to match payment to the exact wholesale order. |
| Delivery | Delivery email, one-time note access, delivery timestamp, batch ID, recipient, and access notes. | Protects code access and makes later claim review possible. |
| Post-delivery review | Sell-through notes, support tickets, region mismatch count, and reorder decision. | Turns the first order into evidence for whether to scale volume. |
When to pause before the next order
Pause if customers or support agents cannot distinguish account region, card region, and listing currency.
Pause if the TXID, quote reference, and delivered batch cannot be tied to the same order.
Pause if support does not know which screenshots, error text, account-region note, or delivery record are required for review.
Server controls and verification boundaries
Before an invoice is created, the server recalculates stock, quantity limits, base and personal discounts, volume tier, and price. The payment poller then requires the selected network and exact invoice amount.
Where separate batch-verification evidence is available, it may support a claim review. The self-service flow does not promise an external activation lookup for every code and does not remove region, listing, storage, or customer-account risk.
Delivery & Security
delivery-note records
Paid codes are delivered through delivery-note records tied to the order email.
delivery note access record
You receive a one-time delivery note tied to the order email; open it once and save the codes immediately.
Payment-gated release
The delivery note is created only for an order recorded as paid. No public page promises a fixed fulfillment time.
Available Denominations
Denominations and availability vary by region. The quote builder shows the current orderable SKUs before invoice creation.
PlayStation Gift Cards
Record account region, catalog region, currency, denomination, quantity, and SKU ID. Use the dated availability snapshot for current public rows.
PS Plus Subscriptions
Record the exact tier, duration, account region, quantity, and SKU ID only when that subscription product is confirmed in the current quote. Gift-card availability does not prove PS Plus availability.
Turn this research into buyer controls
Use these links to move from research into supplier checks, order records, and the request path.
Buyer answers hub
Use the buyer answers for concise checks on legal identity, B2B scope, regions, verification limits, and Sony independence.
Procurement checklist
Turn research into supplier identity checks, quote review, payment proof, and delivery records.
API Verification answer
Explain verification as a supplier-side checking process without replacing buyer records.
company facts hub
Use the entity reference page for supplier identity, B2B scope, verification path, and trademark boundary.
Ready to get started?
Open secure quote access and build a live order.
Calculate Your Potential Profit
Use our free ROI calculator to see your potential profits based on your order volume and chosen regions. Get instant projections with current market data.
Try ROI CalculatorLast materially reviewed: 2026-09-01
Plan the delivery record before you send payment
The order is bound to the email used for access. That address receives the workspace link and the paid-order delivery message, so it should belong to the team that can store the order record and retrieve the codes.
Submit the request, open the email-bound magic link, and confirm that the workspace shows the intended delivery email before building the basket.
Choose TRC20 or BEP20, pay the exact USDT amount during the invoice window, and keep the transaction reference.
After payment confirmation and fulfillment, the email links to a one-time note protected by the delivery email. Opening starts the short viewing window.
Continue the check: review one-time delivery, review USDT payment, store the order evidence.