Adyen BinLookup API

Name: Adyen BinLookup API
Brand: Adyen BIN Lookup API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey, basic2 EndpointsREST

Install Jentic One Beta

Connect the Adyen BinLookup API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen BinLookup API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Adyen BinLookup API.

Determine which 3D Secure version (3DS1, 3DS2) the issuing bank supports for a card BIN via POST /get3dsAvailability

Retrieve a processing cost estimate for a card via POST /getCostEstimate to feed dynamic pricing logic

Decide checkout authentication routing — frictionless 3DS2, challenge, or fallback — before payment creation

GET STARTED

Start building with Adyen BinLookup API

Explore with Jentic

View OpenAPI Document

For Agents

Look up 3D Secure version availability and processing cost estimates for a card BIN before creating a payment.

Use for: Check which 3D Secure version applies to a given card BIN, Get an Adyen interchange and fee estimate for a specific card, Decide whether to use 3DS2 frictionless or fallback for a checkout, Surface processing cost to a dynamic pricing engine before checkout

Not supported: Does not handle payment creation, 3DS authentication itself, or settlement — use for pre-checkout BIN-level 3DS and cost lookups only.

The Adyen BIN Lookup API resolves card BIN (Bank Identification Number) data into actionable information for routing and authentication decisions before a payment is created. Two endpoints cover the core needs: POST /get3dsAvailability returns the 3D Secure version supported by the issuing bank for a given BIN, and POST /getCostEstimate returns Adyen's interchange and scheme fee estimate for a card. Use the API at the front of a checkout flow to choose the right authentication path and to surface processing-cost estimates to internal pricing logic.

Use Cases

Patterns agents use Adyen BinLookup API for, with concrete tasks.

★ Pre-Checkout 3D Secure Routing

Modern checkouts choose between 3DS2 frictionless, 3DS2 challenge, and 3DS1 fallback based on what the issuer supports. POST /get3dsAvailability returns that information for a given BIN before the customer commits to checkout, so the front end can configure the payment session correctly the first time and avoid an unnecessary fallback round-trip.

Call POST /get3dsAvailability with the cardNumber prefix (BIN) and merchantAccount, then use the threeDSecure flag to configure the Checkout session

Dynamic Pricing Based on Processing Cost

Some merchants pass interchange-style cost differentials onto the customer or use them in margin analysis. POST /getCostEstimate returns Adyen's estimate of the interchange and scheme fee for a specific card, which a pricing engine can use to surface a different price for premium cards or to gate certain payment methods.

Call POST /getCostEstimate with the cardNumber prefix and amount, then pass the returned costEstimateAmount into the merchant's pricing engine

Issuer-Aware Checkout Optimisation

Combining the 3DS availability and cost estimate calls lets a checkout decide more than just the auth flow — whether to suppress particular issuers from the wallet shortlist, whether to upsell to a different funding source, or whether to prompt for a fallback method. Both endpoints are inexpensive POSTs that complete before the payment is created.

Call POST /get3dsAvailability and POST /getCostEstimate in parallel for the entered card, then choose a paymentMethod to highlight in the checkout UI

Agent-Driven BIN Decisioning via Jentic

A checkout-orchestration agent can use Jentic to call BIN Lookup before committing a Checkout request. Jentic resolves both operations from intent search, executes them with credentials managed in the Jentic vault, and returns the structured response for the agent to feed into its routing decision.

Use Jentic to search for '3d secure availability for a card', execute POST /get3dsAvailability with the BIN, and chain the result into a PaymentMethodsRequest call to Adyen Checkout

Key Endpoints

2 endpoints — the adyen bin lookup api resolves card bin (bank identification number) data into actionable information for routing and authentication decisions before a payment is created.

METHOD

PATH

DESCRIPTION

POST

/get3dsAvailability

Return 3D Secure version availability for a card BIN

POST

/getCostEstimate

Return processing cost estimate for a card BIN

POST

/get3dsAvailability

Return 3D Secure version availability for a card BIN

POST

/getCostEstimate

Return processing cost estimate for a card BIN

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Adyen X-API-Key and basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as '3d secure availability for a card' or 'card processing cost estimate', and Jentic returns the matching BinLookup operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Adyen BinLookup API through Jentic.

What authentication does the Adyen BIN Lookup API use?

The API supports an apiKey scheme using the X-API-Key header and HTTP basic auth with a Customer Area username and password. Through Jentic, the X-API-Key is stored in the encrypted vault so agents call /get3dsAvailability and /getCostEstimate without holding the raw credential.

Can I look up the issuing bank for a card BIN with this API?

The API focuses on actionable lookups — 3D Secure version availability and processing cost estimate — rather than returning a generic issuer profile. For pure issuer-name lookups, Adyen exposes other data inside the Checkout flow's payment methods response.

What are the rate limits for the Adyen BIN Lookup API?

The OpenAPI spec does not declare programmatic rate limits. Adyen documents per-merchant-account throughput limits in their developer portal; for high-volume checkouts, cache 3DS availability results per BIN for the session rather than calling on every keystroke.

How do I check 3D Secure availability through Jentic?

Search Jentic for '3d secure availability for a card', load the POST /get3dsAvailability operation, and execute it with the card BIN and merchantAccount. Jentic returns the structured response so the agent can drive the next Checkout step.

Should I call BIN Lookup on every keystroke or once per checkout?

Call once when the BIN is fully entered and stable (typically the first 6-8 digits). Calling on every keystroke wastes calls and risks triggering rate limits without changing the answer.

Adyen BinLookup API

Connect the Adyen BinLookup API to your agent

Capabilities

Start building with Adyen BinLookup API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs