---
title: "View a Card Registration"
method: GET
path: "/v2.01/{ClientId}/cardregistrations/{CardRegistrationId}"
tags: ["cardRegistrations"]
---

# View a Card Registration

`GET /v2.01/{ClientId}/cardregistrations/{CardRegistrationId}`

View a Card Registration

## Path parameters

- `ClientId` string, required
- `CardRegistrationId` string, required

## Headers

- `Authorization` string, required

## Response `200`

Success

- CardRegistrationResponse
  - `Id` string — The unique identifier of the Card Registration object.
  - `Tag` string — 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.
  - `CreationDate` integer — Unix timestamp (UTC) of the date and time the object was created.
  - `UserId` string — The unique identifier of the user the card belongs to.
  - `AccessKey` string — The secure value to use when tokenizing the card via the dedicated endpoint.
  - `PreregistrationData` string — The secure value to identify the registration when tokenizing the card via the dedicated endpoint.
  - `RegistrationData` string — 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.
  - `CardId` string — The unique identifier of the Card object, which is returned after updating the Card Registration object with the `RegistrationData`.
  - `CardType` string — **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.
  - `CardRegistrationURL` string — 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.
  - `ResultCode` string — 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.
  - `ResultMessage` string — The explanation of the result code.
  - `Currency` string — **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.
  - `Status` string — **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`.

---

[API](https://skmtc.dev/mangopay/apis/api-reference.md) · [All operations](https://skmtc.dev/mangopay/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mangopay/api-reference/revisions/fafbd0c69654/schema)