List Payment Card Types

The /api/enums/paymentCardTypes endpoint returns a comprehensive list of payment card types supported by the Netevia platform. Each entry includes a name, numeric identifier, description, and grouping information. This data is intended for front-end integration, enabling applications to present users with a valid set of card type options during payment flows.

Endpoint

GET /api/enums/paymentCardTypes

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 building payment forms or card management screens that require a dropdown or selection list of supported card types. Call it during application initialization or when dynamically populating card type options so that the values shown to users always reflect what the platform currently supports. This is especially useful when creating or updating payment card records where a valid card type identifier is required.

Response

200 OK

Returns an array of enum description objects. Each object represents one supported payment card type.

[
  {
    "name": "VISA",
    "id": 1,
    "description": "Visa",
    "groupName": "Credit",
    "endpoints": [
      "/api/cards/physical",
      "/api/cards/virtual"
    ]
  },
  {
    "name": "MASTERCARD",
    "id": 2,
    "description": "Mastercard",
    "groupName": "Credit",
    "endpoints": [
      "/api/cards/physical",
      "/api/cards/virtual"
    ]
  },
  {
    "name": "AMEX",
    "id": 3,
    "description": "American Express",
    "groupName": "Credit",
    "endpoints": [
      "/api/cards/physical"
    ]
  }
]

Error Codes

Common Mistakes

• Hardcoding card type IDs in your integration instead of fetching them dynamically — card type IDs may change; always retrieve the list at runtime or cache it with a short TTL.
• Using the name field as the identifier in downstream API calls — always use the id field when a card type value is required by other endpoints.
• Skipping this endpoint and guessing type values — submitting an unsupported card type ID will result in a 400 error on card creation or update calls.

Related Endpoints

• GET /api/enums/cardStatuses — Returns valid card status values used in card management operations
• POST /api/cards/physical — Create a physical payment card; requires a valid card type
• POST /api/cards/virtual — Create a virtual payment card; requires a valid card type

Example

curl -X GET https://api.banking.netevia.dev/api/enums/paymentCardTypes \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"