---
title: "Available Card Configs"
method: GET
path: "/cards/available-cards"
tags: ["Cards"]
---

# Available Card Configs

`GET /cards/available-cards`

Returns a list of card configurations which are available for the API user to issue for the given organization. Pliant describes cards with a so called `cardConfig`. The card config describes all relevant aspects of a card, like the look of the card or the type of the card. Card configs can be used to [issue](./issue-card) new cards and they then replace the old `type` field of the card issuing.

## Query parameters

- `organizationId` string, uuid, required

## Response `200`

Ok

- object
  - `cardConfigs` object[], required — A list of card configs which are available for the API user to issue for the given organization.
    - `id` string, uuid — The unique identifier of the card config.
    - `accountGroup` string — The account group this card config belongs to.
    - `cardConfig` string — The technical name of the card config. This can be used as a parameter for the [card issuing](./issue-card) endpoint.
    - `canBeIssued` boolean — Indicates whether new cards can currently be issued using this card config.
    - `name` string — The business name of the card config.
    - `description` string, nullable — A description of the card config.
    - `type` 'VIRTUAL' | 'PHYSICAL' — Determines if the card is virtual or physical.
    - `country` string — The country-availability of the card config in ISO 3166-1 alpha-2 notation.
    - `maxTransactions` integer, nullable — The maximum number of transactions which are allowed on cards using this card config. If this is `null`, there is no limit. If this is `1`, the card can only be used once etc.
    - `cardDesigns` object[] — A list of card designs which are available for this specific card config.
      - `cardDesignId` string, uuid — The unique identifier of the card design.
      - `cardDesignLogoName` string, nullable — The name of the card design.
    - `fundingType` 'CHARGE' | 'LOAD_BASED_ACCRUING' | 'LOAD_BASED_NON_ACCRUING' | 'BALANCE_BASED', nullable — * `CHARGE` - normal (non-benefit) credit card * `LOAD_BASED_ACCRUING` - benefit card where money not spent is transferred to the next month * `LOAD_BASED_NON_ACCRUING` - benefit card where money not spent is lost end of month * `BALANCE_BASED` - benefit card with a standing balance that persists across months and is spent down until depleted (no monthly reset).
    - `loadBasedSettings` object, nullable — Defines the load configuration for this card config. Only filled for cards with `LOAD_BASED_ACCRUING` or `LOAD_BASED_NON_ACCRUING` funding type.
      - `fixedFrequency` 'MONTHLY' | 'QUARTERLY' | 'ANNUAL' — The frequency at which the card is loaded. * `MONTHLY` - loaded once per month * `QUARTERLY` - loaded once per quarter * `ANNUAL` - loaded once per year
      - `fixedAmount` object — The fixed amount loaded onto the card at each load interval.
        - `value` number — The value of the monetary amount, converted to minor units of the currency. For instance 1.00 EUR is 100 cents, thus the value here is `100`. See our [guides](/docs/monetary-values) for more details about how to handle monetary amounts.
        - `currency` string — The currency of the monetary amount in ISO 4217 format, for example `EUR` for Euro or `USD` for US Dollar.
    - `clickToPaySupported` boolean — Whether this card configuration supports Visa Click to Pay enrollment. Only Visa cards (excluding Travel Purchasing Cards) support Click to Pay.
    - `expiryPeriodsInMonths` integer[] — Defines available expiry periods for this card config in months.
    - `cardAccounts` string[] — The set of card account IDs associated with this card config.
    - `cardControls` object — A summary of the card control settings available for this card config, indicating which controls are enabled, editable, and required.
      - `categories` object — Card controls based on merchant category. Keys are category control types (`MCC`, `CATEGORY`).
      - `merchants` object — Card controls based on specific merchants. Keys are merchant control types (`MATCH_TERM`, `MID`, `PMDB_ID`).
      - `dates` object — Card controls based on date restrictions. Keys are date control types (`FIXED`, `WEEKLY`, `MONTHLY`, `YEARLY`).
      - `times` object — Card controls based on time-of-day restrictions. Keys are time control types (`TIMERANGE`).
      - `locations` object — Card controls based on geographic location. Keys are location control types (`POSTAL_CODE`, `REGION`).
      - `acceptanceMethods` object — Card controls based on payment acceptance method. Keys are acceptance method types (`ONLINE`, `MOBILE_WALLET`, `MANUAL_ENTRY`, `CONTACTLESS`, `CHIP_DIP`, `NOT_AVAILABLE`, `MAGNETIC_STRIPE`, `OTHER`).
      - `countries` AdditionalProperties — unresolved $ref
    - `copilotAllowed` boolean — Indicates whether the Pliant Copilot feature is available for cards using this card config.
    - `transactionCountLimitSupported` boolean — Indicates whether a transaction count limit can be configured on cards using this card config.
    - `validityPeriodEnabled` boolean — Indicates whether a custom validity period can be set on cards using this card config.
    - `premiumProductType` string, nullable — The premium product type associated with this card config, if applicable.
    - `network` string — The card network (e.g. `VISA`, `MASTERCARD`) for this card config.

## Other responses

- `400` — unresolved $ref
- `401` — unresolved $ref
- `403` — unresolved $ref
- `404` — unresolved $ref
- `429` — unresolved $ref
- `500` — unresolved $ref

---

[API](https://skmtc.dev/getpliant/apis/pliant-customer-api.md) · [All operations](https://skmtc.dev/getpliant/apis/pliant-customer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getpliant/pliant-customer-api/revisions/f3f589cfa718/schema)