Card Info

Information returned in the response is sourced directly from the card networks' BIN tables and updated daily. Integrating with them can remove the need to continuously update and maintain offline lists of card ranges used in pre-processing and assist in accurate routing.

The card number for which the information is requested should be submitted in the cardNumber field, allowing partial card ranges to be entered. The full PAN is not required to be sent; if fewer digits are sent, we will append 0 to make the PAN big enough. However, it is advised to enter at least the full card range (first 12 digits) or the full card number to get the best result since issuers can sub-split card products.

The API response also indicates the source from which the information of that particular card range has been pulled. Please note that the card ranges of a card scheme are, in some cases, also listed in the BIN table for other schemes that allow for cross-network processing. By default, the API response will give a result from the best possible source, also when entries have been found in multiple tables. It is possible to set the infoSource property to a particular card scheme, forcing the information to be sourced from that BIN table if present. In the API response, the card scheme to which the card range belongs is indicated in the primaryCardNetwork field. For some card ranges, this field may return unknown, which suggests that these card ranges are, for example, private label or proprietary ATM cards.

Most of the information returned by the card info API is generalized across the different supported card networks to make it easier to process card info from different card networks in the same way. However, some information is only available for a specific card network, and some fields have particular codes only defined within a specific card network. This information is available in the optional fields mastercardCardInfo, visaCardInfo, and bancontactCardInfo. The fields will only be present if the card info is sourced from the corresponding card network, as reported in the infoSource field. For example, if the infoSource field has the value Mastercard, the mastercardCardInfo field will be present. In the event of a co-branded card, we will always share the additional card info for the larger card network unless the other network is specified in the infoSource field (e.g., a co-branded Visa and Bancontact card would always return the visaCardInfo unless Bancontact was defined as the infoSource.

Next, to request details on a single card range, on the Silverflow Platform, it is possible to retrieve all the card ranges per card network by doing a GET to the /cardInfo/{network} endpoint. The network for which you are trying to retrieve that card range should be provided in {network} in the endpoint as a path parameter.

This API response will contain a large amount of information. To make such responses easier to handle, we have introduced a way to receive compressed chunked JSON on this endpoint. To use it, you need to set the header Accept-Encoding: gzip, and instead of plain JSON, you will receive a gzipped one in a chunked manner.