Integrate payments and related Stripe operations.
US cards:2.9% + USD 0.30/transactionUsage-based
Market / IBANforge
External service · publisher supplied metadata
IBANforge
Source and listing identity
Source: x402 Bazaar
Listing ID: x402:765fd1d77d2145f6e015bd2abfccf0663677a6225e84b7ace3a6b809db3facbd
Topic categories are inferred from listing text. Prices are source declarations; provider terms take precedence.
A registry entry or matching company name does not establish product authorship. Compare record IDs before treating similar titles as one product.
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.5.0.
Listing completeness · 80/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 0/15 · Missing or insufficient
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 0/5 · Missing or insufficient
Evaluated 2026-10-30 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
x402 resource
https://api.ibanforge.com/v1/iban/validateRead the current payment requirements with a compatible client before authorizing a call.
Categories and declared capabilities
Topic categories are derived from publisher text for discovery, not independently verified capabilities.
The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.
Evidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.
The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →Related tools
Similar tasks and categories; compatibility has not been tested.
Inspect local HTML, JSON and OpenAPI files and save a diagnostic report.
Free local useSoftware licence
Create structured JSON descriptions from your documents and save the result.
Free local useSoftware licence
Analyse recorded observations and save a local report.
Free local useSoftware licence