v2
latestOpenAPI 3.1.02026-07-262279731.3 MBCards
Deactivate or edit a Card
<Warning icon="fa-regular fa-triangle-exclamation"> **Warning – Implement card deactivation**Because card information cannot be kept without the end user's approval, you should implement a way to deactivate the end user’s card systematically when relevant.
</Warning>
Deactivate or edit a Card
This call serves one of two purposes:
- Setting the card as inactive, and thereby disabling it from being used again. This action is irreversible but doesn’t prevent the card being registered again with POST Create a Card Registration.
- Adding the CardHolderName to an existing Card object. The CardHolderName cannot be modified once added to a Card object. It can also be done during registration with PUT Update a Card Registration, in which case attempting to edit it with this endpoint returns an error.
put/v2.01/{ClientId}/cards/{CardId}
Path parameters
ClientIdstring required
Platform's API account identifier, associated with the API key.
CardIdstring required
The unique identifier of the Card object, which is returned after updating the Card Registration object with the RegistrationData.
Headers
Authorizationstring required
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.
Request body
Response
Success