Visa BIN Attribute Sharing Service

JSON implementation - Full BIN List API: This API allows entities to consume the full BIN data extract by paginating through the BIN range dataset. The client application will need to make multiple calls to this API to consume the entire dataset. The API response is tied to the entities access level.

File stream implementation: This implementaion allows entities to receive the full BIN data in file stream format. For optimal performance, the entire BIN data is split into multiple files that are ~5MB in size each. To download these file contents entities will need to call the BIN Files Metadata API to get the list of the BIN File names and then pass that to the BIN File Transfer API to see the contents of that file. The file contents is comma delimited. BIN Files Metadata and BIN File Transfer API also follow the data levels as described in the above table. 

BIN Files Metadata API: This API allows entities to retrieve the list of the BIN file names. When calling BIN files Metadata API, entities must pass P for Account range or T for token range as a parameter to receive the list of the account range or token range files. Along with file name, the file size, checksum and file creation date will be displayed. These additional details can be used to make sure that the entire file is consumed. Entities need to make separate calls  for each of the account range and the token range file.  

BIN File Transfer API: This API allows entities to pass the BIN file name that was retrieved from the BIN Files Metadata API response to consume it. For each file download there needs to be a separate call made to this API with the respective file name. A successful response will file stream all the contents of the file in a comma delimited format. Entities will need to write code to read the file stream and save it at their end. Using the file size, record count and  checksum that was presented on the BIN Files Metadata response, entities can validate if each of files were completely downloaded. We use the md5sum checksum algorithm here. The attributes received in the BIN File Transfer API response will be tied to the approved access level of the entity. 

Single BIN-Lookup API: This API allows an entity to request issuer BIN attribute data on an account-by-account basis. This capability provides Level 3 data by default and includes Account Level Management data for product ID, as provided by participating issuers. The service supports both six and eight-digit BINs. To use the Single BIN Lookup API, you must provide a valid Visa Primary Account Number (PAN) or Token in the request message. The response message will list all the BIN attributes as listed under Level 3 - Complete column on the table above.

VBASS Issuer API can only be accessed using file stream implementation via VBASS Files Metadata and VBASS File Transfer APIs.

File stream implementation: This implementaion allows entities to receive the full BIN data in file stream format. For optimal performance, the entire BIN data is split into multiple files that are ~5MB in size each. To download these file contents entities will need to call the VBASS Files Metadata API to get the list of the File names and then pass that to the VBASS File Transfer API to see the contents of that file. 

VBASS Files Metadata API: This API allows entities to retrieve the list of the file names. When calling VBASS Files Metadata API, entities must pass ACQ as a parameter to receive the list of files. Along with file name, the file size, checksum and file creation date will be displayed. These additional details can be used to make sure that the entire file is consumed. 

VBASS File Transfer API: This API allows entities to pass the file name that was retrieved from the VBASS Files Metadata API response to consume it. For each file download there needs to be a separate call made to this API with the respective file name. A successful response will file stream all the contents of the file in a comma delimited format. Entities will need to write code to read the file stream and save it at their end. Using the file size, record count and checksum that was presented on the VBASS Files Metadata response, entities can validate if each of files were completely downloaded. We use the md5sum checksum algorithm here.

Refer to API Reference to learn more about every individual request and response parameters. A complete list of all of the related code values and their names can be found in the Request and Response Code Reference.

Any access and use for any of the above listed API requires the participant to be a Visa licensed acquirer or issuer (or sponsored by a participating Visa licensed acquirer or issuer) and is subject to approval by Visa for permissible use cases only. Payment Card Industry Data Security Standard (PCI DSS) compliance is required of all entities that store, process, or transmit Visa cardholder data, including financial institutions, merchants and service providers. The utilization of Single BIN Lookup API requires the participant to be PCI DSS compliant.

Please contact your Visa Account Representative with more information on how to register for and participate in the VBASS.