Card creation endpoint
POST/v1/cards
Required States: ACTIVE
This endpoint creates a card instance if the following conditions are satisfied:
- Party is in a relevant state
ACTIVE - Party has a valid account that is
ACTIVE - Party has not reached the maximum number of cards allowed for the product
- The selected card type is allowed for the product
- The account product is mapped to the requesting client/brand
This method creates a card instance against the nominated account. The account must be in ACTIVE state and is subject to restrictions imposed by the underlying card provider and product configuration.
Card Types:
- PHYSICAL - A physical card will be created and sent to the party.
- VIRTUAL - A virtual card will be created and made available for the party to use.
- PHYSICAL_AND_VIRTUAL - A physical card will be created and sent to the party, and a virtual card will be created and made available for the party to use.
Dependent on the card type, the card will be created in the following states:
- PHYSICAL: The card will be created in a
NEWstate, and be visible in the card listing after it has been submitted to the provider for provisioning. - VIRTUAL: The card will be created in a
ACTIVEstate - PHYSICAL_AND_VIRTUAL: The card will be created in a
ACTIVEstate
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 500
- 503
Created
Schema validation failed (GEN000000)
Missing or invalid authentication token (GEN001002) or Role unauthorized (GEN001006) or Tenant context could not be resolved (AUT001001)
External application access denied (AUT003001) or Party not in required status (PAR003001)
No open binding for the account (CRT004005) or Card not found (CAR004001) or Account not found (CAR004004) or Product mapping not found (CAR004005)
Internal server error (CAR100001) or Core banking error (CAR100002) or General internal server error (GEN100000) or Service error (GEN100001)
All connector targets are currently unhealthy (CRT103001)