risk data for machine payments
Endpoint
netintel.dev/iban/validate
Validate any IBAN offline — mod-97 check digits, per-country structure, bank/branch extraction, and pretty formatting for ~80 countries — deterministic, instant, no upstream. A structurally invalid IBAN is a real answer: valid:false + findings naming exactly what failed. Pass iban as ?iban= (GET) or a JSON body (POST).
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 4h ago | 402 | 160 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.005000 | clean |
| 4d ago | 402 | 192 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.005000 | clean |
| 4d ago | 402 | 284 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.005000 | clean |
Reference
| URL | https://netintel.dev/iban/validate |
| Sources | well-known |
| Recipient per catalogue | 0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.