---
title: "Look up metadata for a payment method"
method: POST
path: "/v2.01/{ClientId}/payment-methods/metadata"
tags: ["paymentMethodMetadata"]
---

# Look up metadata for a payment method

`POST /v2.01/{ClientId}/payment-methods/metadata`

<Check>
**Best practice – For BIN lookup, use an 8-digit version if available**

An 8-digit BIN provides the most detailed and accurate data for card identification and assessment, and is becoming the industry standard. The 6-digit version continues to be used but provides less granular classification that may be ambiguous if 8-digit sub-ranges have been introduced by the issuer.

A transaction's `CardInfo.BIN` property returns the 8-digit BIN if its available. In the Card object, the `Alias` only ever reveals the first 6 digits – the 8-digit version should be preferred. 
</Check>

## Path parameters

- `ClientId` string, required

## Headers

- `Authorization` string, required

## Request body

- LookUpMetadataForAPaymentMethodRequest
  - `Type` string, required — **Allowed values:** `BIN`, `GOOGLE_PAY` The type of metadata.
  - `Bin` string — Format: 6 or 8 digits Required if the `Type` is `BIN`. The bank identification number (BIN).
  - `Token` string — Required if the `Type` is `GOOGLE_PAY`. The tokenized payment data provided by the third-party payment method.

## Response `200`

Success

- LookUpMetadataForAPaymentMethodResponse
  - `Type` string — The type of metadata.
  - `Bin` string — Format: 6 or 8 digits The bank identification number (BIN).
  - `IssuerCountryCode` string — Format: Two-letter country code ([ISO 3166-1 alpha-2 format](/api-reference/overview/data-formats)) The country where the card was issued.
  - `IssuingBank` string — The name of the card issuer.
  - `BinData` LookUpMetadataForAPaymentMethodResponseBinDataItems[] — 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.
    - `CardType` string — **Returned values:** `CREDIT`, `DEBIT`, `CHARGE CARD` The type of the card.
    - `CommercialIndicator` string — **Returned values:** `PERSONAL`, `COMMERCIAL` Whether the card is held in a personal or commercial capacity.
    - `SubType` string — 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` string — 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.
  - `TokenFormat` string — **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.

---

[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)