Guides

IBAN, BIC/SWIFT and SEPA Guides

Learn how IBAN, BIC/SWIFT, SEPA, checksums, and transfer details work. The guides keep format-validation limits and browser-local privacy visible.

Payment-code guides

Start with the topic that matches the detail you are reviewing. Each guide gives plain-language context and practical limits.

What Is an IBAN?

Understand the parts of an IBAN and how digital and print formats are used in payment details.

Useful for

People reviewing invoices, payment forms, international account details, and software fields that ask for an IBAN.

Read guide

What Is a BIC/SWIFT Code?

Read the 8 or 11 character BIC structure and understand how business party prefix, country code, suffix, and branch identifier segments fit together.

Useful for

Users checking bank identifier fields on invoices, payment instructions, vendor records, and international transfer forms.

Read guide

What IBAN Validation Can and Cannot Check

Understand which IBAN format checks are useful and why they still cannot verify a real bank account or recipient.

Useful for

People reviewing payment forms, invoices, vendor records, and software validation results before using real payment details.

Read guide

Why a Valid IBAN Does Not Mean a Real Account

See the difference between structural IBAN validation and real-world bank or account verification.

Useful for

Anyone reviewing invoice details, vendor bank details, customer forms, or payment instructions and wondering what a valid result really means.

Read guide

BIC Format and Bank Directory Limits

Understand BIC/SWIFT structure and the limits of format-only checks without licensed bank directory data.

Useful for

Users reviewing BIC/SWIFT fields on invoices, vendor records, payment forms, and developer test cases.

Read guide

SEPA Country Status Limitations

Understand why SEPA country status is useful context but not account-level or bank-level payment verification.

Useful for

Users checking European payment context before reviewing IBANs, invoices, or payment provider requirements.

Read guide

Browser-Local Payment Code Checks

Understand BankCodeKit's local-first privacy model for payment-code checks and why sensitive values should not be sent to analytics, ad scripts, logs, URLs, or email.

Useful for

Users and teams that want quick payment-code checks without uploading sensitive payment details or creating an account.

Read guide

IBAN vs BIC/SWIFT

A practical comparison of account-number format and bank-identifier format in payment details.

Useful for

Freelancers, accountants, developers, and payment operations teams explaining why forms may ask for both values.

Read guide

SEPA vs SWIFT

A careful explanation of SEPA country scope and BIC/SWIFT code context without oversimplifying payment rules.

Useful for

Users choosing which payment details to request for European and international bank transfers.

Read guide

How IBAN Checksum Validation Works

Understand the plain-English checksum flow that helps catch many IBAN typing mistakes.

Useful for

Developers, QA testers, finance operations teams, and curious users who want to understand IBAN validation results.

Read guide

International Bank Transfer Checklist

A practical, non-advisory checklist for reviewing international bank transfer details before sending money.

Useful for

Freelancers, accountants, small businesses, and operations teams preparing or reviewing payment instructions.

Read guide

SEPA Countries

Understand country-level SEPA lookup and how it relates to IBAN and payment-code review.

Useful for

Users checking whether a country or territory appears in SEPA reference data before reviewing IBAN and BIC details.

Read guide

IBAN Print Format vs Digital Format

Compare readable spaced IBANs with compact digital IBANs used by payment forms and validation tools.

Useful for

People copying IBANs from invoices, PDFs, emails, bank letters, country pages, and payment forms.

Read guide

Common IBAN Typing Mistakes

Spot common IBAN typing and copy-paste mistakes before using payment details elsewhere.

Useful for

People entering invoice payment details, reviewing vendor records, checking customer payment forms, or testing IBAN validation flows.

Read guide

BIC8 vs BIC11

Understand 8-character and 11-character BIC/SWIFT format patterns without overclaiming directory or network verification.

Useful for

People reviewing BIC/SWIFT fields on invoices, vendor records, payment forms, and software test cases.

Read guide

Payment Reference on Invoices

Understand payment references as invoice matching text, not proof that payment details are correct.

Useful for

Freelancers, small businesses, finance teams, and operations users preparing or reviewing invoice payment details.

Read guide

How to Review Bank Transfer Details

A practical review checklist for bank transfer details, focused on format checks and verification reminders.

Useful for

People preparing invoice payments, vendor records, customer refunds, or transfer details before using a bank or payment provider workflow.

Read guide

How to Check an IBAN Before an Invoice Payment

A practical invoice-payment review flow that keeps IBAN format checks separate from real payment verification.

Useful for

People reviewing invoice payment details before copying an IBAN, BIC, amount, currency, and reference into a bank or payment provider workflow.

Read guide

What to Do If an IBAN Checksum Fails

A careful checklist for checksum failures that focuses on re-checking the source value, not guessing payment details.

Useful for

People pasting IBANs from invoices, emails, PDFs, bank letters, spreadsheets, or payment forms and seeing a failed checksum result.

Read guide

Why Bank Transfer Details Should Be Confirmed Through a Trusted Channel

Understand why format checks do not replace trusted confirmation for changed or unexpected bank transfer details.

Useful for

People reviewing invoices, vendor bank changes, emailed payment instructions, payment references, or copied transfer details.

Read guide

CSV IBAN Validation Safety

Practical safety notes for pasted IBAN lists, validation results, and CSV exports from browser-local checks.

Useful for

People checking multiple IBAN values from spreadsheets, payment batches, vendor lists, customer records, or test datasets.

Read guide

Payment Details Copy-Paste Safety

A practical guide to reviewing copied payee, IBAN, BIC, amount, currency, and reference details before using them elsewhere.

Useful for

People copying payment details from invoices, PDFs, emails, accounting tools, spreadsheets, or generated payment-detail blocks.

Read guide

Practical review guides

Use these guides when copying payment details from invoices, PDFs, vendor records, or payment forms. They keep format checks separate from real payment verification.

Guides on validation limits and privacy

These guides explain what BankCodeKit checks can and cannot prove. Read them before relying on a format result in a payment workflow.

Before sending a payment

Use BankCodeKit guides and tools to catch format issues and understand payment-code terms. Before sending money, verify details through a trusted bank, payment provider, invoice issuer, or recipient channel.

  • Confirm the payee name and payment reference.
  • Check the IBAN and BIC/SWIFT format when those fields are required.
  • Confirm amount, currency, fees, and transfer method.
  • Do not rely on format validation as proof of account ownership.
  • Do not rely on format validation as proof of payment readiness or payment success.

How these guides relate to the tools

Guides explain the concepts behind the tools. The tools perform browser-local checks such as IBAN normalization, checksum validation, BIC parsing, and country-level SEPA lookup.

FAQ

Do these guides replace bank instructions?

No. Guides explain payment-code formats and validation limits. Real payment details should be verified with your bank, payment provider, invoice issuer, or recipient.

Do BankCodeKit tools confirm account ownership?

No. BankCodeKit validates format and reference data only. It does not confirm account existence, account ownership, bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.

Are values entered into tools uploaded?

The tool design is browser-local for user-entered payment details. Values should not be sent to servers, analytics, ad scripts, or URLs.