What the public register confirms
Companies House lists PSN NETWORK LTD as an active private limited company, company number 16191822, incorporated on 17 January 2025 with a registered office at 16 Ling Road, Victoria Docks, London, E16 4AL.
Evidence created during an order
Email identity
The magic link opens a workspace tied to the request email. Paid delivery is sent to that same identity.
Server-built quote
Region, denomination, quantity, stock, base discount, personal discount, and volume tier are recalculated on the server.
Exact invoice
The invoice names one USDT network, one wallet address, one exact amount, and a limited payment window.
Blockchain record
The transaction hash, amount, token contract, recipient, block, and confirmation state can be checked independently.
One-time delivery
The paid order email receives a password-protected note. After opening, the code view expires after three minutes.
Claim packet
Order ID, batch, delivery timestamp, region, customer error and support thread create a reviewable record.
Payment boundary
What the payment poller accepts
The browser cannot mark an order paid. Payment status comes from the server-side poller after it finds the expected token transfer on the selected network.
Two networks
USDT TRC20 and USDT BEP20 only. A transfer on another network is not a valid payment for the invoice.
Exact amount
The observed transfer amount must equal the invoice amount. A different amount is not automatically accepted.
Limited window
The standard invoice window is 20 minutes, with controlled late-payment checking for reconciliation.
Server confirmation
Client-side JavaScript displays status but does not decide it. The order state is written by the server.
Buyer records to retain
Before payment
Quote ID, region, product type, denomination, quantity, unit price, discount lines, network, wallet address, exact amount and expiry.
After payment
Transaction hash, token contract, recipient, transferred amount, block/confirmation status and payment confirmation time.
After delivery
Order ID, delivery email, delivery timestamp, SKU/batch labels and the internal inventory record created from the one-time note.
For a claim
Affected SKU/batch, customer account region, exact error, timestamp, screenshot and the listing language shown to the customer.
Claim review boundaries
Claims are reviewed through [email protected]. Evidence supports investigation but does not create an automatic refund or replacement. Outcomes depend on the order terms, batch records, region compatibility, code status and the facts available for the specific claim.
Do not email an entire unused batch.
Send the order ID and only the affected code or batch reference first. Protect unrelated inventory until support requests additional evidence.
Read the claim process or open the dispute evidence template.
Independent and official sources
Supplier verification sequence
- 1Verify the legal operator
Match the company name, number and registered office against Companies House.
- 2Inspect current inventory
Use the public availability page, then confirm the selected SKU inside the workspace.
- 3Start at the minimum
Use 15 cards to test payment matching, delivery, inventory import and support before increasing exposure.
- 4Preserve the record
Keep the quote, TXID, delivery timestamp and batch mapping together.
Verify first, then place a controlled order
Check the public catalog and company record before requesting a magic link. The minimum payable order is 15 cards.
Last materially reviewed: 2026-07-13