BIN intelligence
Card details must be verified before authorisation. BIN intelligence gives fraud and risk developers real-time issuer, country, card type, prepaid and commercial status through Cardflo’s pre-authorisation lookup endpoint.
- Category
- Routing
- Capabilities
- 6
- Available on
- All plans
Risk and fraud teams require detailed card metadata before submitting a transaction for authorisation. Waiting until a decline occurs creates unnecessary processing costs and obscures malicious activity. Merchants need immediate access to issuer identification to block prepaid instruments, verify the origin country, and accurately calculate anticipated scheme fees at the checkout.
Cardflo provides a real-time bin check via a single API endpoint that returns comprehensive card attributes upon number entry. The gateway queries an up-to-date issuer identification network database, feeding actionable data back to the merchant's application to inform their internal fraud logic before any financial message enters the clearing network.
Through advanced BIN intelligence, we identify the card's issuing bank and country of origin, informing your global acquiring strategy. This crucial data assists in fraud prevention and the optimisation of processing costs across our acquirer partner network.
BIN intelligence overview
Accurate card metadata forms the foundation of any sophisticated merchant risk system. Relying on basic digit validation leaves platforms exposed to prepaid card fraud, unexpected cross-border interchange fees, and commercial card surcharges.
By implementing a dedicated bin lookup api, development teams can retrieve the issuing bank name, product tier, and precise geographical coordinates of a payment method the moment a customer inputs their details. This programmatic verification happens entirely pre-authorisation.
While merchants might separately configure bin routing to direct volume or rely on bin reporting and card issuer performance reporting for retrospective analysis, this specific application focuses entirely on capturing immediate, raw issuer identification network data. The resulting metadata empowers merchant systems to flag discrepancies between the card's origin and the buyer's IP address instantly.
How BIN intelligence works
Checkout intercept and API request
As the customer enters the first six to eight digits of their primary account number, the merchant application triggers an immediate request to the Cardflo endpoint. This initial sequence isolates the bank identifier without requiring the full card string or security code. The request transmits securely in the background without interrupting the buyer's progression through the payment form.
Metadata retrieval and schema mapping
The platform queries the internal card bin database to match the numerical sequence against current scheme registries. The system maps the returned variables, formatting the issuing bank name, country code, card category, and product level into a standard JSON payload. This response returns to the merchant environment in milliseconds, ensuring the front-end application never stalls while waiting for verification.
Internal risk logic application
Upon receiving the real-time bin check payload, the merchant's internal logic engine evaluates the returned metadata against their established security thresholds. If the origin country mismatches the billing address, or if the product type violates terms of service, the system can dynamically halt the transaction, prompt for additional authentication, or decline the attempt entirely before authorisation.
Why BIN intelligence matters
Pre-authorisation fraud prevention
Capturing card attributes before financial submission allows merchants to detect anomalies early. By verifying the issuing country and identifying anonymous prepaid instruments, risk teams can reject suspicious attempts without incurring processing fees or risking scheme penalties. This early intervention protects the merchant account from unnecessary authorisation declines and potential chargeback liability down the line.
Transparent cost calculation
Knowing whether a buyer holds a standard debit card, a premium credit tier, or a commercial product allows merchants to predict interchange costs accurately. This visibility ensures finance teams can model their scheme fee exposure on specific transactions, apply permitted commercial surcharges where regulated, or adjust checkout messaging based on the exact payment instrument presented.
Regulatory notes for BIN intelligence
Scheme compliance for eight-digit expansion
Both Visa and Mastercard mandate that merchants and payment technology providers correctly handle eight-digit issuing identifiers across all applications. Failing to parse the longer formats can result in scheme fines and severe processing errors, as specific blocks are subdivided among entirely different financial institutions.
Merchants building custom checkouts must ensure their front-end validation logic collects sufficient digits before executing the lookup. Restricting the input collection to legacy six-digit parameters permanently prevents the database from returning accurate commercial card identification or pinpointing the correct regulatory jurisdiction of the issuing entity.
Data security and PCI implications
Processing the first six to eight digits of a primary account number does not generally subject a merchant to the full scope of strict Payment Card Industry Data Security Standard (PCI DSS) requirements.
These leading digits solely constitute bank identifiers rather than sensitive individual cardholder data.
However, merchants must ensure they do not accidentally log or transmit the remaining digits or the security code during the verification request.
The lookup payload itself contains only public institutional metadata, meaning the resulting JSON response can be safely stored within the merchant's internal fraud logs without encryption overhead.
BIN intelligence use cases
Free trial card screening
Streaming and software services need to distinguish prepaid cards from debit and credit products before granting promotional access, because disposable instruments can undermine trial eligibility controls. Cardflo returns real-time BIN intelligence at checkout, allowing operators to apply product-specific acceptance rules before authorisation.
Issuer country order checks
Electronics retailers compare the card issuer country with billing, delivery and device locations before releasing fraud-sensitive stock, especially where fulfilment begins immediately after payment. Cardflo supplies issuer country and bank metadata through an API lookup, enabling merchants to flag inconsistent orders for review before authorisation.
Verifying regulated card credentials
Investment and wealth platforms need to establish whether a funding card was issued in a permitted jurisdiction before accepting deposits under their KYC and AML controls. Cardflo provides pre-authorisation issuer country, bank and card product data, helping compliance teams screen instruments against documented account funding policies.
Commercial card fee classification
B2B suppliers taking corporate invoice payments need to identify commercial, purchasing and business cards before authorisation, as product classification can affect scheme costs and acceptance policy. Cardflo exposes real-time card category and issuer metadata, allowing finance teams to classify the instrument and present appropriate payment options at checkout.
BIN intelligence by the numbers
Industry reports often show these gains. They appear when implementing intelligent routing based on geographic BIN data. This matches local acquirers with local issuers.
Typical savings are observed by enterprise merchants. These merchants shift from cross-border to domestic routing by accurately identifying card origins.
The reliability of identifying the issuing bank and country type serves as a foundation. It supports broader risk assessment and velocity check logic.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with BIN intelligence
- Access a comprehensive card bin database updated daily to capture new scheme number blocks.
- Detect prepaid, virtual, and gift cards instantly to enforce policy restrictions on specific inventory.
- Extract the exact issuing country to verify customer identity against location data during onboarding.
- Identify commercial and corporate card products to accurately estimate processing costs before payment submission.
- Query the issuer identification network data with millisecond latency to keep checkout flows responsive.
- Retrieve the exact issuing bank name to assist support teams during customer payment inquiries.
A short scoping call, then a written plan for your MIDs.
Questions about BIN intelligence
Does the API support the eight-digit BIN expansion?
Yes, the platform fully supports the eight-digit standard mandated by Visa and Mastercard. The card bin database updates continuously to reflect the industry transition from six-digit to eight-digit identifiers.
Developers can submit up to the first nine digits to account for account range variations, ensuring the resulting metadata remains precise. This capability prevents misidentification errors that occur when legacy systems attempt to parse expanded numerical blocks using outdated six-digit truncation logic.
How frequently is the issuer identification network data updated?
Cardflo maintains an active synchronisation with the major card schemes to ensure the underlying database reflects new block allocations and reassignments. The internal registries update daily, capturing changes across all supported geographic regions and product tiers.
Relying on stale metadata causes false positives in fraud engines and miscalculates cross-border parameters. By connecting directly to the updated repository, merchants guarantee their real-time bin check pulls from the most current institutional data available in the global payments ecosystem.
Does a BIN lookup trigger a transaction or reserve funds?
Querying the metadata endpoint does not interact with the issuing bank or the card scheme's authorisation network. It is a completely passive, informational request performed against an internal database.
The process never places a hold on the cardholder's funds, nor does it appear on their bank statement.
This allows development teams to verify card types and origins repeatedly during the checkout flow or account registration without impacting the user's available balance or generating zero-value authorisation fees.
Can the lookup distinguish between debit and credit products accurately?
The application programming interface returns explicit funding source fields, cleanly separating debit, credit, deferred debit, and prepaid instruments. This distinction relies on the exact scheme definitions mapped to that specific numeric block.
Risk systems require this exact categorisation, as prepaid and standard debit cards carry significantly different risk profiles despite often bearing the same network branding. The payload also details the specific card tier, distinguishing basic consumer products from infinite or corporate lines.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.