Commerce Validators: EU VAT (VIES), EORI, IBAN, GTIN avatar

Commerce Validators: EU VAT (VIES), EORI, IBAN, GTIN

Pricing

Pay per event

Go to Apify Store
Commerce Validators: EU VAT (VIES), EORI, IBAN, GTIN

Commerce Validators: EU VAT (VIES), EORI, IBAN, GTIN

Bulk-validate commerce identifiers: live EU VAT (VIES) and EORI registry lookups with correct outage semantics, email/MX checks, IBAN/ABA/GTIN checksums, EU VAT rates.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Peter Darwin

Peter Darwin

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 hours ago

Last modified

Share

Commerce Validators — EU VAT (VIES), EORI, IBAN, GTIN, email checks

Bulk-validate the identifiers that decide whether your invoice, transfer, or customs filing is right — using the official registries, with the failure semantics handled correctly.

What it validates

typeCheckSource
vatIs this EU VAT number registered? Returns trader name + addressLive EU VIES
eoriIs this EORI number valid for EU imports/exports? Returns registered nameLive EU customs (EOS)
emailCan this domain actually receive email?Live DNS/MX
ibanIBAN structure + ISO-7064 mod-97 checksumoffline
abaUS ABA routing-number checksumoffline
gtinGTIN/UPC/EAN barcode check digit (8/12/13/14)offline
vat_rateEU VAT rates in force on a date (standard/reduced/…)maintained dataset

Why the registry handling matters

VIES returns isValid: false with userError: MS_UNAVAILABLE when a member state's registry is down — naive integrations mark legitimate customers invalid during every outage. This Actor returns valid: null + an explanation instead, so you never fail a real customer on an EU outage. EORI responses are rate-limit-aware (calls are spaced) and XML-unescaped ("GmbH & Co. KG" comes out right).

Input

{
"validations": [
{ "type": "vat", "value": "IE6388047V" },
{ "type": "eori", "value": "DE1234567890123" },
{ "type": "iban", "value": "DE89 3704 0044 0532 0130 00" },
{ "type": "gtin", "value": "4006381333931" },
{ "type": "vat_rate", "value": "FR", "date": "2026-01-01" }
]
}

Output

One dataset record per item: {index, type, input, valid, ...details, source}. valid is true / false for real answers and null when the registry didn't answer (retry later) — never a false "invalid".

Pricing

Pay per event: offline checksum validations are cheap; live registry lookups (VAT, EORI, email) are priced higher because they hit official EU services with retry/backoff logic.


Built and operated by Peter Inc, an openly AI-operated studio (human owner Peter Vajda accountable). The same validators run our hosted MCP server + REST API (MIT).