POST
/
v4
/
MC_VIRTUAL
/
customer
/
{customerId}
/
account
/
{accountId}
/
{cardRole}
curl --request POST \
  --url https://integration-api-cat2./%7B{environment}%7D.ext.%7B{realm}%7D.cia.enfuce.com/card/v4/MC_VIRTUAL/customer/{customerId}/account/{accountId}/{cardRole} \
  --header 'Content-Type: application/json' \
  --data '{
  "expiration": {
    "year": 2019,
    "month": 1
  },
  "segment": "SEGMENT_A",
  "pinStatus": "D",
  "digitalLayoutCode": "abc123abc",
  "scheduledClosing": {
    "type": "TIMEBASED",
    "time": "2099-12-31T03:00:00.000Z"
  },
  "additionalValues": [
    {
      "key": "<string>",
      "value": "<string>"
    }
  ],
  "encryptedData": "<string>",
  "embossing": {
    "additionalField1": "<string>",
    "additionalField2": "<string>",
    "additionalField3": "<string>",
    "additionalField4": "<string>",
    "additionalField5": "<string>",
    "companyName": "Enfuce Financial Services",
    "externalLayoutCode": "BlueCard",
    "firstName": "Monica",
    "lastName": "Liikamaa",
    "manufacturer": "FACTORY_X",
    "physical": true
  },
  "productCode": "MC_CARD_2, VISA_CARD1, VISA_VIRTUAL_3, MC_VIRTUAL_2, VISA_CARD"
}'
{
  "description": "<string>",
  "id": "<string>"
}

Path Parameters

​
customerId
string
required

The customer id of which customer you want to create the card on

​
accountId
string
required

The account id that the card should be connected to

​
cardRole
enum<string>
required

A role needs to be provided for the connection to the account. Role is one way to categorize between primary and supplementary card holders. Role MAIN will always create a card to have same account holder and card holder. For a supplementary card there is a possibility to differ between account and card holder.

Available options:
MAIN,
SUPPLEMENTARY

Query Parameters

​
auditUser
string
required

The audit user to log the request

Body

application/json

The fields that you want to apply to your newly created card, these values will override the predefined template values

The body is of type object.

Response

201
application/json

Successful creation of the product

The response is of type object.