US Address for PlayStation Store Testing

Generate a US address whose city, state and ZIP code genuinely agree — the pairing address forms and card AVS checks actually compare — for testing the address and billing fields of a storefront, companion app or checkout you are building alongside PlayStation Store.

Updated

Switches to that country's generator page.

Viola S. Hammes

2998 Upton Gateway
Lafayette, LA 70503
United States

Fictional test data — not a real person

Personal

SexFemale
SSN978-16-XXXXFormat only — never issued, safe for testing.
Geo coordinates30.22304, -92.07423

Phone

Phone337-555-0120
Country codeUS

Birthday

BirthdayMarch 21, 1953
Age72 years old
Tropical zodiacAries

Online

Email addressvhammes79@jourrapide.com
UsernameViolaHam754
Password2osoP76EaF
Websitedefinitive-carnival.name
Browser user agentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

Finance

Credit card typeJCB
Card number3566002020360828Sandbox test number — non-chargeable.
CVV2340
Expires02/28
CurrencyUSD

Physical

Height5' 7" (171 cm)
Weight188.1 pounds (85.3 kg)
Blood typeO-
Hair colorLight brown
Eye colorHazel

Tracking numbers

UPS tracking1Z 971 119 20 6340 835 9

Other

Favorite colorteal
Vehicle2016 Renault Camaro
License plateNI55VYT
GUIDd698e3cf-29d2-4d78-9565-9069e0afd66d

This is randomly generated fictional data for software testing, QA, and privacy. It does not describe a real person. Any resemblance to a real individual is coincidental.

Start where a documented workflow exists, which here is your payment gateway rather than Sony. Adyen's AVS documentation names the exact billing fields a card check requires: country as an ISO 3166-1 alpha-2 code, city, street, houseNumberOrName and postalCode, capped at five digits for the United States, with stateOrProvince conditionally required for US and Canadian shoppers. It then enumerates the outcomes — code 7 is “Both postal code and address match”, code 1 “Address matches, but the postal code does not match”, code 2 neither. Stripe exposes the same result in the card object's checks — address_line1_check and address_postal_code_check, each pass, fail, unavailable or unchecked. Between them that is a harness you can drive in a test environment today. This page supplies the fixtures that go into it.

Sony publishes nothing comparable. The developer entry point at playstation.com/en-us/develop redirects to partners.playstation.net, which serves no public field schemas, no validation rules and no sandbox address guidance, so anyone describing PlayStation Store's internal address checks in detail is guessing. What is public is consumer support and the PSN Terms of Service, and on one point those are unusually clear: residence is tied to the payment instrument rather than to typed text. The Terms state that your “country/area of residence may be verified by your credit or debit card number and may be rejected if the information does not match”, and that once an account exists “you will not be able to change the country or region code associated with your account”. So this page is not about a PlayStation account. It is about software you are building yourself.

What makes a US address hard to fabricate is that it is not four independent fields. The five-digit ZIP is geographically structured — the first three digits identify a USPS sectional center facility, the last two a delivery area inside it — so a ZIP implies a state and a set of cities. That holds in all but a handful of border cases: 42223 serves Fort Campbell on both the Kentucky and Tennessee sides, and 06390, Fishers Island, is in New York under Connecticut's 063 prefix. A validator treating the rule as absolute wrongly rejects those real addresses. Put 90210 beside New York and any lookup rejects the pair; five arbitrary digits fail harder, matching nothing. USPS Publication 28, Postal Addressing Standards, sets the bar: a complete address carries “all the address elements necessary to allow an exact match with the current Postal Service ZIP+4 and City State files”.

Where Sony is specific is its own physical-goods storefront, and those rules make a serviceable test matrix for any US checkout. direct.playstation.com documents that “your billing address and shipping address should be from the same country/region as your direct.playstation.com country/region”, that “orders can't be shipped to PO boxes”, and that “orders can't be shipped to U.S. territories, or to addresses outside the United States”. The territory rule is the one address forms most often get wrong: Puerto Rico, Guam and the US Virgin Islands carry ordinary five-digit ZIPs and standard two-letter codes, so they clear a format check and must then be caught by a business rule. Sony's card-troubleshooting page adds a character-set constraint — replace special characters with “the nearest letter from the basic 26-letter Latin alphabet”, avoiding asterisks, hyphens, apostrophes and slashes — worth exercising against your own storage and normalization.

This generator covers the fifty states and the District of Columbia. Each record pairs a real city with a postal code USPS actually attributes to that city, drawn from the GeoNames US postal-code dataset rather than composed from a prefix drawn from the codes USPS actually issues for it, alongside a NANPA area code for the same region and a randomized street name and house number — so the address is region-consistent while pointing at no real occupant. Be equally clear about its edges. It emits five-digit ZIPs only, with no ZIP+4 extension, and it has no mode for producing territory addresses, PO boxes, over-length values or deliberately malformed input; those fixtures you still write by hand. For a real purchase or delivery, or anywhere accuracy is legally required, use your own details.

How the generator helps with PlayStation Store address and checkout testing: City, state and ZIP that genuinely agree — the pairing a real postal lookup checks; Postal codes selected from the real list USPS attributes to each city, not a prefix drawn from the codes USPS actually issues for it; Real NANPA area code for the same region, so the phone field agrees with the address; Randomized street name and house number, so the address matches no actual residence; Pin any of the fifty states, the District of Columbia, or a specific city, so state-keyed and city-keyed branches of your own checkout logic run against a known jurisdiction; Bulk export to CSV, JSON or SQL, and the JSON API additionally accepts a seed so a fixture can be committed and replayed exactly.

What a generated identity gives you for PlayStation Store address and checkout testing

FieldFormatWhy it's safe
NameLocale-aware first + lastRandomly combined; describes no real person
AddressReal city + valid ZIP, random house #Never resolves to a real residence
PhoneValid national formatUS uses the 555-0100…0199 fiction range
Emailname@example-style domainFormat-valid placeholder, not a live inbox
National IDCountry-labeled, masked placeholderNot a real local-format identifier
Credit cardLuhn-validSandbox test BIN — non-chargeable

Every field is fictional and safe to use for PlayStation Store address and checkout testing — it describes no real person and cannot collide with a real identifier.

Frequently asked questions

Why does an address form reject an address that looks correct?+

Usually because the fields disagree with one another, rather than because any one of them is malformed. A US ZIP is geographically structured — its first three digits map to a USPS sectional center facility — so in all but a handful of border cases it implies a single state, and a ZIP sitting beside the wrong state fails a lookup even though both values look fine alone. Arbitrary five-digit numbers fail harder still, matching no record at all. Worth testing the exceptions too: 42223 covers Fort Campbell across the Kentucky–Tennessee line, and 06390 is a New York ZIP under Connecticut's 063 prefix, so a validator hard-coding one state per prefix rejects real addresses.

What does AVS actually compare?+

The billing address you submit is compared against the address the card issuer holds on file, and the score covers the street line and the postal code specifically. Adyen returns a single code — 7 for “Both postal code and address match”, 1 for “Address matches, but the postal code does not match”, 2 for neither — and Stripe exposes address_line1_check and address_postal_code_check, each pass, fail, unavailable or unchecked. City and state are submitted with the request but do not appear in the score. What a merchant does with a partial match is its own decision.

Does Sony document how PlayStation Store validates an address?+

Not publicly. The developer entry point redirects to partners.playstation.net, which publishes no field schemas and no validation rules, so any specific claim about Sony's internal address checks is unverifiable. What is public is consumer support and the PSN Terms of Service: residence may be verified by the card number; an account's country or region cannot be changed after creation; on direct.playstation.com billing and shipping addresses must share a country, and PO boxes and US territories are not shipped to; and special characters in an address should be replaced with basic Latin letters. Treat everything else as unknown and test against your own stack.

Can I use this to change my PlayStation account's region, or to get a price, trial or promotion I'm not entitled to?+

No. Using generated data to change a real account's region, or to obtain a trial, promotion, price or regional catalogue you are not entitled to, is against that service's terms, and it is not what this data is for. Nor would it work: a fictional address identifies nobody and authorizes nothing, Sony states that an account's country/region cannot be changed after it is created, and the PSN Terms tie residence to the card number rather than to typed text. This page exists for testing address and billing fields in software you are building.

Which address edge cases are worth testing in a US checkout?+

Four catch most bugs, and you write all four by hand — this generator does not produce them. A ZIP that does not belong to its state, which a real lookup rejects, plus its mirror image: a genuine cross-border ZIP such as 42223, which a naive validator wrongly rejects. A US territory — Puerto Rico, Guam, the US Virgin Islands — which has a valid five-digit ZIP and a two-letter code but is out of scope for direct.playstation.com shipping. A PO box, which that storefront refuses outright. And a secondary unit designator such as APT, STE or UNIT that has to survive being split, stored and reassembled.

Are these addresses real?+

The city is real and the ZIP is one USPS genuinely attributes to that city, but the street name and house number are randomized, so the full address matches no actual residence. It is built to satisfy a validator, not to receive anything. Never use it for shipping, billing, KYC, or anywhere a real address is required — including any real purchase on a real storefront.

Other use cases

Popular generators

Free validation tools

Sources

  1. ISO 3166 — Codes for country names and subdivisionsISO
  2. ITU-T E.164 — International telephone numbering planITU
  3. Universal Postal Union — Addressing and postal code standardsUniversal Postal Union

We use cookies for analytics and ads to keep this generator free. See our Privacy Policy.