BIN code lookup with apilayer API
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (3)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest
What it does
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: - bincode: A sample BIN like JH4KA7560RC003647 - apikey: Your apilayer API key Step 3: HTTP Request - Node Type: HTTP Request - Method: GET - URL: https://api.apilayer.com/bincheck/{{ $json.bincode }} - Headers: - Name: apiKey - Value: {{ $json.apikey }} (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.