# IBANForge IBAN Compliance Check

> IBANForge IBAN Compliance Check is a paid API for AI agents from api.ibanforge.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-13).

Runs pre-flight compliance triage on a single IBAN, returning a 0-100 risk score plus OFAC sanctions screening, FATF jurisdiction flags, SEPA Instant reachability, and VoP (EU 2024/886) participation status.

## Facts

- Endpoint: GET https://api.ibanforge.com/v1/iban/compliance
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ibanforge-iban-compliance-check-03f4549f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G5zhiO_IVU1nuOcuQIvrJ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ibanforge-iban-compliance-check-03f4549f
```

Example prompt: Before I send this payment, run a compliance check on IBAN DE89370400440532013000 — I need the risk score, OFAC sanctions status, FATF jurisdiction flag, and whether it can receive SEPA Instant.

## When to prefer this

Use this endpoint when you need a fast, multi-dimensional pre-flight compliance check on a single IBAN before initiating a SEPA or cross-border payment — specifically when you need OFAC screening, FATF jurisdiction risk, SEPA Instant reachability, and VoP participation all in one call. Prefer this over the batch endpoint when checking a single IBAN ad hoc. Use the single IBAN validation endpoint instead if you only need structural validation and bank enrichment without compliance screening.

## Known failure modes

- Invalid IBAN format returns a 400 error with a format validation message
- IBAN from an unsupported or non-SEPA country may return null for SEPA/VoP fields
- Rate limiting or quota exhaustion returns a 429 error
- Network latency beyond server-side <5ms processing not guaranteed — measure with GET /ping
- Data freshness caveat: weekly refresh means very recent sanctions additions may not be reflected

## How this service works

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.3.

## Output

Returns a JSON object containing: risk_score (integer 0-100), OFAC sanctions screening result (hit/clear), FATF jurisdiction flag (risk level of the country), SEPA Instant reachability (boolean), and VoP (EU 2024/886) participant status (boolean). Data is refreshed weekly. Response is informational and not a regulated AML/CFT determination.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "properties": {
    "method": {
     "type": "string",
     "enum": [
      "GET"
     ]
    }
   },
   "required": [
    "method"
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ibanforge-iban-compliance-check-03f4549f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.ibanforge.com](https://www.zero.xyz/host/api.ibanforge.com/llms.txt)