Skip to main content

BIN code lookup with apilayer API

Workflow preview

Workflow preview
100%
BIN code lookup with apilayer API preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow is designed to validate and fetch information about a card using the BIN code. It utilizes apilayer's BIN Check API and provides details like the card brand, type, issuing bank, and c...

Best for

  • Engineering automation workflows
  • beginner n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.set, n8n-nodes-base.stickynote, n8n-nodes-base.httprequest

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Sarfaraz Muhammad Sajib.

Original n8n.io source

1.1 Workflow description

Title
BIN code lookup with apilayer API
Workflow name
BIN code lookup with apilayer API

This workflow is designed to validate and fetch information about a card using the BIN code. It utilizes apilayer's BIN Check API and provides details like the card brand, type, issuing bank, and country.

Prerequisites:

  • An apilayer account
  • API Key for the BIN Check API

Steps in n8n:

Step 1: Manual Trigger

  • Node Type: Manual Trigger
  • Purpose: Starts the workflow manually

Step 2: Set BIN Code and API Key

  • Node Type: Set
  • Fields to set:
    • bin_code: A sample BIN like JH4KA7560RC003647
    • apikey: Your apilayer API key

Step 3: HTTP Request

(Optional) Step 4: Handle the Output

  • Add nodes to store, parse, or visualize the API response.

Expected Output: The response from apilayer contains detailed information about the provided BIN:

  • Card scheme (e.g., VISA, MasterCard)
  • Type (credit, debit, prepaid)
  • Issuing bank
  • Country of issuance

Example Use Case: Use this to build a fraud prevention microservice, pre-validate card data before sending to payment gateways, or enrich card-related logs.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Execute workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Set API Key & BIN Number to Lookup

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Lookup BIN

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

3. Summary Table

Workflow BIN code lookup with apilayer API
Complexity beginner
Nodes 4
Categories Engineering
Author Sarfaraz Muhammad Sajib
Published 23 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6306/6306.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does BIN code lookup with apilayer API do?

This workflow is designed to validate and fetch information about a card using the BIN code. It utilizes apilayer's BIN Check API and provides details like the card brand, type, issuing bank, and c...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering use case.