> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/api-reference/cards/card-object/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# The Card object

### Description

The Card object is the virtual and secured version (i.e., the tokenized version) of a card that can be used to make a payment.

The card object is created upon successfully completing the card registration process. The same actual card can be registered several times for security and privacy purposes. As a consequence, for a single real-life card, multiple Card objects can be created in the Mangopay environment.

> **Warning**
>
> **Caution – Card validation within 24 hours**
>
> A successful transaction (preauthorization, pay-in, or recurring) or card validation within 24 hours of the card registration is required to validate a card. Otherwise, the card becomes invalid and a new card registration will be necessary.

### Attributes

### Schema (`ViewACardResponse`)

```yaml
components:
  schemas:
    Validity:
      type: string
      description: >-
        **Returned values:** `UNKNOWN`, `VALID`, `INVALID`


        Whether the card is valid or not.

        - `UNKNOWN` – No payment or card validation has been processed, so the
        validity of the card remains unknown.

        - `VALID` – The first payment or card validation using the card was
        processed successfully within 24 hours of the initial card registration.

        - `INVALID` – The first payment or card validation using the card was
        attempted and failed, or the status of the corresponding card
        registration was `CREATED` for more than 24 hours.

        Once a card is set to `INVALID`, it cannot be set back to `VALID`. A new
        card registration will be necessary to make a payment.
      title: Validity
    Id:
      type: string
      description: >-
        Max length: 128 characters (see [data
        formats](/api-reference/overview/data-formats) for details)


        The unique identifier of the object.
      title: Id
    Tag:
      type: string
      description: >-
        Max. length: 255 characters


        Custom data that you can add to this object, such as unique identifiers
        in your system. To store multiple values, you can serialize them into a
        single string, for example a JSON object:
        `"{\"id_1\":AB123,\"id_2\":DE456}"`.
      title: Tag
    CreationDate:
      type: integer
      description: Unix timestamp (UTC) of the date and time the object was created.
      title: CreationDate
    ViewACardResponse:
      type: object
      properties:
        ExpirationDate:
          type: string
          description: |-
            Format: “MMYY”

            The expiration date of the card.
        Alias:
          type: string
          description: The card number, partially obfuscated.
        CardType:
          type: string
          description: >-
            **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.
        CardProvider:
          type: string
          description: >-
            **Allowed values:** `CB`, `VISA`, `MASTERCARD`, `AMEX`, `MAESTRO`,
            `BCMC`, `JCB`, `DISCOVER`


            The provider of the card.
        Country:
          type: string
          description: >-
            Format: ISO-3166-1 alpha-3 three-letter country code (e.g., “FRA”)


            The country of the card (which is the same as the country of the
            issuer).
        Product:
          type: string
          description: The product type of the card.
        BankCode:
          type: string
          description: The name of the card issuing bank.
        Active:
          type: boolean
          description: >-
            Whether the card is active or not. Setting this parameter to `false`
            is irreversible and should be done once the pay-in is successful.
        Currency:
          type: string
          description: >-
            **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.
        Validity:
          $ref: '#/components/schemas/Validity'
        UserId:
          type: string
          description: >-
            The unique identifier of the User (natural or legal) who owns the
            bank account.
        Id:
          $ref: '#/components/schemas/Id'
        Tag:
          $ref: '#/components/schemas/Tag'
        CreationDate:
          $ref: '#/components/schemas/CreationDate'
        Fingerprint:
          type: string
          description: >-
            The unique representation of the card number. This string can be
            used to track the card behavior while keeping the card information
            confidential.
        CardHolderName:
          type: string
          description: >-
            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.
      title: ViewACardResponse
```

### Related resources

#### [How to](/guides/payment-methods/card/direct/how-to)

Learn how to process a card payment

#### [Guide](/guides/payment-methods/card)

Learn about card registration and processing

#### [Testing](/testing/payment-methods)

Learn more about testing all payment methods

#### [Checkout SDK](/sdks/checkout)

Simplify card registration with Checkout SDK