Cardholder Region Restrictions
Residential country, nationality, and proof-of-address (POA) requirements for cardholders.
Before creating a cardholder or requesting a card, check whether the cardholder's actual country of residence is eligible. Then use the cardholder's nationality to determine whether proof of address is required. Each card product retains its own information and KYC requirements.
💡 Quick summary
- Check
individual.address.countryagainst the Red and Yellow residence lists. Residents of these countries are rejected. - If the residence is eligible, check
nationality. A Red-group nationality requires valid POA. - Product KYC requirements always apply, regardless of region.
1. Residential Address Country​
Card issuance is REJECTED for residents of any country in the Red or Yellow group below. Providing proof of address does not override this restriction.
Use the cardholder's actual residential country (individual.address.country) and keep it consistent with their real residence information. The following do not replace the actual residence:
- Mobile phone dialing code (
country_code)
Mainland China (CN), Hong Kong (HK), and Macao (MO) are evaluated separately.
| Group | Country codes (2 letter ISO 3166-1) |
|---|---|
| Red | BD, BY, CN, CU, IN, ID, IR, IQ, KP, LK, MA, NP, RU, SY, TR, UA, US |
| Yellow | DZ, BT, CA, EG, ET, HK, IL, JO, MV, MX, NZ, OM, PK, PR, SA, TN, VE |
Note: Absence from this table does not confirm support for a region. Country codes must be valid and the submitted information must be consistent. Contact your account manager / HashDT team to confirm eligibility for a specific region.
2. Nationality​
Only after the residence is confirmed eligible does the cardholder's nationality determine the POA requirement.
| Nationality group | POA requirement |
|---|---|
| Red | Both new and existing cardholders must have valid POA linked to them under the current account before requesting each new card. |
| Non-Red (including Yellow) | No additional mandatory POA requirement. The product's KYC requirements still apply. |
The Red group for nationality uses the same country codes as the Red residence list above.
3. Preparing Cardholder Information​
Note: Region and POA checks are enforced when creating a card or assigning a physical card. Creating or updating a cardholder only saves information and attachments; the country groups on this page do not by themselves reject those requests. Account permissions, platform sanctions, data validation, and update-status restrictions still apply.
Step 1: Save the required information and POA​
Complete the required cardholder information through Create Cardholder API. If the cardholder has an eligible residence and a Red-group nationality, also provide POA using these fields in identity:
| Field | Description |
|---|---|
proof_of_address | Base64-encoded POA file (PDF, PNG, JPG, JPEG, max 10 MB after decoding) |
proof_of_address_issue_date | Issue date (YYYY-MM-DD), within the last 12 months |
proof_of_address_issuing_country | 2-letter ISO 3166-1 code of the issuing country or region |
Card-issuance requests do not accept proof_of_address attachments. Submit POA through the cardholder endpoints first.
Step 2: Confirm POA is valid and readable​
When POA is required, it must:
- belong to the current account and the cardholder,
- be fully saved, and
- remain readable.
Valid saved POA can be reused for subsequent cards; you do not need to upload it again for each card. POA does not replace kyc_verification.kyc_proof.
Step 3: Request a Card after meeting KYC requirements​
After the product's KYC requirements are met, use the cardholder_id to create a card or assign a physical card. POA does not require a separate approval wait.
Uploading an attachment does not approve KYC, request a new card, or reopen a failed request.
4. Product and Resource Availability​
Passing region and POA checks does not guarantee card issuance. Product permissions, KYC, currency, card form, available funds, and issuing-resource checks still apply. Physical card assignment must also meet the requirements of the specified inventory card.
Decision Flow​
| Check | Result |
|---|---|
individual.address.country is in Red or Yellow | Rejected. POA does not override. |
Residence Eligible, nationality is in Red | Valid POA must be linked before each new card request. |
Residence Eligible, nationality is not Red | Supported No extra POA requirement. Product KYC still applies. |