How to integrate BINLIST.net into a decision engine

BINLIST is a service that identifies card details from the first 6/8 digits of a card. It can tell you whether the card is credit or debit. It may also identify whether the card is personal, business, or corporate. For some BINs, it returns only the issuing country. For others, it can also identify the issuing bank, including bank details.

The service is free if you stay under 10 requests per minute. For a low request volume, the integration is straightforward. If you need more requests, contact binlist.net and get API keys.

1.

Create a data source in Decisimo Portal

  • Select New in Data sources, ask the AI Assistant to configure the provider, then check and apply its proposal.
  • Once the data source is created, you do not need to do anything else because this service does not require an API key for the free tier.
    BINLIST.net data source form with the lookup endpoint, GET and JSON selected, and a {bin} parameter
  • Tell the AI Assistant that the API needs only the BIN card number. It proposes the endpoint and parameters; review and adjust them before applying the connection to your decision flow.
3.

Add BINLIST.net data source to your decision flow

  • If you already have a decision step for data sources, add the call to BINLIST.net in the same step. The decision engine will call all sources in that step in parallel. Parallel calls give you the fastest execution time.
  • If you do not have a decision flow step for external data, add one. Connect the step in your decision flow and double-click it to open the definition window.
  • In the decision flow step, define the attribute from your data object that contains the BIN number to send to BINLIST.net. Make sure you send only the first 6/8 digits, not the full card number.
  • BINLIST.net within a decision step
GO
Decisimo decision engine

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

See pricing

Run the decision making

  • Release your decision flow, deploy it to an endpoint, and make decisions using data from BINLIST.net.
Check other data source guides

Frequently asked questions

What card data should the decision send to BINLIST.net?

Send only the card’s first 6 or 8 digits, as required for the lookup, and map the source attribute to that truncated value before calling the service. Never send the full card number for a BIN lookup. Check the configured request parameters and test the outbound payload, since selecting the wrong input can expose more card data than the lookup needs.

Should I use six or eight digits for a BIN lookup?

Follow BINLIST.net’s current API requirements and use the shortest supported prefix that returns the fields your policy needs. Coverage varies by BIN: some results identify only the issuing country, while others include card type or issuer details. Test representative cards from your own market and make the policy tolerate fields that are absent.

What should the fraud decision do when BINLIST.net returns incomplete data or times out?

Treat a missing issuer or card-type field as unknown, not as proof of legitimacy or fraud. Define a fallback using the signals still available, such as continuing with other checks or routing the payment for review. Test timeout and partial-response paths before release, and make sure the policy does not silently substitute a default value.

Decisimo decision engine

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

See pricing

Related Articles

  • How to Streamline Insurance Policy Management with Policy Administration Software and Rule Engine

    Policy administration software centralizes policy lifecycle tasks. It handles creation, underwriting, rating, billing, and compliance, so insurers can automate routine work. A rule engine captures decision logic to validate data, calculate premiums, automate underwriting, and produce auditable decision traces.

  • How to integrate Email Hippo Assess into a decision engine

    How to connect Email Hippo Assess to a decision engine, step by step. This guide covers API key setup and explains how to create the data source in Decisimo and add the call to your decision flow so email, IP, and optional identity fields are evaluated during sign-up.

  • Jamaica credit bureaus and when a second call is worth it

    Learn how to compare bureau call strategies on your applicants, account for Jamaica’s reporting duties and decide when a second report is worth its cost.

  • Why segmented pre-collection activity matters for lending businesses

    Segmented pre-collection helps lending businesses focus on accounts that need attention before they become delinquent. This article explains what pre-collection is, why segmentation matters, and the main ways lenders can use it to improve recovery without unnecessary contact with borrowers who are likely to pay on time.

  • Credit limit management for BNPL / Consumer lending

    Credit limit management in BNPL and consumer lending is not a one-time check. It starts at underwriting, continues through upsell and cross-sell decisions, and should also run during portfolio monitoring as customer behavior changes. This article covers the main factors behind limit setting, when to increase limits, and when to reduce them.