> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synctera.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Card Products
> A card product is the shared configuration behind a group of cards. It defines the features, limits, and fulfillment behavior that every card issued against it inherits.
The Cards API works with two primary objects: the **card product** and the **card**. The card product comes first — you cannot issue a card without naming the product it belongs to.
A card product represents a particular card you offer to your customers, bundling together the BIN it is issued on, its physical characteristics, and the features enabled for it. For example, one card product might be "Mastercard consumer debit, physical, contactless, digital wallets enabled, no cross-border."
Your Synctera Onboarding & Implementation manager sets up your card products based on your requirements and your sponsor bank agreement. Card products are not created through the API — you read them and reference them by ID when issuing cards.
## What a card product defines
| Field | Description |
| ------------------------- | ------------------------------------------------------------------ |
| `id` | The card product ID you pass when issuing a card |
| `name` | Human-readable name, up to 40 characters |
| `card_brand` | `MASTERCARD` or `VISA` |
| `card_category` | `CONSUMER` or `COMMERCIAL` |
| `card_type` | `DEBIT`, `CREDIT`, or `PREPAID` |
| `form` | `PHYSICAL` or `VIRTUAL` |
| `bin_country` | The country of the BIN, used to evaluate cross-border transactions |
| `active` | Whether the product can still be used to issue cards |
| `start_date` / `end_date` | When the product goes live and when it is decommissioned |
| Field | Description |
| --------------------------- | ------------------------------------------------------------------------------------------ |
| `card_fulfillment_provider` | The card embosser: `ARROWEYE` or `GD` |
| `card_fulfillment_country` | Where cards are manufactured |
| `physical_card_format` | `MAGNETIC_STRIPE`, `CHIP`, `CONTACTLESS`, or `PHYSICAL_COMBO` |
| `bulk_shipping_enabled` | Whether cards on this product can ship in bulk |
| `return_address` | The return address printed on the mailing - defaults to the fulfillment provider's address |
| `package_id` | The fulfillment provider's package ID for the card carrier |
| `orientation` | Card orientation |
| `color` | Color code for dynamic card elements such as the PAN and cardholder name |
| `image` / `image_mode` | Whether a custom card image is supported and how it is handled |
Card fulfillment providers:
* `ARROWEYE` — cards are printed on demand.
* `GD` — cards are manufactured in bulk (minimum order), and then personalized on demand.
These card fulfillment providers offer different options when it comes to card material (plastic, metal, etc.). Your Synctera Onboarding & Implementation Manager will help you finalize your card design and provider setup.
| Field | Description |
| --------------------- | ------------------------------------------------- |
| `pin_issuance_policy` | `NOT_REQUIRED` (default), `REQUIRED`, or `RANDOM` |
The PIN issuance policy controls whether a physical card can be fulfilled before a PIN is set. Virtual cards do not have a PIN issuance policy.
**`NOT_REQUIRED`** — the default. The card ships without a PIN. A PIN must still be set, but the cardholder can do that after they receive the card.
**`REQUIRED`** — the card is created with `PENDING` status and the physical card is not manufactured until a PIN is set with the [Set PIN widget](/v2/docs/card-widgets-set-pin). Within a few minutes of the PIN being set, the card moves to `UNACTIVATED` and fulfillment proceeds. Subscribe to `CARD.UPDATED` to be notified.
**`RANDOM`** — the system assigns a random PIN before shipment. The card is created with `PENDING` status and moves to `UNACTIVATED` within a few minutes. Once the cardholder receives and activates the card, they can retrieve the PIN with the [Reveal PIN widget](/v2/docs/card-widgets-reveal-pin).
| Field | Description |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `cross_border_enabled` | When false, transactions are declined automatically if the merchant country differs from the BIN country. **Disabled by default.** |
| `l2l3_enabled` | Whether Level 2 and Level 3 transaction data is captured. Disabled by default. |
| `txn_enhancer` | Third-party merchant data enrichment: `MX` (default) or `NONE` |
| `afd_preauth_limit` | Override for the automated fuel dispenser preauthorization hold, in cents, up to \$1,000 |
| `digital_wallet_tokenization` | Card art and provisioning controls for Apple Pay and Google Pay |
| Field | Description |
| -------------------------- | ---------------------------------------------------------------------------------- |
| `card_limit` | Maximum number of cards per person on this product. Not applied to business cards. |
| `issue_without_kyc` | Allows issuing cards on this product without KYC — used for gift card programs |
| `unsecured_credit_enabled` | Whether unsecured credit is enabled for the product |
## List your card products
Use [List Card Products](/v2/reference/listcardproducts) to retrieve every product configured for you, with its full configuration.
```bash cURL theme={"system"}
curl --request GET \
--url "$baseurl/v2/cards/products" \
--header "Authorization: Bearer $apikey"
```
Note the `id` of the product you intend to issue against — that is the `card_product_id` you pass to [Issue a Card](/v2/reference/issuecard).
Card product configuration changes — enabling cross-border transactions, changing the fulfillment provider, adjusting the card limit — go through your Synctera representative, not the API. Check `active` before issuing: inactive products cannot be used for new cards.