Currently, we do not have a timeline on when the BIN Table API will be available. Please check back on the API Browser page or the Release Notes page periodically for updates.
Release Notes - https://developer.visa.com/release_notes
API Browser - https://developer.visa.com/apibrowser
Is there a chance to see this API in public (or in private, because it does not matter)?
We are willing to pay and obtain access.
Thanks in advance,
Hi there - any updates on this? We are also in need for this information.
Its april already, is there some updates on BIN API?
At this time, we do not have an API that provides BIN table information. Please do note the solution is that it doesn’t support the outright sending of the complete BIN table extract. We will have more information in the coming months. For now, you could consider using the PAAI API ( https://developer.visa.com/capabilities/paai ).
VISA credit cards numbers starting with;
💳 4 , 4556, 4539, 4916, 4532, 4929, 40240071, 4485, 4716 💳
prefix numbers and it has max 16 digits number. 😉
Did this service ever got released?
I was looking at the release notes but I wasn't able to find anything related to BIN table.
We are integrating BIN table and Account Validation services on all the card brands/networks that we support so we can enhance our chargeback assessment and also calculate the interchange/MDR properly. Right now VISA is the only one we are missing.
Can you give us a heads up on it?
At this time, we do not have an API that provides BIN table information. We have no new updates for you yet. For BIN, I'm still recommending you to look at Payment Account Attributes Inquiry - https://developer.visa.com/capabilities/paai
@DianaTran-Yee thanks for getting back.
So, is this API available for Payment Service Providers and Payment Facilitators?
I've checked on that and it successfully returned a card details based on a BIN I've provided. Although it is no the ideal to query that on every single transaction, we could add a cache layer on top of those calls to avoid hit your servers frequently.
Looking forward to see how we can get access for it in production.