Common APIs
Reference data endpoints for countries, cities, mobile codes, plus file upload and work order management.Base URL:
POST /api/v2.1/fincard/virtual/...Country/Region List
Returns all supported countries and regions with ISO codes.{} (empty body)
Response data[]:
| Field | Type | Description |
|---|---|---|
code | String | ISO 3166-1 alpha-2 (e.g. US) |
standardCode | String | ISO 3166-1 alpha-3 (e.g. USA) |
name | String | Country/region name |
Example Response
Example Response
City List
Returns cities filtered by country/region code.| Field | Type | Required | Description |
|---|---|---|---|
regionCode | String | No | ISO 3166-1 alpha-2 filter |
data[]:
| Field | Type | Description |
|---|---|---|
code | String | City code |
name | String | City name |
country | String | ISO 3166-1 alpha-2 |
Example Response
Example Response
City List v2 (Hierarchical)
Returns cities with province/state/city hierarchy (two levels).data[]:
| Field | Type | Description |
|---|---|---|
code | String | Province/state code |
name | String | Province/state name |
country | String | ISO 3166-1 alpha-2 |
countryStandardCode | String | ISO 3166-1 alpha-3 |
parentCode | String | Parent code ("0" for root) |
children[] | Array | Child cities (same structure recursively) |
Example Response
Example Response
Mobile Code List
Returns mobile area codes by region.{} (empty body)
Response data[]:
| Field | Type | Description |
|---|---|---|
code | String | Mobile code (e.g. +1) |
name | String | Region name (e.g. Canada) |
areaCode | String | ISO 3166-1 alpha-2 (e.g. CA) |
language | String | zh_CN or en_US |
enableGlobalTransfer | Boolean | Is global transfer available |
Example Response
Example Response
Upload File
Upload a file for use in cardholder KYC or work orders. Supports jpg, png, pdf formats, max 2MB.| Field | Type | Required | Description |
|---|---|---|---|
category | String | Yes | Use card |
file | File | Yes | jpg/png/pdf, max 2MB |
data:
| Field | Type | Description |
|---|---|---|
fileId | String | UUID reference for the uploaded file |
Example Response
Example Response
Use the returned
fileId when creating cardholders (B2C model requires ID document uploads).Submit Work Order
Submit a work order for card activation or support requests.| Field | Type | Required | Description |
|---|---|---|---|
merchantOrderNo | String | Yes | Client transaction ID. Length [20..40] |
title | String | Yes | Title. Length [1..255] |
target | String | Yes | Target. Length [1..255]. Card number for activation |
content | String | No | Content. Length [0..1000] |
files | List<String> | No | File IDs from upload endpoint |
tradeType | String | Yes | CARD_ACTIVE or OTHER |
data:
| Field | Type | Description |
|---|---|---|
merchantOrderNo | String | Client transaction ID |
orderNo | String | Platform transaction ID |
title | String | Title |
target | String | Target |
content | String | Content |
tradeType | String | CARD_ACTIVE / OTHER |
tradeStatus | String | wait_process / processing / success / fail |
remark | String | Remark |
createTime | Long | Millisecond timestamp |
updateTime | Long | Millisecond timestamp |
Example Response
Example Response
Work Order List
Query work orders with optional filters and pagination.| Field | Type | Required | Description |
|---|---|---|---|
merchantOrderNo | String | No | Filter by client tx ID |
orderNo | String | No | Filter by platform tx ID |
target | String | No | Filter by target |
tradeType | String | No | CARD_ACTIVE / OTHER |
tradeStatus | String | No | wait_process / processing / success / fail |
data: { total: Long, records: [...] } — records have same shape as Submit response plus description.