IBAN Validator

About Payvaly

Payvaly is an independent micro-tool site built to help people catch formatting mistakes in IBAN and card numbers before those values reach a payment or banking workflow.

Who built it

Payvaly is built and maintained by an independent development team with a background in fintech integrations and payment systems. The validation logic — MOD-97 for IBAN, Luhn algorithm for card numbers — follows published international standards (ISO 13616, ISO/IEC 7812). It is not operated by a bank, card network, payment processor, or government body. All results are structural and informational only. Bug reports and validation disagreements are reviewed within 48 hours.

What Payvaly does

  • Runs all validation entirely in your browser — no IBAN or card number is ever sent to our servers.
  • Checks IBAN structure, country code, length, and MOD-97 checksum.
  • Checks card number format, network pattern, and Luhn checksum.
  • Keeps the experience simple for quick validation and QA work.

Our guides

In-depth guides on IBAN formats, card validation, and common errors:

What Payvaly does not do

  • It does not verify bank accounts, account ownership, or payment eligibility.
  • It does not verify card status, available funds, expiry date, or CVV.
  • It does not claim authority on behalf of banks or payment networks.

Transparency

  • Validation logic is informational and format-based.
  • If a result matters financially, confirm it with the recipient or issuing institution.
  • In-depth technical guides covering IBAN formats, card validation, and common errors are available in our guides section.
  • Questions, corrections, or bug reports can be sent to contact@payvaly.com.

How validation works technically

Every check runs entirely in your browser using JavaScript. No IBAN or card number is ever transmitted to our servers, stored in a database, or accessible to any third party — not even to us. This is verifiable: the page has no form submission and makes no network requests during validation.

Contact

For bug reports or validation disagreements, include the country, the expected outcome, and a safe masked example when possible. Do not send full sensitive financial data. We typically respond to bug reports within 48 hours.