---
title: "Create combo card (deprecated)"
method: POST
path: "/wallet/v1/relationship"
tags: ["Cards"]
deprecated: true
---

# Create combo card (deprecated)

`POST /wallet/v1/relationship`

> **Deprecated.**

Associates a customer's debit and credit accounts to create a combination card with both debit and credit payment capabilities that can be used as one embossed card.
It is recommended you create a combination card using card modes as this endpoint will soon be deprecated. For more information, refer to the [mode documentation](https://developers.pismo.io/pismo-docs/docs/cards-overview-1#create-a-combination-card-with-card-modes) in the Cards management guide.
**Note:** This endpoint takes an account token - an access token encoded with a Pismo account ID.

## Headers

- `x-idempotency-key` string

## Request body

- RelationshipBody — Accounts relationship for combo cards enablement
  - `credit` object, required — Credit object
    - `program_id` integer, required — Program ID (First program ID)
    - `account_id` integer, required — Credit account ID
    - `customer_id` integer, required — Pismo customer ID.
    - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
    - `embossing_custom_field` string — For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal. You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser—what to send, what values to send, what format to send, what size to send for each value, and so on.
    - `template_id` string — Template ID. Templates are used to implement the BIN override feature. For more information, refer to the [BIN override](https://developers.pismo.io/pismo-docs/docs/bin-override-feature) guide.
  - `debit` object, required — Object containing the debit side in the relationship
    - `program_id` integer, required — Program ID (second program ID)
    - `customer_id` integer, required — Debit program customer ID
    - `account_id` integer, required — Debit program account ID
    - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
    - `embossing_custom_field` string — For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal. You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser—what to send, what values to send, what format to send, what size to send for each value, and so on.
    - `template_id` string — Template ID. Templates are used to implement the BIN override feature. For more information, refer to the [BIN override](https://developers.pismo.io/pismo-docs/docs/bin-override-feature) guide.

## Response `201`

Cards relationship information

- RelationshipResponse
  - `cardID` integer, required — Primary card ID
  - `cards` object[], required
    - `cardID` integer, required — Secondary card ID
    - `roleType` 'SECONDARY_DEBIT' | 'SECONDARY_CREDIT' | 'SECONDARY_LOC' | 'SECONDARY_INSTALLMENT' | 'SECONDARY_PREPAID', required — Card role type: * `SECONDARY_DEBIT`—Debit card * `SECONDARY_CREDIT`—Credit card * `SECONDARY_LOC`—Secondary/fallback funding source * `SECONDARY_INSTALLMENT`—Installment plan * `SECONDARY_PREPAID`—Prepaid card
    - `isFallback` boolean, required — Is this the fallback card? Only one card can be a fallback card.

## Other responses

- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `409` — You already have a card with this type and name active
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)