Skip to main content
POST
/
user
/
routable-cards
/
create
Issue a routable card to a user
curl --request POST \
  --url https://api.sdev.banking.ingopayments.tech/api/v4/user/routable-cards/create \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '
{
  "api_key": "YOUR_API_KEY",
  "user_id": "user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef",
  "card_type": "virtual"
}
'
{
  "status": "success",
  "message": "operation completed",
  "data": {
    "items": [
      {
        "id": "rcrd-9a117b23-cc90-d1ef-8f3a-2b1c0e444f2d",
        "card_type": "physical",
        "last_four": "4242",
        "status": "unactivated",
        "user_id": "user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef",
        "business_id": "buss-2ef94c60-5a11-4d72-a3c1-5be7fab0123e",
        "created_at": "2026-04-16T12:34:56.000Z"
      }
    ],
    "pagination": {
      "page": 1,
      "per_page": 25,
      "total": 100,
      "sort": "created_at:desc",
      "search": "jane"
    }
  }
}

Documentation Index

Fetch the complete documentation index at: https://developers.ingopayments.com/llms.txt

Use this file to discover all available pages before exploring further.

Card Issuance is currently In Development and not yet available for integration. This endpoint is documented for advance planning only and will not respond until the capability is enabled for your program.

Authorizations

api_key
string
header
required

Program API key identifying your integration. Pass as the api_key HTTP header (preferred) or as an api_key field in the JSON request body. Required on every request in addition to the HMAC Authorization header.

Body

application/json
user_id
string
required

Identifier of the target user. Required when the endpoint operates on a specific user.

Example:

"user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef"

card_type
enum<string>
required

Requested card form factor.

Available options:
physical,
virtual
api_key
string

Program API key. Accepted either in the api_key HTTP header or as this body field.

idempotent_key
string

Client-supplied idempotency token. Submitting the same key twice returns the first response rather than creating a duplicate transaction.

shipping_address
object

Shipping address object. Required for physical card issuance.

virtual_card_id
string

Existing virtual card id to materialise as the physical card (when issuing physical after virtual).

Response

Success.

status
enum<string>
required
Available options:
success
message
string
required
Example:

"operation completed"

data
object

Endpoint-specific payload; shape varies per operation.