Get Card Designs

The Get Card Designs endpoint retrieves a list of available card design templates that can be applied to payment cards. Partners can use this endpoint to present customers with visual personalization options when issuing new physical or virtual cards. Each design entry includes metadata such as the card network, intent, and preview icon URLs.

Endpoint

GET /api/paymentCards/cardDesigns

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

Call this endpoint before issuing a new payment card to allow the customer to choose a design that reflects their personal style or brand. It is also useful when building card issuance flows in partner applications to populate a design selection UI. You can filter results by cardProductId or financialAccountId to return only designs applicable to a specific product or account context.

Query Parameters

Response

200 OK

Returns an array of card design objects.

[
  {
    "cardProfileSetId": "cps_abc123xyz",
    "name": "Netevia Classic Blue",
    "intent": "PHYSICAL",
    "network": "VISA",
    "isDefault": true,
    "description": "A professional blue card design suitable for business accounts.",
    "icons": [
      "https://cdn.netevia.com/designs/classic-blue-front.png",
      "https://cdn.netevia.com/designs/classic-blue-back.png"
    ]
  },
  {
    "cardProfileSetId": "cps_def456uvw",
    "name": "Netevia Dark Edition",
    "intent": "VIRTUAL",
    "network": "MASTERCARD",
    "isDefault": false,
    "description": "A sleek dark-themed design for virtual card use.",
    "icons": [
      "https://cdn.netevia.com/designs/dark-edition-front.png"
    ]
  }
]

Error Codes

Common Mistakes

• Passing an invalid or non-existent cardProductId may return an empty array rather than a 404; verify the product ID before using it in a card issuance flow.
• Omitting the Authorization header will result in a 401 error even though the endpoint may appear to be informational — authentication is always required.
• Not filtering by financialAccountId when issuing a card tied to a specific account may return designs incompatible with that account type.

Related Endpoints

• POST /api/paymentCards — Issue a new payment card using a selected card design
• GET /api/paymentCards — List all payment cards for a customer
• GET /api/paymentCards/{paymentCardId} — Retrieve details of a specific payment card

Example

curl -X GET "https://api.banking.netevia.dev/api/paymentCards/cardDesigns?cardProductId=cps_abc123xyz" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"