Countries, Provinces, and States
Keep account, billing, and shipping address regions consistent for invoices, tax, delivery, and reporting.
Keep your location data accurate and standardised with Countries, Provinces, and States. MyPetParlor App stores countries, Canadian provinces, and U.S. states as ISO alpha-2 codes, which improves communication with payment gateways and tax services and reduces address validation errors.
Definition#
Countries, Provinces, and States is the system that converts country, province, and state values to ISO alpha-2 codes inside the account, billing, invoice, and shipping address records. These codes are the format used when MyPetParlor App communicates with payment gateways and other third parties, so location data stays in a universally recognised shape.
Key Benefits#
- Standardisation — Using ISO alpha-2 codes for countries, provinces, and states gives every record the same recognised format and reduces the chance of typos.
- Improved communication — Standard codes are sent to payment gateways and tax services, so address data transfers cleanly between systems.
- Reduced errors — Sending capitalised ISO alpha-2 codes minimises address validation and tax-calculation errors at gateway level.
- Comprehensive coverage — All recognised countries, all Canadian provinces, and all U.S. states are supported.
Key Details#
How It Works#
- When sending location data to MyPetParlor App — for example, when creating an account, updating an address, or processing a transaction — send countries, provinces, and states as their capitalised ISO alpha-2 codes. For example, send
USfor the United States,CAfor Canada,ZAfor South Africa,ONfor Ontario, orNYfor New York. - If MyPetParlor App can't match the value to a recognised code, the raw input is stored as-is. For example, sending
New Yorkinstead ofNYresults inNew Yorkbeing stored on the address record. - Where the value matches a known code, the standard code is what gets passed to payment gateways and tax services for transactions, validation, and reporting.
Use uppercase ISO alpha-2 codes wherever your integration captures address data. Avoid lowercase or full names when an ISO code is available.
Countries#
MyPetParlor App follows the ISO 3166-1 alpha-2 standard for country codes. Common codes used by accounts on the platform include:
| Code | Country |
|---|---|
| ZA | South Africa |
| US | United States |
| CA | Canada |
| GB | United Kingdom |
| AU | Australia |
| NZ | New Zealand |
| IE | Ireland |
| DE | Germany |
| FR | France |
| NL | Netherlands |
The full list covers every recognised country. Use the official ISO 3166-1 alpha-2 reference for any code not shown above.
Canadian Provinces#
MyPetParlor App follows the ISO 3166-2:CA codes for Canadian provinces and territories.
| Code | Province / Territory |
|---|---|
| AB | Alberta |
| BC | British Columbia |
| MB | Manitoba |
| NB | New Brunswick |
| NL | Newfoundland and Labrador |
| NS | Nova Scotia |
| NT | Northwest Territories |
| NU | Nunavut |
| ON | Ontario |
| PE | Prince Edward Island |
| QC | Quebec |
| SK | Saskatchewan |
| YT | Yukon |
U.S. States#
MyPetParlor App follows the ISO 3166-2:US codes for U.S. states, federal district, and Armed Forces designations.
| Code | State / Territory |
|---|---|
| AL | Alabama |
| AK | Alaska |
| AZ | Arizona |
| AR | Arkansas |
| CA | California |
| CO | Colorado |
| CT | Connecticut |
| DE | Delaware |
| DC | District of Columbia |
| FL | Florida |
| GA | Georgia |
| HI | Hawaii |
| ID | Idaho |
| IL | Illinois |
| IN | Indiana |
| IA | Iowa |
| KS | Kansas |
| KY | Kentucky |
| LA | Louisiana |
| ME | Maine |
| MD | Maryland |
| MA | Massachusetts |
| MI | Michigan |
| MN | Minnesota |
| MS | Mississippi |
| MO | Missouri |
| MT | Montana |
| NE | Nebraska |
| NV | Nevada |
| NH | New Hampshire |
| NJ | New Jersey |
| NM | New Mexico |
| NY | New York |
| NC | North Carolina |
| ND | North Dakota |
| OH | Ohio |
| OK | Oklahoma |
| OR | Oregon |
| PA | Pennsylvania |
| RI | Rhode Island |
| SC | South Carolina |
| SD | South Dakota |
| TN | Tennessee |
| TX | Texas |
| UT | Utah |
| VT | Vermont |
| VA | Virginia |
| WA | Washington |
| WV | West Virginia |
| WI | Wisconsin |
| WY | Wyoming |
| AS | American Samoa |
| GU | Guam |
| MP | Northern Mariana Islands |
| PR | Puerto Rico |
| VI | U.S. Virgin Islands |
| AA | Armed Forces Americas |
| AE | Armed Forces (Europe / etc.) |
| AP | Armed Forces Pacific |
Address Region Fields#
These location fields appear across the account billing domain.
| Field | Description |
|---|---|
| Country | The country associated with the account, billing, or shipping address. |
| Region or province | The province, state, or regional subdivision inside the country. |
| Town or city | The city or town for the address. |
| Suburb | A local suburb or neighbourhood. |
| Postal code | The postal or ZIP code for the address. |
| Location | Coordinate data, when captured by the address workflow. |
Where These Fields Appear#
| Record | Region usage |
|---|---|
| Account address | The main address stored against the account. |
| Billing address | The address linked to billing info or invoices. |
| Invoice address | The address snapshot shown on invoice records. |
| Shipping address | The delivery or service-destination address. |
| Business entity | The business billing entity can also have tax and display addresses. |
Why Consistency Matters#
Using ISO alpha-2 codes consistently across these records helps with:
- Correct invoice display.
- Tax and VAT calculation.
- Payment gateway verification and billing-info validation.
- Shipping and service-location communication.
- Reporting by country or region.
- Matching customers to the right business entity where location-based billing rules apply.
Recommended Formatting#
| Decision | Recommended approach |
|---|---|
| Country | Use the capitalised ISO alpha-2 code (ZA, US, GB). |
| Province / state | Use the capitalised ISO alpha-2 code where one exists (ON, NY); otherwise use the full province name. |
| Postal codes | Capture postal codes without extra words or punctuation. |
| Missing data | Leave optional fields blank instead of placeholders such as N/A, unless your tenant process requires a placeholder. |