Create Payment Card for Authorized User

This endpoint issues a new payment card to an authorized sub-user (sub-profile) within a business customer's account. You can create a virtual card or request a physical card to be shipped by providing delivery details. The card is linked to the sub-user's associated financial account and can optionally be activated immediately upon creation.

Endpoint

POST /api/subProfiles/issuePaymentCard

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a business customer needs to provision a payment card for one of their authorized sub-profile users. This is appropriate when onboarding a new authorized user who requires spending capabilities, or when an existing sub-user needs an additional card. The issued card is tied to the sub-user's account and can be used for transactions immediately if activateOnCreate is set to true.

Request Body

Top-level fields (createpaymentcardrequest)

orderPhysicalPaymentCard object

deliveryDetails object

deliveryDetails.name object

deliveryDetails.address object

courier object

Example — Issue virtual card (activate immediately)

{
  "subProfileId": 4821,
  "paymentCardName": "Online Purchases",
  "activateOnCreate": true,
  "cardProfileSetId": "cps_8f3a21bc9d"
}

Example — Order physical card with shipping

{
  "subProfileId": 4821,
  "paymentCardName": "Corporate Card",
  "activateOnCreate": false,
  "orderPhysicalPaymentCard": {
    "deliveryDetails": {
      "name": {
        "givenName": "Jane",
        "familyName": "Smith"
      },
      "companyName": "Acme Corp",
      "address": {
        "streetAddress": "742 Evergreen Terrace",
        "extendedAddress": "Suite 100",
        "postalCode": "62704",
        "region": "IL",
        "locality": "Springfield",
        "countryCodeAlpha3": "USA"
      }
    },
    "courier": {
      "method": "UPS_NEXT_DAY"
    }
  },
  "cardProfileSetId": "cps_8f3a21bc9d"
}

Response

200 OK

financialAccount object fields

{
  "id": "pcd_a1b2c3d4e5f6",
  "formFactor": "VIRTUAL",
  "bin": "411111",
  "last4": "4242",
  "status": "ACTIVE",
  "financialAccountId": "fa_9z8y7x6w5v",
  "isMainCard": false,
  "network": "VISA",
  "isEmailNotify": true,
  "isPushNotify": false,
  "financialAccount": {
    "id": "fa_9z8y7x6w5v",
    "last4": "XXXXXXXXXX",
    "name": "Business Checking",
    "type": "CHECKING",
    "accountStatus": "ACTIVE",
    "routingNumber": "021000021",
    "clientName": "Acme Corp"
  },
  "cardName": "Online Purchases",
  "expirationDate": "2028-06-30T23:59:59Z"
}

Error Codes

Common Mistakes

• Providing orderPhysicalPaymentCard without the required deliveryDetails object causes a 400 validation error.
• Using a 2-letter country code (e.g., US) instead of the required ISO 3166-1 alpha-3 code (e.g., USA) for countryCodeAlpha3 will fail validation.
• Setting activateOnCreate: true for a physical card does not mean the card is usable immediately — the card must still be physically received and may require a separate activation step depending on the card profile configuration.
• The region field must be exactly 2 characters (US state code). Passing a full state name (e.g., California) will fail.
• Omitting subProfileId may result in the card not being linked to the intended authorized user; confirm the sub-profile ID before calling this endpoint.
• Using an expired or soon-to-expire Bearer token (lifetime is 10 minutes) will return a 401; refresh the token via POST /api/auth/refresh before calling this endpoint.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer authentication token
• POST /api/auth/refresh — Refresh an existing Bearer token
• GET /api/subProfiles — List all sub-profiles for the authenticated business customer
• POST /api/subProfiles — Create a new authorized sub-profile user
• GET /api/subProfiles/{subProfileId}/paymentCards — List all payment cards for a specific sub-profile
• PUT /api/subProfiles/paymentCard/{cardId} — Update or manage an existing sub-profile payment card

Example

Issue a virtual card for an authorized user:

curl -X POST https://api.banking.netevia.dev/api/subProfiles/issuePaymentCard \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "subProfileId": 4821,
    "paymentCardName": "Online Purchases",
    "activateOnCreate": true,
    "cardProfileSetId": "cps_8f3a21bc9d"
  }'

Order a physical card with next-day shipping:

curl -X POST https://api.banking.netevia.dev/api/subProfiles/issuePaymentCard \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "subProfileId": 4821,
    "paymentCardName": "Corporate Card",
    "activateOnCreate": false,
    "orderPhysicalPaymentCard": {
      "deliveryDetails": {
        "name": {
          "givenName": "Jane",
          "familyName": "Smith"
        },
        "companyName": "Acme Corp",
        "address": {
          "streetAddress": "742 Evergreen Terrace",
          "extendedAddress": "Suite 100",
          "postalCode": "62704",
          "region": "IL",
          "locality": "Springfield",
          "countryCodeAlpha3": "USA"
        }
      },
      "courier": {
        "method": "UPS_NEXT_DAY"
      }
    },
    "cardProfileSetId": "cps_8f3a21bc9d"
  }'