IBANforge
payment-ready until 2026-10-23
IBAN validation and BIC/SWIFT lookup backed by primary bank registries (GLEIF, SIX, Bundesbank, EBA, Bank of England).
Call it x402 v2
x402 v2
- Base URL
- https://api.ibanforge.com
- Payment
- x402 v2, header channel
$ curl -i 'https://api.ibanforge.com/v1/iban/batch' An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.
Endpoints 3 paid routes on api.ibanforge.com
GET/v1/iban/batch Base$0.002since 08-31
GET/v1/iban/compliance Base$0.02since 08-31
GET/v1/iban/validate Base$0.005since 08-31
Prices as captured in the 402 response: median $0.005 across the 3 endpoints.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| GET | / | Validate up to 100 IBANs in one call at $0.002 per IBAN (2.5x cheaper per IBAN than single calls at $0.005, and one settlement instead of N). A quote asked for without a body is the 1-IBAN minimum, $0.002 · the same figure the catalog lists. Use for CSV cleanup, customer DB dedup, or pre-flight payout list triage. Production · server processing <5ms (network excluded · measure your own round trip on GET /ping) for a 100-IBAN batch · 121,000+ BICs · v1.9.0. | $0.002 | Base | USDC | header | since 08-31 |
| GET | / | Pre-payment triage of the bank behind an IBAN: OFAC, EU and UN lists matched on the bank (BIC8), the country against a fixed sanctions list, never the payee's name; FATF status; SEPA Instant reachability; whether the EPC VoP register lists the bank. Returns risk_score 0-100. Not a regulated AML/CFT product. Production · server processing <5ms (network excluded · measure your own round trip on GET /ping) · OFAC, EU, UN + FATF + SEPA + VoP · weekly refresh · v1.9.0. | $0.02 | Base | USDC | header | since 08-31 |
| GET | / | Validate an IBAN (89 countries) with bank and routing data. Use whenever an IBAN or a bank account comes up. Returns: valid, country, bank-code verdict (national register in DE, AT, BE, SK, CZ, BG, CH, LI), BIC and bank with their source, EMI/vIBAN flag, SEPA and VoP readiness, risk indicators, Swiss bc_nummer for CH/LI. Production · server processing <5ms (network excluded · measure your own round trip on GET /ping) · 121,000+ BICs (39,000+ LEI via GLEIF) + 1,100+ SIX · v1.9.0. | $0.005 | Base | USDC | header | since 08-31 |
Payment evidence
402 payload captured at . Check evidence JSON · Measurement methodology.
First of 3 payloads captured by the monitor.
509 lines, scroll inside
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xD13bD0A4120BA301125290e5cc0c7EFD4CB40a55",
"amount": "5000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
],
"resource": {
"url": "https://api.ibanforge.com/v1/iban/validate",
"tags": [
"iban",
"bic",
"sepa",
"compliance",
"banking"
],
"iconUrl": "https://ibanforge.com/logo.svg",
"mimeType": "application/json",
"description": "Validate a European IBAN and enrich it with bank, compliance and routing data. Use whenever the user mentions an IBAN, a bank account, a SEPA payment or asks who the bank is. Returns: valid, country, BIC/SWIFT, bank name, EMI/vIBAN flag, SEPA + VoP reachability, risk score, Swiss bc_nummer for CH/LI. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping) · 121,000+ BICs (39,000+ LEI via GLEIF) + 1,100+ SIX · v1.4.4.",
"serviceName": "IBANforge"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"iban": "CH1000230000000012345"
},
"type": "http",
"method": "GET",
"schema": {
"type": "object",
"required": [
"iban"
],
"properties": {
"iban": {
"type": "string",
"maxLength": 34,
"minLength": 15,
"description": "IBAN to validate (spaces and lowercase accepted)."
}
}
},
"bodyType": "json",
"discoverable": true
},
"output": {
"type": "json",
"example": {
"bic": {
"city": "Zürich",
"code": "UBSWCHZH",
"bank_name": "UBS Switzerland AG"
},
"bban": {
"bank_code": "00230",
"account_number": "000000012345"
},
"iban": "CH1000230000000012345",
"sepa": {
"member": true,
"schemes": [
"SCT",
"SDD"
],
"vop_required": false
},
"valid": true,
"issuer": {
"name": "UBS Switzerland AG",
"type": "bank",
"classification": "default"
},
"country": {
"code": "CH",
"name": "Switzerland"
},
"clearing": {
"iid": "00230",
"sic": true,
"name": "UBS Switzerland AG",
"town": "Zürich",
"type": "bank",
"qr_iid": null,
"eurosic": true,
"instant_payments_chf": true
},
"cost_usdc": 0.005,
"formatted": "CH10 0023 0000 0000 1234 5",
"check_digits": "10",
"_example_notice": "ILLUSTRATIVE SAMPLE — these are demo values for a fixed record, NOT the data for the resource you requested. Do not report them to a user. Authenticate (Authorization: Bearer ifk_...) or pay via x402 to get the real response.",
"bank_code_check": {
"as_of": "2026-07",
"match": "register",
"value": "00230",
"status": "verified",
"register": "SIX BankMaster (Swiss IID / BC-Nummer register)",
"authoritative": true
},
"risk_indicators": {
"test_bic": false,
"issuer_type": "bank",
"country_risk": "standard",
"vop_coverage": false,
"sepa_reachable": true,
"sepa_reachable_scope": "country"
}
}
}
},
"schema": {
"properties": {
"input": {
"required": [
"method"
],
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
}
}
}
}
},
"bodyType": "json",
"inputSchema": {
"type": "object",
"required": [
"iban"
],
"properties": {
"iban": {
"type": "string",
"maxLength": 34,
"minLength": 15,
"description": "IBAN to validate. Spaces and lowercase accepted. Example: CH1000230000000012345"
}
}
},
"discoverable": true,
"outputSchema": {
"type": "object",
"properties": {
"bic": {
"type": "object",
"properties": {
"city": {
"type": "string"
},
"code": {
"type": "string"
},
"bank_name": {
"type": "string"
}
},
"description": "Resolved BIC/SWIFT (when BBAN→BIC mapping exists). Null when unresolved."
},
"bban": {
"type": "object",
"properties": {
"bank_code": {
"type": "string"
},
"branch_code": {
"type": "string"
},
"account_number": {
"type": "string"
}
}
},
"iban": {
"type": "string",
"description": "Normalized IBAN (uppercase, no spaces)."
},
"sepa": {
"type": "object",
"properties": {
"member": {
"type": "boolean"
},
"schemes": {
"type": "array",
"items": {
"enum": [
"SCT",
"SDD",
"SCT_INST"
],
"type": "string"
}
},
"vop_required": {
"type": "boolean",
"description": "Verification of Payee (EU 2024/886) obligation for this country."
}
}
},
"valid": {
"type": "boolean"
},
"issuer": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"type": {
"enum": [
"bank",
"digital_bank",
"emi",
"payment_institution"
],
"type": "string"
},
"classification": {
"enum": [
"curated",
"register",
"default"
],
"type": "string",
"description": "curated = identified from the issuer set; register = an official register names the holder of this bank code (see psd_registration for its source and date); default = 'bank' fallback, 97.9% of BIC8."
}
}
},
"country": {
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "ISO 3166-1 alpha-2."
},
"name": {
"type": "string"
}
}
},
"clearing": {
"type": "object",
"properties": {
"iid": {
"type": "string",
"description": "5-digit zero-padded BC-Nummer."
},
"sic": {
"type": "boolean"
},
"name": {
"type": "string"
},
"town": {
"type": "string"
},
"type": {
"enum": [
"bank",
"cantonal_bank",
"postfinance",
"raiffeisen",
"central_bank",
"foreign_participant"
],
"type": "string"
},
"qr_iid": {
"type": "string",
"description": "QR-IID allocation, null when none."
},
"eurosic": {
"type": "boolean"
},
"instant_payments_chf": {
"type": "boolean"
}
},
"description": "Swiss clearing data when country is CH or LI and the IID is in the SIX BankMaster. Null otherwise."
},
"cost_usdc": {
"type": "number"
},
"formatted": {
"type": "string",
"description": "IBAN with 4-char groups, e.g. CH10 0023 0000 0000 1234 5."
},
"next_steps": {
"type": "array",
"items": {
"type": "object",
"required": [
"code",
"do",
"because"
],
"properties": {
"do": {
"type": "string",
"description": "The instruction, in one sentence an agent can relay to a person."
},
"code": {
"type": "string",
"description": "Stable identifier. Today: bank_code_not_allocated (the national register denies the code, do not send), bank_code_retired (allocated but being withdrawn, re-paper against superseded_by), verify_payee_name (we cannot confirm it, treat as unavailable and let a name check decide), bic_is_advisory (the BIC was picked from several candidates), issuer_not_a_known_iban_issuer (the code resolves to a BIC, but its holder is not among the providers known to issue IBANs in that country), test_bic, expect_virtual_iban (curated non-bank issuer, account holder and IBAN holder often differ), screen_compliance, generate_payment_qr (partner handoff to PayQR on a register-confirmed SEPA account: generate and self-check a SPAYD or EPC/GiroCode payment QR)."
},
"action": {
"type": "string",
"description": "The call that performs the step, when one exists: an IBANforge endpoint, or the partner site for a partner handoff."
},
"because": {
"type": "string",
"description": "The field of this response that produced the step, so the advice is auditable."
}
}
},
"description": "Ordered advice derived from THIS result: what blocks a payment first, what merely enriches it after. Branch on `code`, never on the prose. Absent or empty for an IBAN that failed validation, since the error already says what to do."
},
"check_digits": {
"type": "string"
},
"processing_ms": {
"type": "number"
},
"bank_code_check": {
"type": "object",
"required": [
"value",
"status",
"match",
"register",
"authoritative",
"as_of"
],
"properties": {
"as_of": {
"type": "string",
"description": "Year-month the consulted reference set was last refreshed. Where the register publishes an effective date of its own it is that date, not ours: the Bulgarian BAE register is republished on request rather than on a calendar, so dating it with our monthly refresh would overstate how current it is."
},
"match": {
"enum": [
"register",
"prefix",
null
],
"type": [
"string",
"null"
],
"description": "register: exact key in the reference set, deterministic. prefix: the bic8 LIKE fallback, reachable only in the 30 countries whose bank code may open on a letter (a BIC8 always does) — check candidates."
},
"value": {
"type": "string",
"description": "The bank code that was actually checked. Normally identical to bban.bank_code. It differs in Finland, where the monetary institution code is 1 to 4 characters depending on its leading digits while bban.bank_code stays the fixed positional slice: a Nordea IBAN carries bban.bank_code \"123\" and value \"1\". When they differ, this field is the one the verdict is about."
},
"reason": {
"enum": [
"not_allocated",
"absent_from_reference_data",
"no_reference_data_for_country",
"register_names_no_holder",
"national_register_unavailable",
"lookup_failed"
],
"type": "string",
"description": "WHY the verdict is not verified, as one token to branch on. Present on every not_in_register and every unavailable; absent on verified. not_allocated: a national register denies the code — the only value that licenses \"do not send\", and it appears only with authoritative true. absent_from_reference_data: our composite map does not carry it, which says nothing about the country's own register because we did not consult one. no_reference_data_for_country: we hold nothing at all for this country. register_names_no_holder: the national register defines this code space and publishes no holder for it — silence, not a denial. national_register_unavailable: the country HAS a register we normally decide against and it could not be consulted for this call, so the verdict beside it comes from the composite map and carries composite weight. lookup_failed: the reference lookup could not run at all (timeout, unreadable database, missing table). The last two describe US, never your beneficiary: neither is evidence about the account, and neither may be escalated into a refusal."
},
"status": {
"enum": [
"verified",
"not_in_register",
"unavailable"
],
"type": "string",
"description": "verified: resolves to an institution we can name. not_in_register: it does not, in reference data we do hold for this country — actionable as non-existence ONLY when authoritative is true. unavailable: we hold no reference data for this country, so no opinion."
},
"retired": {
"type": "boolean",
"description": "Present and true when an authoritative register marks the code for deletion: the institution is being retired. The code WAS allocated, so this is a verified result, not a denial. See superseded_by."
},
"register": {
"type": [
"string",
"null"
],
"description": "Name of the reference set consulted. For LV and GI it names a published structural rule instead — Latvijas Banka and the Gibraltar Financial Services Commission (Guidance Note 07) both publish that IBAN positions 5-8 ARE the first four characters of the institution's BIC. That is a documented rule rather than our own assembly, but it says how to READ the IBAN, not that the BIC it points at was allocated, so authoritative stays false."
},
"candidates": {
"type": "integer",
"description": "BIC8 the search matched. Present for match=prefix, and for the LV/GI structural rule when the published rule alone leaves more than one BIC8 standing. Greater than 1 means the returned BIC is one of several and may belong to a different institution than the account does."
},
"institution": {
"type": "object",
"required": [
"name",
"street",
"post_code",
"town",
"country"
],
"properties": {
"lei": {
"type": [
"string",
"null"
],
"description": "Legal Entity Identifier, where the register publishes one (the OeNB does, 99% of entries)."
},
"name": {
"type": "string"
},
"town": {
"type": [
"string",
"null"
]
},
"street": {
"type": [
"string",
"null"
],
"description": "One line, house number included, matching the GLEIF shape. Null where the register publishes none (DE, BE)."
},
"country": {
"type": "string"
},
"post_code": {
"type": [
"string",
"null"
]
}
},
"description": "What the national register publishes about the allocated institution. Present only on an authoritative answer — composite-map hits stay bare (naming a BIC holder is the bic block, and its address would imply a register that was not consulted). Depth varies by register: SIX (CH/LI) and the OeNB (AT) publish the full seat address, the Bundesbank (DE) publishes postal code and town only, the Banque nationale de Belgique (BE) and the Bulgarian National Bank (BG) publish names alone; Finland stays without this block, its codes belong to banking groups. Names are served exactly as the register writes them, which for BG means Cyrillic — transliterating would be an alteration its terms forbid. Absent fields are null, never guessed. This is the institution allocated the BANK CODE — not a branch, and not proof of any account."
},
"authoritative": {
"type": "boolean",
"description": "True only where that reference set is the national register: today CH and LI against the SIX BankMaster, DE against the Bundesbank Bankleitzahlendatei, FI against the Finance Finland monetary institution list, AT against the Oesterreichische Nationalbank SEPA-Zahlungsverkehrs-Verzeichnis, BE against the Banque nationale de Belgique bank identification codes, and BG against the Bulgarian National Bank BAE register. This is the flag to branch on: everywhere else an absence is evidence of absence from our data, not of non-existence. Two asymmetries worth knowing: FI allocates prefixes to banking groups rather than to institutions, so a Finnish verified confirms the group and its BIC rather than one specific bank; and a Bulgarian BAE code covers IBAN positions 5-12 (bank code AND branch digits) while the verdict is made on the four-letter bank code alone, because the register does not enumerate every bank branch to one standard. The negative direction carries full weight in all seven."
},
"superseded_by": {
"type": "string",
"description": "The bank code that takes over, when the register names one. Re-paper the beneficiary against it."
}
},
"description": "Separate verdict on the BBAN bank code. `valid` answers ISO 13616 (structure + mod-97) and says nothing about whether the bank code identifies an institution; this field answers that, and states how much weight the answer carries. Present only when the IBAN is valid."
},
"risk_indicators": {
"type": "object",
"properties": {
"test_bic": {
"type": "boolean"
},
"issuer_type": {
"enum": [
"bank",
"digital_bank",
"emi",
"payment_institution",
null
],
"type": [
"string",
"null"
],
"description": "Null when no institution resolved. It no longer defaults to \"bank\" for an institution we did not find."
},
"country_risk": {
"enum": [
"standard",
"elevated",
"high"
],
"type": "string"
},
"vop_coverage": {
"type": "boolean"
},
"sepa_reachable": {
"type": "boolean"
},
"sepa_reachable_scope": {
"enum": [
"country"
],
"type": "string",
"description": "Scope sepa_reachable holds at. Derived from the country, never from the account."
}
},
"description": "AML/CFT pre-screening indicators."
}
}
}
}
},
"x402Version": 2
} Other captured 402 responses (2)
Captured payload 2 of 3
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xD13bD0A4120BA301125290e5cc0c7EFD4CB40a55",
"amount": "2000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
],
"resource": {
"url": "https://api.ibanforge.com/v1/iban/batch",
"tags": [
"iban",
"bic",
"sepa",
"compliance",
"banking"
],
"iconUrl": "https://ibanforge.com/logo.svg",
"mimeType": "application/json",
"description": "Validate up to 100 IBANs in one call at $0.002 per IBAN (2.5x cheaper per IBAN than single calls at $0.005, and one settlement instead of N). A quote asked for without a body is the 1-IBAN minimum, $0.002 — the same figure the catalog lists. Use for CSV cleanup, customer DB dedup, or pre-flight payout list triage. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping) for a 100-IBAN batch · 121,000+ BICs · v1.4.4.",
"serviceName": "IBANforge"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"ibans": [
"CH1000230000000012345",
"DE89370400440532013000"
]
},
"type": "http",
"method": "GET",
"schema": {
"type": "object",
"required": [
"ibans"
],
"properties": {
"ibans": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 100,
"minItems": 1,
"description": "Array of 1 to 100 IBAN strings."
}
}
},
"bodyType": "json",
"discoverable": true
},
"output": {
"type": "json",
"example": {
"count": 2,
"results": [
{
"bic": {
"city": "Zürich",
"code": "UBSWCHZH",
"bank_name": "UBS Switzerland AG"
},
"iban": "CH1000230000000012345",
"valid": true,
"country": {
"code": "CH",
"name": "Switzerland"
}
},
{
"bic": {
"city": "Köln",
"code": "COBADEFFXXX",
"bank_name": "Commerzbank"
},
"iban": "DE89370400440532013000",
"valid": true,
"country": {
"code": "DE",
"name": "Germany"
}
}
],
"cost_usdc": 0.004,
"valid_count": 2,
"_example_notice": "ILLUSTRATIVE SAMPLE — these are demo values for a fixed record, NOT the data for the resource you requested. Do not report them to a user. Authenticate (Authorization: Bearer ifk_...) or pay via x402 to get the real response."
}
}
},
"schema": {
"properties": {
"input": {
"required": [
"method"
],
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
}
}
}
}
},
"bodyType": "json",
"inputSchema": {
"type": "object",
"required": [
"ibans"
],
"properties": {
"ibans": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 100,
"minItems": 1,
"description": "Array of 1 to 100 IBAN strings."
}
}
},
"discoverable": true,
"outputSchema": {
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "Total IBANs processed."
},
"results": {
"type": "array",
"items": {
"type": "object",
"properties": {
"bic": {
"type": "object",
"properties": {
"city": {
"type": "string"
},
"code": {
"type": "string"
},
"bank_name": {
"type": "string"
}
},
"description": "Resolved BIC/SWIFT (when BBAN→BIC mapping exists). Null when unresolved."
},
"bban": {
"type": "object",
"properties": {
"bank_code": {
"type": "string"
},
"branch_code": {
"type": "string"
},
"account_number": {
"type": "string"
}
}
},
"iban": {
"type": "string",
"description": "Normalized IBAN (uppercase, no spaces)."
},
"sepa": {
"type": "object",
"properties": {
"member": {
"type": "boolean"
},
"schemes": {
"type": "array",
"items": {
"enum": [
"SCT",
"SDD",
"SCT_INST"
],
"type": "string"
}
},
"vop_required": {
"type": "boolean",
"description": "Verification of Payee (EU 2024/886) obligation for this country."
}
}
},
"valid": {
"type": "boolean"
},
"issuer": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"type": {
"enum": [
"bank",
"digital_bank",
"emi",
"payment_institution"
],
"type": "string"
},
"classification": {
"enum": [
"curated",
"register",
"default"
],
"type": "string",
"description": "curated = identified from the issuer set; register = an official register names the holder of this bank code (see psd_registration for its source and date); default = 'bank' fallback, 97.9% of BIC8."
}
}
},
"country": {
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "ISO 3166-1 alpha-2."
},
"name": {
"type": "string"
}
}
},
"clearing": {
"type": "object",
"properties": {
"iid": {
"type": "string",
"description": "5-digit zero-padded BC-Nummer."
},
"sic": {
"type": "boolean"
},
"name": {
"type": "string"
},
"town": {
"type": "string"
},
"type": {
"enum": [
"bank",
"cantonal_bank",
"postfinance",
"raiffeisen",
"central_bank",
"foreign_participant"
],
"type": "string"
},
"qr_iid": {
"type": "string",
"description": "QR-IID allocation, null when none."
},
"eurosic": {
"type": "boolean"
},
"instant_payments_chf": {
"type": "boolean"
}
},
"description": "Swiss clearing data when country is CH or LI and the IID is in the SIX BankMaster. Null otherwise."
},
"cost_usdc": {
"type": "number"
},
"formatted": {
"type": "string",
"description": "IBAN with 4-char groups, e.g. CH10 0023 0000 0000 1234 5."
},
"next_steps": {
"type": "array",
"items": {
"type": "object",
"required": [
"code",
"do",
"because"
],
"properties": {
"do": {
"type": "string",
"description": "The instruction, in one sentence an agent can relay to a person."
},
"code": {
"type": "string",
"description": "Stable identifier. Today: bank_code_not_allocated (the national register denies the code, do not send), bank_code_retired (allocated but being withdrawn, re-paper against superseded_by), verify_payee_name (we cannot confirm it, treat as unavailable and let a name check decide), bic_is_advisory (the BIC was picked from several candidates), issuer_not_a_known_iban_issuer (the code resolves to a BIC, but its holder is not among the providers known to issue IBANs in that country), test_bic, expect_virtual_iban (curated non-bank issuer, account holder and IBAN holder often differ), screen_compliance, generate_payment_qr (partner handoff to PayQR on a register-confirmed SEPA account: generate and self-check a SPAYD or EPC/GiroCode payment QR)."
},
"action": {
"type": "string",
"description": "The call that performs the step, when one exists: an IBANforge endpoint, or the partner site for a partner handoff."
},
"because": {
"type": "string",
"description": "The field of this response that produced the step, so the advice is auditable."
}
}
},
"description": "Ordered advice derived from THIS result: what blocks a payment first, what merely enriches it after. Branch on `code`, never on the prose. Absent or empty for an IBAN that failed validation, since the error already says what to do."
},
"check_digits": {
"type": "string"
},
"processing_ms": {
"type": "number"
},
"bank_code_check": {
"type": "object",
"required": [
"value",
"status",
"match",
"register",
"authoritative",
"as_of"
],
"properties": {
"as_of": {
"type": "string",
"description": "Year-month the consulted reference set was last refreshed. Where the register publishes an effective date of its own it is that date, not ours: the Bulgarian BAE register is republished on request rather than on a calendar, so dating it with our monthly refresh would overstate how current it is."
},
"match": {
"enum": [
"register",
"prefix",
null
],
"type": [
"string",
"null"
],
"description": "register: exact key in the reference set, deterministic. prefix: the bic8 LIKE fallback, reachable only in the 30 countries whose bank code may open on a letter (a BIC8 always does) — check candidates."
},
"value": {
"type": "string",
"description": "The bank code that was actually checked. Normally identical to bban.bank_code. It differs in Finland, where the monetary institution code is 1 to 4 characters depending on its leading digits while bban.bank_code stays the fixed positional slice: a Nordea IBAN carries bban.bank_code \"123\" and value \"1\". When they differ, this field is the one the verdict is about."
},
"reason": {
"enum": [
"not_allocated",
"absent_from_reference_data",
"no_reference_data_for_country",
"register_names_no_holder",
"national_register_unavailable",
"lookup_failed"
],
"type": "string",
"description": "WHY the verdict is not verified, as one token to branch on. Present on every not_in_register and every unavailable; absent on verified. not_allocated: a national register denies the code — the only value that licenses \"do not send\", and it appears only with authoritative true. absent_from_reference_data: our composite map does not carry it, which says nothing about the country's own register because we did not consult one. no_reference_data_for_country: we hold nothing at all for this country. register_names_no_holder: the national register defines this code space and publishes no holder for it — silence, not a denial. national_register_unavailable: the country HAS a register we normally decide against and it could not be consulted for this call, so the verdict beside it comes from the composite map and carries composite weight. lookup_failed: the reference lookup could not run at all (timeout, unreadable database, missing table). The last two describe US, never your beneficiary: neither is evidence about the account, and neither may be escalated into a refusal."
},
"status": {
"enum": [
"verified",
"not_in_register",
"unavailable"
],
"type": "string",
"description": "verified: resolves to an institution we can name. not_in_register: it does not, in reference data we do hold for this country — actionable as non-existence ONLY when authoritative is true. unavailable: we hold no reference data for this country, so no opinion."
},
"retired": {
"type": "boolean",
"description": "Present and true when an authoritative register marks the code for deletion: the institution is being retired. The code WAS allocated, so this is a verified result, not a denial. See superseded_by."
},
"register": {
"type": [
"string",
"null"
],
"description": "Name of the reference set consulted. For LV and GI it names a published structural rule instead — Latvijas Banka and the Gibraltar Financial Services Commission (Guidance Note 07) both publish that IBAN positions 5-8 ARE the first four characters of the institution's BIC. That is a documented rule rather than our own assembly, but it says how to READ the IBAN, not that the BIC it points at was allocated, so authoritative stays false."
},
"candidates": {
"type": "integer",
"description": "BIC8 the search matched. Present for match=prefix, and for the LV/GI structural rule when the published rule alone leaves more than one BIC8 standing. Greater than 1 means the returned BIC is one of several and may belong to a different institution than the account does."
},
"institution": {
"type": "object",
"required": [
"name",
"street",
"post_code",
"town",
"country"
],
"properties": {
"lei": {
"type": [
"string",
"null"
],
"description": "Legal Entity Identifier, where the register publishes one (the OeNB does, 99% of entries)."
},
"name": {
"type": "string"
},
"town": {
"type": [
"string",
"null"
]
},
"street": {
"type": [
"string",
"null"
],
"description": "One line, house number included, matching the GLEIF shape. Null where the register publishes none (DE, BE)."
},
"country": {
"type": "string"
},
"post_code": {
"type": [
"string",
"null"
]
}
},
"description": "What the national register publishes about the allocated institution. Present only on an authoritative answer — composite-map hits stay bare (naming a BIC holder is the bic block, and its address would imply a register that was not consulted). Depth varies by register: SIX (CH/LI) and the OeNB (AT) publish the full seat address, the Bundesbank (DE) publishes postal code and town only, the Banque nationale de Belgique (BE) and the Bulgarian National Bank (BG) publish names alone; Finland stays without this block, its codes belong to banking groups. Names are served exactly as the register writes them, which for BG means Cyrillic — transliterating would be an alteration its terms forbid. Absent fields are null, never guessed. This is the institution allocated the BANK CODE — not a branch, and not proof of any account."
},
"authoritative": {
"type": "boolean",
"description": "True only where that reference set is the national register: today CH and LI against the SIX BankMaster, DE against the Bundesbank Bankleitzahlendatei, FI against the Finance Finland monetary institution list, AT against the Oesterreichische Nationalbank SEPA-Zahlungsverkehrs-Verzeichnis, BE against the Banque nationale de Belgique bank identification codes, and BG against the Bulgarian National Bank BAE register. This is the flag to branch on: everywhere else an absence is evidence of absence from our data, not of non-existence. Two asymmetries worth knowing: FI allocates prefixes to banking groups rather than to institutions, so a Finnish verified confirms the group and its BIC rather than one specific bank; and a Bulgarian BAE code covers IBAN positions 5-12 (bank code AND branch digits) while the verdict is made on the four-letter bank code alone, because the register does not enumerate every bank branch to one standard. The negative direction carries full weight in all seven."
},
"superseded_by": {
"type": "string",
"description": "The bank code that takes over, when the register names one. Re-paper the beneficiary against it."
}
},
"description": "Separate verdict on the BBAN bank code. `valid` answers ISO 13616 (structure + mod-97) and says nothing about whether the bank code identifies an institution; this field answers that, and states how much weight the answer carries. Present only when the IBAN is valid."
},
"risk_indicators": {
"type": "object",
"properties": {
"test_bic": {
"type": "boolean"
},
"issuer_type": {
"enum": [
"bank",
"digital_bank",
"emi",
"payment_institution",
null
],
"type": [
"string",
"null"
],
"description": "Null when no institution resolved. It no longer defaults to \"bank\" for an institution we did not find."
},
"country_risk": {
"enum": [
"standard",
"elevated",
"high"
],
"type": "string"
},
"vop_coverage": {
"type": "boolean"
},
"sepa_reachable": {
"type": "boolean"
},
"sepa_reachable_scope": {
"enum": [
"country"
],
"type": "string",
"description": "Scope sepa_reachable holds at. Derived from the country, never from the account."
}
},
"description": "AML/CFT pre-screening indicators."
}
}
}
},
"cost_usdc": {
"type": "number",
"description": "Actual USDC charged for this call."
},
"valid_count": {
"type": "number",
"description": "Number of valid IBANs."
}
}
}
}
},
"x402Version": 2
}Captured payload 3 of 3
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xD13bD0A4120BA301125290e5cc0c7EFD4CB40a55",
"amount": "20000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
],
"resource": {
"url": "https://api.ibanforge.com/v1/iban/compliance",
"tags": [
"iban",
"bic",
"sepa",
"compliance",
"banking"
],
"iconUrl": "https://ibanforge.com/logo.svg",
"mimeType": "application/json",
"description": "Pre-flight compliance triage on an IBAN before a SEPA / cross-border payment: sanctions screening (OFAC), FATF jurisdiction flag, SEPA Instant reachability, VoP (EU 2024/886) participant. Returns risk_score 0-100. Informational, not a regulated AML/CFT product. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping) · OFAC + FATF + SEPA + VoP · weekly refresh · v1.4.4.",
"serviceName": "IBANforge"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"iban": "CH1000230000000012345"
},
"type": "http",
"method": "GET",
"schema": {
"type": "object",
"required": [
"iban"
],
"properties": {
"iban": {
"type": "string",
"maxLength": 34,
"minLength": 15,
"description": "IBAN to triage."
}
}
},
"bodyType": "json",
"discoverable": true
},
"output": {
"type": "json",
"example": {
"bic": {
"city": "Zürich",
"code": "UBSWCHZH",
"bank_name": "UBS Switzerland AG"
},
"iban": "CH1000230000000012345",
"meta": {
"scope": "bank_bic_only"
},
"valid": true,
"country": {
"code": "CH",
"name": "Switzerland"
},
"compliance": {
"vop": {
"status": "not_found",
"participant": false
},
"flags": [
"no_vop"
],
"sanctions": {
"fatf_status": "member",
"matched_lists": [],
"bank_sanctioned": false,
"country_sanctioned": false
},
"risk_level": "low",
"risk_score": 5,
"reachability": {
"sct": true,
"sdd": true,
"sepa_instant": true
}
},
"_example_notice": "ILLUSTRATIVE SAMPLE — these are demo values for a fixed record, NOT the data for the resource you requested. Do not report them to a user. Authenticate (Authorization: Bearer ifk_...) or pay via x402 to get the real response."
}
}
},
"schema": {
"properties": {
"input": {
"required": [
"method"
],
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
}
}
}
}
},
"bodyType": "json",
"inputSchema": {
"type": "object",
"required": [
"iban"
],
"properties": {
"iban": {
"type": "string",
"maxLength": 34,
"minLength": 15,
"description": "IBAN to validate. Spaces and lowercase accepted. Example: CH1000230000000012345"
}
}
},
"discoverable": true,
"outputSchema": {
"type": "object",
"properties": {
"bic": {
"type": "object",
"properties": {
"city": {
"type": "string"
},
"code": {
"type": "string"
},
"bank_name": {
"type": "string"
}
}
},
"iban": {
"type": "string"
},
"meta": {
"type": "object",
"properties": {
"scope": {
"type": "string"
},
"sources": {
"type": "string"
},
"disclaimer": {
"type": "string"
},
"fatf_as_of": {
"type": "string"
},
"sanctions_as_of": {
"type": "string"
},
"country_risk_as_of": {
"type": "string",
"description": "Year-month the editorial country-risk axis was last reviewed. risk_indicators.country_risk is a SEPARATE axis layered on top of fatf_status, not a restatement of it: the two can disagree on a country by design."
},
"country_risk_scope": {
"type": "string"
}
}
},
"valid": {
"type": "boolean"
},
"country": {
"type": "object",
"properties": {
"code": {
"type": "string"
},
"name": {
"type": "string"
}
}
},
"compliance": {
"type": "object",
"properties": {
"vop": {
"type": "object",
"properties": {
"status": {
"enum": [
"active",
"pending",
"inactive",
"not_found"
],
"type": "string"
},
"participant": {
"type": "boolean"
}
}
},
"flags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Risk flags, e.g. sanctioned_country, sanctioned_bank, fatf_grey_list, emi_issuer, test_bic, no_sepa_instant, no_vop."
},
"sanctions": {
"type": "object",
"properties": {
"fatf_status": {
"enum": [
"member",
"grey_list",
"black_list",
"non_member"
],
"type": "string"
},
"matched_lists": {
"type": "array",
"items": {
"type": "string"
}
},
"bank_sanctioned": {
"type": "boolean"
},
"country_sanctioned": {
"type": "boolean"
}
}
},
"risk_level": {
"enum": [
"low",
"medium",
"elevated",
"high",
"critical",
"unassessable"
],
"type": "string",
"description": "unassessable = the IBAN failed validation, no screening was possible. Never treat it as low."
},
"risk_score": {
"type": [
"number",
"null"
],
"maximum": 100,
"minimum": 0,
"description": "null when the IBAN did not validate: there was nothing to score."
},
"reachability": {
"type": "object",
"properties": {
"sct": {
"type": "boolean"
},
"sdd": {
"type": "boolean"
},
"sepa_instant": {
"type": "boolean"
}
}
}
}
}
}
}
}
},
"x402Version": 2
}Can I trust it score from our own monitoring
score from our own monitoring
88/100 Solid
#17 of 138 in Verification. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 99.9% uptime 30d
- Compliance
- A 14/14 checks pass
- Price
- $0.002 to $0.02 p16 in Verification
- Risk
- clean no risk flag
- Traction
- $0.008 30d 2 buyers, top buyer 62% (address, not entity)
14/14 compliance checks
- 402 payload captured
- accepts[] array present
- payTo address recoverable
- payTo at accepts[0].payTo (conformant shape)
- payTo is a valid on-chain address
- atomic price declared
- atomic price in a sane range
- asset (token) address declared
- network resolves to CAIP-2
- payment scheme declared
- served over HTTPS
- declares the current x402 version (2)
- EIP-712 domain parameters present on every EVM entry
- x402 v2 envelope delivered in the payment-required header
402 terms unchanged since 2026-08-31. Last up 2026-10-16.
── Site signals
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
How the score works
What the score read on this service: status online, 99.9% uptime 30d, 554ms response p95, x402 compliance 14 of 14, $0.002 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
It is a score inside Verification, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 138 listings, this one among them: the same 138 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
Settled via coinbase ($0.008, 2 tx). Traction is a conservative undercount; first settlement seen 2026-04-29.
All measured facts
What it does
IBAN validation and BIC/SWIFT lookup backed by primary bank registries (GLEIF, SIX, Bundesbank, EBA, Bank of England). Returns bank identity, SEPA and Verification of Payee reachability, sanctions and risk flags, Swiss clearing detail, ISO 20022 structured addresses. Pay per call in USDC via x402, no account needed. MCP server available for AI agents.
IBANforge is a listed x402 Verification API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.
Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.
Page rendered at . This response time is separate from the observation and computation times attached to each measurement.
Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.
Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.
Observed daily coverage: 2026-09-17 to 2026-10-16 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Latest settlement in the assessment: . Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.
Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.
x402 List home · Services · Verification
- uptime · latest daily rollup
- 100%
- uptime 7d
- 100%
- uptime 30d
- 99.9%
- uptime 90d
- 99.8%
- response p95
- 554ms
- avg response
- 445ms
- total checks
- 2,773
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
- price (min)
- $0.002
- price (max)
- $0.02
- category percentile (min)
- p16 in Verification
- category percentile (max)
- p33 in Verification
- endpoints / prices
- 3 / 3
- model
- tiered
- stability
- 100%
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
- domain age
- 195d
- registrar
- Infomaniak Network SA
- hosting
- custom
- domain created
- 2026-04-01
Identity facts, not a risk score.
- assessment volume 30d
- $0.008
- exact assessment volume 30d (USD)
- 0.008
- assessment recorded at (UTC)
- 2026-10-15T23:03:02.687Z
- buyers 30d
- 2
- settlements 30d
- 2
- measured since
- 2026-04-29 (start of our harvest window)
- last settlement
- 2026-10-14
- top buyer share
- 62% of 30d volume (address, not entity)
- top 3 buyers share
- 100% of 30d volume (addresses, not entities)
- concentrated volume
- no
- trend 7d vs 30d
- 1.61x the 30d daily rate
- networks
- eip155:8453
- volume all-time
- $0.27
- settlements all-time
- 48
- median settlement 30d
- $0.004
- max settlement 30d
- $0.005
Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.
Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.
Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.
- member since
- 2026-08-31
Recent checks
| Checked at (UTC) | Status | HTTP | Response | Endpoints |
|---|---|---|---|---|
| Online | 402 | 222ms | 3 | |
| Online | 402 | 238ms | 3 | |
| Online | 402 | 334ms | 3 | |
| Online | 402 | 299ms | 3 | |
| Online | 402 | 229ms | 3 | |
| Online | 402 | 588ms | 3 | |
| Online | 402 | 436ms | 3 | |
| Online | 402 | 295ms | 3 | |
| Online | 402 | 326ms | 3 | |
| Online | 402 | 320ms | 3 | |
| Online | 402 | 192ms | 3 | |
| Online | 402 | 204ms | 3 | |
| Online | 402 | 370ms | 3 | |
| Online | 402 | 277ms | 3 | |
| Online | 402 | 229ms | 3 | |
| Online | 402 | 240ms | 3 | |
| Online | 402 | 249ms | 3 | |
| Online | 402 | 119ms | 3 |
Changes0 in 30d
No changes recorded in the last 30 days.
Over time
On-chain volume daily snapshots, USD 30d: $0.008, peak $0.01 on 09-29
volume no data in the payload
Distinct buyers per dayDistinct buyers per day
Uptime 4 of 29 completed days below 100%
uptime below 100%, to scale
- Volume 30d
- $0.008
- Uptime
- 4 of 29 completed days below 100%
More charts
Response time daily average, ms min 298ms, avg 446ms, max 641ms
09-17 to 10-16* UTC
Scores over time
x402 compliance low 14/14, high 14/14
09-17 to 10-16* UTC
Price percentile in Verification own low to high; exact values below
09-17 to 10-16* UTC
Site signals present (of 6) own low to high; exact values below
09-17 to 10-16* UTC
Scores: one day per column, 09-17 to 10-16*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.
Each series spans only the dates it has data for. Every series is also served as JSON at /api, /scores, /volume and /buyers.
Values
* today so far, partial (UTC).
The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.
Daily snapshot total, 30d: $0.01, peak $0.01 on 09-29. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.
Daily address snapshots: 2026-09-17 to 2026-10-16 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here. † marks a recorded $0.00 with settlements.
Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.
Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.
| Day | Volume | Buyers | Settlements | Uptime | Response | Compliance | Price percentile | Site signals |
|---|---|---|---|---|---|---|---|---|
| 2026-09-17 | no data | no data | no data | 100% | 423.76ms | 14/14 | p13 | 4/6 |
| 2026-09-18 | no data | no data | no data | 100% | 641.42ms | 14/14 | p13 | 4/6 |
| 2026-09-19 | no data | no data | no data | 100% | 376.61ms | 14/14 | p13 | 5/6 |
| 2026-09-20 | no data | no data | no data | 100% | 399.02ms | 14/14 | p13 | 5/6 |
| 2026-09-21 | no data | no data | no data | 100% | 572.69ms | 14/14 | p15 | 5/6 |
| 2026-09-22 | no data | no data | no data | 100% | 608.46ms | 14/14 | p15 | 5/6 |
| 2026-09-23 | no data | no data | no data | 100% | 503.50ms | 14/14 | p14 | 5/6 |
| 2026-09-24 | no data | no data | no data | 100% | 461.82ms | 14/14 | p14 | 5/6 |
| 2026-09-25 | no data | no data | no data | 98.89% | 451.88ms | 14/14 | p14 | 5/6 |
| 2026-09-26 | no data | no data | no data | 100% | 550.97ms | 14/14 | p15 | 5/6 |
| 2026-09-27 | no data | no data | no data | 100% | 493.72ms | 14/14 | p14 | 5/6 |
| 2026-09-28 | no data | no data | no data | 98.89% | 540.22ms | 14/14 | p14 | 5/6 |
| 2026-09-29 | $0.01 | 1 | 1 | 100% | 453.26ms | 14/14 | p15 | 5/6 |
| 2026-09-30 | no data | no data | no data | 98.89% | 531.33ms | 14/14 | p15 | 5/6 |
| 2026-10-01 | no data | no data | no data | 98.89% | 529.93ms | 14/14 | p15 | 5/6 |
| 2026-10-02 | no data | no data | no data | 100% | 435.47ms | 14/14 | p15 | 5/6 |
| 2026-10-03 | no data | no data | no data | 100% | 512.77ms | 14/14 | p15 | 5/6 |
| 2026-10-04 | no data | no data | no data | 100% | 414.88ms | 14/14 | p15 | 5/6 |
| 2026-10-05 | no data | no data | no data | 100% | 361.02ms | 14/14 | p15 | 5/6 |
| 2026-10-06 | no data | no data | no data | 100% | 459.52ms | 14/14 | p15 | 5/6 |
| 2026-10-07 | no data | no data | no data | 100% | 369.24ms | 14/14 | p15 | 5/6 |
| 2026-10-08 | no data | no data | no data | 100% | 381.64ms | 14/14 | p15 | 5/6 |
| 2026-10-09 | no data | no data | no data | 100% | 373.11ms | 14/14 | p15 | 5/6 |
| 2026-10-10 | no data | no data | no data | 100% | 402.42ms | 14/14 | p15 | 5/6 |
| 2026-10-11 | no data | no data | no data | 100% | 422.03ms | 14/14 | p15 | 5/6 |
| 2026-10-12 | no data | no data | no data | 100% | 405.27ms | 14/14 | p15 | 5/6 |
| 2026-10-13 | no data | no data | no data | 100% | 332.42ms | 14/14 | p15 | 5/6 |
| 2026-10-14 | $0.00 recorded† | 1 | 1 | 100% | 364.14ms | 14/14 | p16 | 5/6 |
| 2026-10-15 | no data | no data | no data | 100% | 297.72ms | 14/14 | p16 | 5/6 |
| 2026-10-16* | no data | no data | no data | 100% | 319.25ms | no data | no data | no data |
Alternatives in Verification
5 of 137 other ranked services in Verification, ordered by the same measured score.
Own this service?
Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.
Update this listingEarn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.
Verify this service ($0.25)Embed a badge
HTML
<a href="https://x402-list.com/services/ ibanforge? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ ibanforge.svg" alt="IBANforge listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ ibanforge? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ ibanforge? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ ibanforge.svg? data=uptime" alt="IBANforge uptime on x402-list" height="28"> </a>
Delisting
To request delisting, email info@x402-list.com or update your listing at /services/ibanforge/update.