Card Info

Information returned in the response is sourced directly from the BIN tables of the card networks, and are updated on a daily basis. Integrating with the 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 and also allows for entry of partial card ranges. The full PAN is not required to be sent, if less digits are sent then we will append 0 to make the PAN big enough. However, to get the best result it is advised to enter at least the full card range (first 12 digits) or otherwise the full card number since issuers are allowed to sub-split card products.

The API response also indicates the source from where the information of that particular card range has been pulled from. Please note, that card ranges of a card scheme are in some cases also listed in the BIN table of other schemes to 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 which will force 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 indicates that these are 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 specific codes that are 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 specified as the infoSource.

Next to request details on a singel card range, on the Silverflow Platform it is also 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 ranges should be provided in {network} in the endpoint as a path parameter.

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