Cancel the nominated card
POST/v1/cards/:cardId/cancel
Required States: ACTIVE
This endpoint will execute when the following conditions are satisfied:
- Party is in a relevant state
ACTIVE - Party has a valid account that is
ACTIVE - Party has a relationship to the nominated card instance.
- The card is in the
PROVISIONED,ACTIVEorLOCKEDstate
This operation cancels, or requests a replacement, for the nominated card instance based on the reason provided for cancellation.
Each of the following reasons will result in a different outcome:
- CANCEL: The card will be cancelled and the status will be updated to
CANCELED - LOST: The card will be cancelled and a replacement card will be requested. The current card instance will transition to
CANCELED - STOLEN: The card will be cancelled and a replacement card will be requested. The current card instance will transition to
CANCELED - DAMAGED: The card will remain
ACTIVEand a replacement card will be requested. Depending on the type of card, it may beACTIVE(VIRTUAL or PHYSICAL_AND_VIRTUAL cards) orNEW(PHYSICAL cards)
The response will return status information about the cancelled card instance.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 500
- 503
OK
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 card (CRT004005) or Card not found (CAR004001) or Account not found (CAR004004)
Invalid card state for this operation (CAR009001)
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)