PlayStation Gift Card Regional Differences: Country and Catalog Map
A field-level comparison for wholesale buyers building a catalog across countries that may share currencies but do not share an automatic redemption scope.
Quick answer
The controlling difference is the PlayStation account country or store country. Currency and face value describe the product but do not replace that country field. This matters most where several lanes share USD or EUR.
Compatibility hierarchy
| Signal | Use | Can it authorize a sale? |
|---|---|---|
| PlayStation account country | Primary customer compatibility field | Only when it matches the voucher country |
| Voucher store country | Primary product scope field | Only when explicit and matching |
| Currency | Catalog and finance label | No; USD and EUR span separate lanes |
| Residence, IP, language | Possible customer context | No |
Country and currency lane map
This comparison records the compatibility decision for each lane. Exact available and sold-out face values belong to the current denomination catalog, so one owner remains responsible for value-level status.
| Account-country lane | Currency | Catalog decision | Value handoff |
|---|---|---|---|
| United Kingdom | GBP | Keep GB separate from every EUR and USD product. | Use the GB row in the denomination catalog. |
| United States / Saudi Arabia / UAE | USD | Maintain US, KSA, and UAE as three distinct country lanes. | Select values only after the country lane is known. |
| France / Germany / Netherlands | EUR | Maintain FR, DE, and NL separately; a generic EUR row is not a country match. | Use the country-specific EUR row, never a pooled value list. |
| Hungary | HUF | Route Hungary accounts to HU/HUF inventory, not generic EU stock. | Use the dated HU status row and the dedicated Hungary guide. |
| India | INR | Keep recipient account-country eligibility in the issue workflow. | Use the dated IN status row before campaign publication. |
| Poland | PLN | Keep PL/PLN independent even though Poland is in the EU. | Use the Poland value row, not an EUR substitute. |
| Turkey | TRY | Reconfirm current commercial terms without changing the TR boundary. | Use the current TR value row for each quote. |
| Ukraine | UAH | Keep UA compatibility and availability as separate checks. | Use the current UA value row before committing quantity. |
Where shared currency creates risk
| Case | Wrong shortcut | Correct catalog action |
|---|---|---|
| US / KSA / UAE | Pool all USD codes | Maintain three account-country SKUs even when face values overlap. |
| France / Germany / Netherlands | Pool all EUR codes | Preserve FR, DE, or NL in supplier, storefront, and support records. |
| Generic EUR row | Assign it to the customer's preferred country | Hold until the exact store-country scope is documented. |
| Poland in the EU | Move PLN stock into generic EU inventory | Keep PL / PLN as its own lane. |
Multi-country procurement workflow
- Collect account-country demand separately for every intended market.
- Map one country, currency, value, and internal SKU to each line.
- Filter the mix against the dated available/sold-out snapshot.
- Show country compatibility before payment or reward selection.
- Receive codes through the one-time encrypted note and reconcile them into country-specific quarantine.
- Release only approved rows; keep held and sold-out values outside available stock.
Regional page ownership
This page compares the differences across lanes. It does not replace the pre-purchase region-lock checklist or the country-specific operating guides in the regional hub. Use the child page when the job is to procure one market; use this map when the job is to design a multi-country catalog.
Commercial and source boundaries
Alpha PSN commercial boundary
The standard minimum is 20 cards and settlement is USDT only. After payment confirmation, codes are sent in a password-protected one-time encrypted note. The customer email address is the password, and the note can be opened once. Public catalog pages do not publish unit prices.