All The Validators logoAll The Validators

data validator

SWIFT/BIC Validator

Validate SWIFT/BIC codes for length and structure locally to catch typos before wires or payouts.

Results

Processing…
Status
Processing...
Details
Processing...

How to use this validator

  1. Paste the SWIFT/BIC code.
  2. Run validate to check length and segment patterns.
  3. If invalid, correct the bank/country/location characters or length and re-validate.

Rules & checks

Checks for 8- or 11-character length.

Validates bank code (4 letters), country code (2 letters), location (2 alphanumeric), and optional branch (3 alphanumeric).

Uppercases input and strips whitespace before validation.

No network calls; nothing is stored or sent.

Inputs explained

  • SWIFT/BIC

    Paste the 8- or 11-character code. Use uppercase A–Z/0–9; avoid spaces. Use test data in non-production.

When to use it

  • Validate SWIFT/BIC in payout or wire instructions
  • QA financial forms, CSV imports, and support tickets
  • Check supplier bank details before processing payments

Common errors

  • Not 8 or 11 characters
  • Lowercase or invalid characters (must be A–Z/0–9)
  • Typos in bank or country code segments

Limitations

  • Structure-only; does not confirm bank/branch existence or ownership.
  • No bank metadata lookup or enrichment.
  • Use PSP/bank checks for production payouts and KYC/ownership validation.

Tips

  • Normalize to uppercase and remove spaces before submission.
  • Even with a valid format, confirm via your PSP/bank for live transfers.
  • Pair with IBAN and routing validators when collecting full bank details.

Examples

Valid 8-char

  • DEUTDEFF -> Valid

Valid 11-char

  • DEUTDEFF500 -> Valid

Invalid length

  • DEUTDEFFF1234 -> Invalid (too long)

Invalid chars

  • DEUTD!FF -> Invalid (non-alphanumeric)

Deep dive

This SWIFT/BIC validator checks 8/11-character codes for proper bank, country, and location segments entirely in your browser.

Use it to catch typos before wiring funds, then rely on your payment provider for live verification and ownership checks.

FAQs

Is my SWIFT/BIC uploaded or stored?
No. Validation is local and clears on refresh.
Does this verify the bank or branch exists?
No. It checks format only. Use your PSP/bank for definitive validation.
Can I include spaces or lowercase?
We uppercase and strip spaces, but stick to A–Z/0–9 for best results.

Related validators

data

IBAN Validator

Validate IBAN structure and checksum locally to catch typos before payouts—no data leaves your browser.

data

Routing Number Validator

Validate US routing numbers (ABA) with checksum math locally to catch typos before payouts.

security

Credit Card Validator

Run a local Luhn check to confirm card number format before hitting payment APIs—no data leaves your browser.

security

API Key & Token Validator

Check common API key/token formats (Stripe, GitHub, AWS, OpenAI, etc.) locally.

security

JWT Signature Validator (HS256)

Validate HS256 JWT signatures with a shared secret, fully client-side—no tokens or secrets ever leave your browser.

SWIFT/BIC codes are processed only in your browser. Nothing is sent, logged, or stored.

Structure validation only; does not verify bank ownership or branch existence.