Skip to main content

Release 03.11.2025

Changelog​

New Endpoint: Retrieve Available BINs​

The new Retrieve Available BINs endpoint returns a list of BIN categories with detailed information about each BIN configuration, including:

  • Category identifiers and types (e.g., travel, corporate expenses)
  • BIN numbers and card networks
  • Supported digital wallet tokenizations (Apple Pay, Google Pay)
  • Tags for categorization and feature indication (e.g., 3DS requirements, use case optimization)
  • Issuer country information
  • Availability status

Configure BIN Restrictions​

You can now control which BINs are available for card issuance at the account level using the new accountBinDirections field:

  • When creating a new account, specify which BIN categories and specific BINs should be available.
  • When updating an account, modify the BIN configuration. Changes only affect newly issued cards; existing cards remain unchanged.

The accountBinDirections field accepts an array of BIN category configurations. For each category, you can:

  • Specify the category identifier (binCategoryId)
  • Optionally list specific BIN identifiers (cardBinIds) from that category

Enhanced BIN Information in Account Responses​

The following endpoints now return enriched BIN information in the binList field:

New fields:

  • categoryIds: Array of BIN category identifiers that define the intended use case (e.g., travel, corporate expenses)
  • tags: Array of tags for categorization and feature indication (e.g., apple_pay, travel, no_3ds)

Updated fields:

  • bin: Now nullable to support category-based configurations
  • issuerCountry: Now nullable
  • cardNetwork: Now nullable
  • cardTokenizations: Documentation corrected to reflect the actual enum values "Apple pay" and "Google pay" (previously documented incorrectly as "apple_pay" and "google_pay")

Issue Cards by BIN Category​

When calling Issue a New Card, you can now specify a BIN category.

  • New field binCategoryId: Specify the intended use case for the card (e.g., travel, corporate expenses). The category determines which BIN will be used for card issuance.
  • New field currency: Explicitly set the card currency (ISO 4217 format).
  • Updated cardProviderBinId: Now optional (nullable).
  • Updated limits: Now required. You must specify at least one spending limit when creating a card.