How PSN Wholesale ordering works

Request secure email access and choose PlayStation Store wallet-credit SKUs for the exact account regions. The basket must reach $500 USD at quoted product prices after the configured discount, contain 15–1,000 cards in total and meet each SKU minimum. Follow the active invoice; delivery follows payment confirmation and required checks.

B2B order requirements

$500 USD · 15–1,000 cards
USDT or native USDC
One-time note after payment confirmation
Region-specific catalog records
Each selected SKU minimum applies
State lifecycle

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.

StateEvidence on the recordMove forward or hold
Access requestedBusiness email and request timestamp.Move forward only through the email-bound magic link; a request is not a quote or stock reservation.
Workspace openedSigned session and delivery email shown in the workspace.Hold if the delivery identity is wrong or the link is expired.
Quote calculatedWallet-code SKU, account region, denomination, quantity, SKU minimum, quoted price after the configured discount, basket value and quote version.Recalculate after any basket change; the browser preview is not a payable instruction.
Invoice waiting for paymentOrder ID, selected asset and network, recipient, exact amount, and active invoice expiry.Hold on any network, amount, destination, or expiry mismatch and create a current instruction instead of reusing an old one.
Payment confirmedMatching 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 sealedPaid 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 destroyedOpen 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 reviewQuote, 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

1

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.

2

Build the quote

Orders start at $500 USD at quoted product prices, after the configured discount. Orders must contain 15–1,000 cards in total and meet each selected SKU's minimum. Eligible regions and denominations can be combined in one basket. Confirm current availability and fulfillment conditions in the private workspace before payment.

3

Pay the active invoice

Choose USDT on TRC20 (TRON) or BEP20 (BNB Smart Chain), and native USDC on Solana or Base. Use only the active invoice's asset, network, recipient, exact amount and payment window; review the USDT payment guide before choosing a network.

4

One-time delivery

After payment confirmation and required operational checks, the agreed delivery route is sent to the order email. Save the codes during the one-time note viewing window; no instant or same-day delivery is guaranteed.

5

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.

StepBuyer should saveWhy it matters
quote access requestTarget region, product type, volume, business channel, and contact owner.Prevents a quote from being interpreted as a generic global offer.
Quote approvalExact account region, wallet denomination, quantity, SKU minimum, quoted product total after the configured discount, quote validity and delivery expectation.Keeps purchasing, catalog, and support aligned on the same assumptions.
PaymentAsset, network, wallet instruction, amount, quote reference, and TXID.Allows finance to match payment to the exact wholesale order.
DeliveryDelivery email, one-time note access, delivery timestamp, batch ID, recipient, and access notes.Protects code access and makes later claim review possible.
Post-delivery reviewSell-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

Region confusion

Pause if customers or support agents cannot distinguish account region, card region, and listing currency.

Weak payment trail

Pause if the TXID, quote reference, and delivered batch cannot be tied to the same order.

Unclear claim evidence

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 invoicing, QBv2 checks the $500 USD quoted product total after the configured discount, 15–1,000 total cards and each selected SKU minimum. No extra personal or volume-tier discount is implied. A selectable catalog entry is not a stock reservation; confirm fulfillment conditions before paying the active invoice.

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

Wallet-credit denominations and selection status vary by exact account region. Confirm the current SKU, price and fulfillment conditions through secure access.

PlayStation gift cards

Record account region, catalog region, currency, denomination, quantity, and SKU ID. Use the dated Availability snapshot as a dated account-region reference, not live stock or prices.

PS Plus boundary

QBv2 supplies PlayStation Store wallet-credit codes, not direct PS Plus subscription codes. Whether wallet funds can pay for a subscription depends on the account, region and Sony store requirements.

Ready to get started?

Request secure access to confirm an eligible $500 USD wallet-code basket, SKU minimums and current fulfillment conditions.

Calculate your potential profit

Use the free ROI calculator for a buyer-entered scenario based on the current quote and your own costs. Its illustrative defaults are not market data, an available order or a promised return.

TRY ROI calculator

Last materially reviewed: 2026-10-18

Fulfillment handoff

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.

Access

Submit the request, open the email-bound magic link, and confirm that the workspace shows the intended delivery email before building the basket.

Invoice

Choose a configured USDT or native USDC option, then follow only the active invoice asset, network, recipient, exact amount and payment window. Keep the transaction reference.

Delivery

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.