v2

latestOpenAPI 3.1.02026-07-262279731.3 MB
cardRegistrations

Update a Card Registration

Update a Card Registration

This call is used to add the string acquired from the tokenization to the Card Registration object in the parameter RegistrationData, thereby validating the registration.

As a result, the Card object is created and the corresponding CardId returned.

Platforms should also send the cardholder’s name as it appears on the payment card. The CardHolderName parameter is sent on this call but not returned in the response; it is added to the Card object.

put/v2.01/{ClientId}/cardregistrations/{CardRegistrationId}

Path parameters

ClientIdstring required

Platform's API account identifier, associated with the API key.

CardRegistrationIdstring required

The unique identifier of the Card Registration object.

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

RegistrationDatastring required

The string returned by the tokenization server on the <a href="/api-reference/card-registrations/tokenize-card">POST Tokenize the card</a> endpoint.

CardHolderNamestring

Min. length: 2 characters; max. length: 45 characters passed to card network, 255 accepted by the API

The cardholder's name shown on the payment card. This value is passed to the card network for use in transaction risk analysis. The value should only contain unmarked alphabetic characters (A-Z, a-z), hyphens (-), apostrophes (‘), and spaces. Letters with diacritics (e.g. É, Ü, ẞ), honorifics (e.g. MRS.) and other special characters are not recommended. The CardHolderName is not returned in the Card Registration object; it is added to the Card object.

Response

Success

Idstring

The unique identifier of the Card Registration object.

Tagstring

Custom data that can be added to this object. In the case of the Card Registration, this parameter can be used to facilitate the link between the User object and its equivalent on your platform for instance. This value will be inherited by the Card object Tag parameter and will not be editable.

CreationDateinteger

Unix timestamp (UTC) of the date and time the object was created.

UserIdstring

The unique identifier of the user the card belongs to.

AccessKeystring

The secure value to use when tokenizing the card via the dedicated endpoint.

PreregistrationDatastring

The secure value to identify the registration when tokenizing the card via the dedicated endpoint.

RegistrationDatastring

The string returned by the tokenization server, which must be sent in full as the RegistrationData on the <a href="/api-reference/card-registrations/update-card-registration">PUT Update a Card Registration</a> endpoint to create the Card object.

CardIdstring

The unique identifier of the Card object, which is returned after updating the Card Registration object with the RegistrationData.

CardTypestring

Returned values: CB_VISA_MASTERCARD, AMEX, MAESTRO, BCMC

Default value: CB_VISA_MASTERCARD

The type of the card. If not supplied, the default value will be taken into account.

CardRegistrationURLstring

The URL to make the card tokenization call.

Caution: This variable URL is specific to each card registration. You must rely on the returned URL in full (host, path, and queries) and not hardcode any part of it.

ResultCodestring

The code indicating the result of the operation. This information is mostly used to <a href="/errors/codes">handle errors</a> or for filtering purposes.

ResultMessagestring

The explanation of the result code.

Currencystring

Returned values: The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings).

The currency of the card.

Statusstring

Returned values: CREATED, VALIDATED, ERROR

The status of the card registration:

  • CREATED – The card registration has been created, but no RegistrationData has been entered yet and the CardId value is null.
  • VALIDATED – The card registration has been successfully updated with the RegistrationData from the tokenization server.
  • ERROR – The card registration couldn’t be updated with the RegistrationData and no CardId was generated. For more information, refer to the ResultCode (<a href="/errors/codes/105206">105206</a>, <a href="/errors/codes/105299">105299</a>) and ResultMessage.