paymentMethodMetadata

Look up metadata for a payment method

Changed on
<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>

post/v2.01/{ClientId}/payment-methods/metadata

Request

  • Base URL
    https://api.sandbox.mangopay.com
  • URL
    https://api.sandbox.mangopay.com/v2.01/{ClientId}/payment-methods/metadata
  • Auth
    HTTP bearer

Path parameters

ClientIdstring required

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

Request body

Typestring required

Allowed values: BIN, GOOGLE_PAY

The type of metadata.

Binstring

Format: 6 or 8 digits

Required if the Type is BIN. The bank identification number (BIN).

Tokenstring

Required if the Type is GOOGLE_PAY.

The tokenized payment data provided by the third-party payment method.

Response

Success

Typestring

The type of metadata.

Binstring

Format: 6 or 8 digits

The bank identification number (BIN).

IssuerCountryCodestring

Format: Two-letter country code (ISO 3166-1 alpha-2 format)

The country where the card was issued.

IssuingBankstring

The name of the card issuer.

TokenFormatstring

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.

Changes

    • warning

      deleted the header request parameter Authorization

    • info

      the endpoint scheme security oauth2 was added to the API

    • info

      api operation id lookup_payment_method_metadata removed and replaced with paymentMethodMetadata_lookup_payment_method_metadata