Verify a supplier before you pay them

Before a first transfer, three questions decide: does this company exist and is it still trading, is its VAT number valid today, and is this IBAN at least structurally plausible and attached to a known bank? The /v1/facturation/dossier route answers all three in one call and returns a closed-list verdict, not prose to interpret.

See a real response (free) Get the quote for /v1/facturation/dossier

What the check catches, and what it cannot catch

The pret_a_facturer verdict is deterministic: the same inputs always give the same output, and every refusal carries a reason drawn from a closed list. That is what lets you wire it into an approval workflow without a human re-reading each response.

• Deregistered or ceased company still invoicing: caught from the registry's administrative status.
• Invalid or revoked VAT number: checked live against VIES, with the consultation identifier kept as proof.
• Malformed IBAN, or one whose check digits do not add up: rejected before the transfer.
• Bank unknown to official registries: the bank code is looked up in public reference data (ACPR/REGAFI in France, NBB in Belgium, OeNB in Austria, Bundesbank in Germany, the Dutch BIC list).

The IBAN check is a form check — ISO 13616 structure, mod-97 key digits, bank identified against official registries. It is not a payee verification: neither the account holder's name nor the account's existence is checked, and the response says so (verification_titulaire: non_disponible). Against bank-details fraud it reduces the risk; it does not remove it.

A VIES outage never yields a false “invalid”

This is the most important design point of this route, and what separates a usable check from a dangerous one. When the European VIES service is unavailable — which happens regularly, member state by member state — the response returns unavailable, never invalid. A fully compliant supplier therefore cannot be blocked by an outage that is not theirs.

Consequence for your workflow: treat unavailable as “retry later”, not as a refusal. The reason is explicit precisely so your code can tell the difference.

The data behind the verdict

The identity check draws on 29,922,486 French company numbers, of which 16,638,954 are active and 8,937,306 are active legal entities, plus 43,896,818 establishments. The identity stock is re-ingested from official publications; the date of the last successful load is shown in the footer.

The full check's price is the /v1/facturation/dossier line in the table below. At that price, checking every new supplier costs less than reversing a single transfer.

How you pay

Every route is paid per call, in USDC or EURC on the Base network, over the x402 protocol: no account to create, no API key, no subscription. The first call returns a 402 quote your client settles, then replays the call. A failed call is never billed.

Would you rather have a euro invoice and prepaid credits? That is in preparation, and we will not announce a date until it is open. Write to contact@sirenic.eu and we will let you know when it opens.

Paid responses are Ed25519-signed: you can later prove what was served to you, and when. The whole catalogue is free to read in the OpenAPI document and in llms.txt.

One call, end to end

# Client x402 (npm) — le devis 402 est réglé et l'appel rejoué automatiquement
npx x402-fetch https://api.sirenic.eu/v1/entreprise/552032534

# Ou en MCP, dans Claude Code / Cursor
claude mcp add --transport http sirenic https://api.sirenic.eu/mcp

Routes used and pricing

The IBAN check is not a payee verification: neither the account holder's name nor the account's existence is checked (verification_titulaire: non_disponible).

Sirenic is not an accredited French e-invoicing platform (PDP), never accesses the central directory, and neither issues, transmits nor routes any invoice.

Frequently asked questions

Does this replace the payee verification required for instant payments?

No, and the response says so itself. We check the IBAN's form and identify the bank; we verify neither the holder's name nor the account's existence. Payee verification is a service only your payment provider can deliver, because only they can query the account-servicing institution.

Do I need an account or an API key?

No. The route answers 402 with a quote, your client settles in USDC or EURC on Base, then replays the call. No sign-up, no prior contract, no IP address to declare.

What if the supplier is established outside France?

Use /v1/eu/facturation/dossier, which covers Belgium (mandate live since 1 January 2026, including Peppol reachability) and Poland (KSeF, including the official White List check: is the IBAN declared by the taxpayer?). Paying an undeclared account above PLN 15,000 costs the buyer the VAT deduction and triggers joint liability.

Take it further

No account to create, no key to request: the first step is free and shows you exactly what you would be buying.

See a real response (free) Get the quote for /v1/facturation/dossier Read the route reference Get notified about euro packs

Read next

• Cross-check the identifiers printed on an invoice you received
• Preparing supplier master data for the French e-invoicing mandate
• Automating business verification (KYB)