Buvei
API ReferenceCards

Query Card BINs

List the BIN ranges available to your project.

GET/open-api/v1/card-bins

Use this endpoint to discover which BINs you can issue from. The response tells you per-BIN whether mobile, email, PIN, billing address, or a KYC cardholder are required when issuing.

Response

cardBinIdstring

Card BIN unique identifier — pass this as cardBinId to POST /cards.

binstring

Card BIN range (first 6 digits).

brandstring

Card brand — "VISA", "MASTERCARD", ...

issuingCountrystring

ISO 3166-1 alpha-2 country code where the card is issued.

currencystring

ISO 4217 currency code. Card currency is determined by the BIN and cannot be overridden at issuance time.

mobileboolean

When true, issuing a card with this BIN requires mobilePrefix and mobile.

emailboolean

When true, issuing a card with this BIN requires email.

supportPinboolean

When true, you may set a 4-digit PIN at issuance and update it later via POST /cards/{cardId}/pin.

requireKycCardholderboolean

When true, issuing requires a cardholderId from an APPROVED KYC cardholder. See KYC flow.

Request
curl -X GET https://api.buvei.com/open-api/v1/card-bins \
  -H "X-API-Key: key_your_api_key" \
  -H "X-Timestamp: 1640995200000" \
  -H "X-Nonce: a1b2c3d4e5f6g7h8" \
  -H "X-Signature: <signature>"
Response
{
  "code": 0,
  "message": "SUCCESS",
  "data": [
    {
      "cardBinId": "v_123456",
      "bin": "555543",
      "brand": "VISA",
      "issuingCountry": "US",
      "currency": "USD",
      "mobile": false,
      "email": false,
      "supportPin": false,
      "requireKycCardholder": true
    }
  ]
}

BIN metadata is safe to cache for 24 hours. Refresh daily, or when a POST /cards returns 400 with "cardBinId" in the errors map.

On this page

Response