Elysia Tools
Navigation
Workflow Playbook
Check credit-card, IBAN/SWIFT, EU VAT, and US EIN strings against syntax, length, country rules, and applicable checksums without treating a format pass as proof of account or registration status.
Hubs
A billing or onboarding field should name the identifier family before validation starts. Preserve the original string and its source label, then note the expected country or EU member state when available. This prevents a plausible-looking EIN, VAT number, card number, or bank code from being sent through the wrong rule set.
The validators can handle common presentation differences, but normalization is not a license to delete meaningful characters. Keep a raw value beside the normalized candidate, retain country prefixes, and record whether spaces, hyphens, or case were changed. A frequent failure is a copied value with an extra label, a missing prefix, or a separator removed from the wrong position.
Use the family-specific output to review length, alphabet, prefix, country pattern, and any checksum or check digit. EU VAT rules vary by member state; IBAN and SWIFT/BIC have different structures; and a US EIN has a nine-digit pattern without this workflow proving current IRS assignment. A card-format pass likewise does not authorize a transaction.
Accept the value for the next formatting-dependent step only when the relevant checks pass and the record includes the raw input, normalized value, selected family, and warnings. If the business question is whether an account exists, a taxpayer is registered, a card can be charged, or funds are available, start a separate authorized verification workflow.
Workflow playbook
Inspect the source field and choose one supported family before editing the value. Use the four validators as a routing set, not as a claim that every identifier can be checked by every tool.
Retain the raw string, then apply only documented trimming, case, space, or hyphen handling for the selected family. Preserve country prefixes and meaningful characters so a later reviewer can reproduce the check.
Review the returned length, structure, country or prefix details, and applicable checksum result. For an EU VAT value, confirm that the detected or selected member state matches the source; for an EIN, treat prefix and nine-digit structure checks as format rules rather than a registry lookup.
Store the normalized candidate, validator output, warnings, and correction reason. Mark the value as format-accepted only when the relevant checks pass, then route any account, registration, authorization, or balance question to a separate approved service.
Route card data to credit-card-validator, banking data to iban-swift-validator, an EU tax number to eu-vat-validator, and a US employer number to us-ein-validator. Do not make a validator choice from a field name alone when the source is ambiguous.
Spaces and hyphens can be display characters for many card, IBAN, and EIN inputs, but the country prefix and significant letters in a VAT or bank identifier must remain intact. Keep both raw and normalized values.
Use the pass only to clear a syntax gate. If the business decision needs an active account, registered taxpayer, authorized card, or usable balance, send the value to an authorized external verification path instead.