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

# The Payment Method Metadata object

### Description

The Payment Method Metadata object allows you to obtain additional information about a specific payment method used for a transaction.

The following inputs are available, indicated by the `Type`:

* `BIN` – The bank identification number (BIN) of a card. The BIN is available in the `CardInfo` parameter returned on transactions with a registered card: direct card pay-in, recurring pay-in (CIT), preauthorization, extended preauthorization, card validation. It is also available in the [Card](/api-reference/cards/card-object) object in the first 6 digits of the `Alias` parameter.
* `GOOGLE_PAY` – The temporary token returned by the Google Pay API, as submitted in the `PaymentData` parameter in the Google Pay pay-in.

### Attributes

### Schema (`LookUpMetadataForAPaymentMethodResponse`)

```yaml
components:
  schemas:
    LookUpMetadataForAPaymentMethodResponseBinDataItems:
      type: object
      properties:
        CardType:
          type: string
          description: |-
            **Returned values:** `CREDIT`, `DEBIT`, `CHARGE CARD`

            The type of the card.
        CommercialIndicator:
          type: string
          description: |-
            **Returned values:** `PERSONAL`, `COMMERCIAL`

            Whether the card is held in a personal or commercial capacity.
        SubType:
          type: string
          description: >-
            The subtype of the card product. Examples include: `CLASSIC`,
            `GOLD`, `PLATINUM`, `PREPAID`, etc.


            **Note:** The possible returned values are numerous and liable to
            evolve over time.
        Brand:
          type: string
          description: >-
            The card brand. Examples include: `AMERICAN EXPRESS`, `DISCOVER`,
            `JCB`, `MASTERCARD`, `VISA`, etc.


            **Note:** The possible returned values are numerous and liable to
            evolve over time.
      title: LookUpMetadataForAPaymentMethodResponseBinDataItems
    LookUpMetadataForAPaymentMethodResponse:
      type: object
      properties:
        Type:
          type: string
          description: The type of metadata.
        Bin:
          type: string
          description: |-
            Format: 6 or 8 digits

            The bank identification number (BIN).
        IssuerCountryCode:
          type: string
          description: >-
            Format: Two-letter country code ([ISO 3166-1 alpha-2
            format](/api-reference/overview/data-formats))


            The country where the card was issued.
        IssuingBank:
          type: string
          description: The name of the card issuer.
        BinData:
          type: array
          items:
            $ref: >-
              #/components/schemas/LookUpMetadataForAPaymentMethodResponseBinDataItems
          description: >-
            Additional data about the card based on the BIN. In the case of <a
            href="/guides/payment-methods/card/co-branded">co-branded card
            products</a>, two objects are returned.
        TokenFormat:
          type: string
          description: >-
            **Returned values:** `PAN_ONLY`, `CRYPTOGRAM_3DS`


            In the case of Google Pay, the format of the `Token`.

            - `PAN_ONLY` – The card is registered in the Google account and
            requires 3DS authentication.

            - `CRYPTOGRAM_3DS` – The card is enrolled in the customer's Google
            Wallet and authentication is handled by the Android device.
      title: LookUpMetadataForAPaymentMethodResponse
```