Free QR generator — no registration

Create an EPC QR code for a SEPA credit transfer

Prepare beneficiary, IBAN, optional BIC, EUR amount, purpose and reference in the EPC QR format used by compatible European banking apps.

  • SEPA credit transfer data
  • EUR only
  • Maximum 331 encoded bytes

Learn more

Why use EPC QR / GiroCode instead of asking the payer to type everything?

An IBAN is long and invoice references are easy to transpose. EPC QR lets a compatible banking app read the payment instruction while leaving the final transfer review and authorization with the payer.

Avoid IBAN transcription errors

The complete validated IBAN is scanned rather than typed.

Carry invoice context

Add a purpose and one structured or unstructured reference according to your billing workflow.

Reach several SEPA markets

One EPC format is supported by compatible apps across multiple European countries.

Inside the QR code

What is stored in a EPC QR / GiroCode payment symbol?

EPC QR is a line-based UTF-8 payload beginning BCD and version 002. It describes an SCT beneficiary, IBAN and optional EUR amount under the European Payments Council guidelines.

The code starts with BCD and version 002

These lines identify the EPC QR format and current character-set scheme.

Only SEPA credit transfer in EUR is covered

Do not use this form for card payments, other currencies or instant-payment guarantees.

BIC requirements vary

BIC is optional in many SEPA cases but may still be required by an app or for particular destinations.

Choose one reference method

A structured creditor reference and unstructured remittance text must not both be populated in a compliant instruction.

Capacity is deliberately limited

The complete service data must not exceed 331 bytes and should use error correction M.

EPC payload example

DE IBAN · EUR 125.00 · invoice reference — BCD\n002\n1\nSCT\nCOBADEFFXXX\nExample Company\nDE89...\nEUR125.00 — A compatible European banking app opens a prepared SEPA transfer.

Check before publishing

  • Validate the IBAN and country before publishing.
  • Use EUR only.
  • Ask the receiving bank whether BIC is required.
  • Keep the beneficiary within 70 characters.
  • Shorten remittance text if the payload exceeds 331 bytes.
  • Test with the banking apps used by the intended audience.

Checks to make before publishing a EPC QR / GiroCode code

EPC QR saves typing, but bank support and national implementation details still need testing.

Use invoice-source data

Copy beneficiary and IBAN from the current invoice or accounting system.

Decide on the reference type

Use either a structured RF reference or unstructured remittance text.

Keep content compact

Short labels create a less dense QR and improve small-print scanning.

Print EUR beside the code

Make the currency explicit for the payer.

Test regional bank apps

Support is not identical across all SEPA institutions.

Features

Features

Scheme-specific validation

Account identifiers, amount formats, references and field lengths are checked for the selected payment standard.

Generated locally

The payment payload and barcode are created in the browser; the generator does not move money or register an account.

PNG and SVG exports

Download a raster image for everyday use or a scalable vector for invoices and high-quality print.

Protected fixed formats

Standards with prescribed rendering disable incompatible color, logo, shape and error-correction controls.

Optional payment context

Where the scheme permits it, prepare an amount, reference, due date or message to reduce payer entry.

Verification remains visible

The workflow reminds the payer to compare the beneficiary and amount in a compatible banking app.

Advantages & Limitations

Advantages

  • Covers many SEPA markets.
  • Reduces IBAN and reference entry.
  • Human-readable line format.
  • Optional amount permits reusable instructions.

Limitations

  • EUR and SCT only.
  • Not every European banking app supports it.
  • Does not confirm instant settlement.
  • 331-byte limit constrains long remittance text.

How EPC QR / GiroCode works

Create, scan and verify a EPC QR / GiroCode payment

An IBAN is long and invoice references are easy to transpose. EPC QR lets a compatible banking app read the payment instruction while leaving the final transfer review and authorization with the payer.

Enter beneficiary and IBAN

Use current SEPA receiving details.

Add EUR and reference

Prepare an optional amount and one compatible remittance reference.

Test in target bank apps

Verify the beneficiary, IBAN, currency and amount.

Use cases

Use cases

European invoices

Move SEPA payment fields from paper into a bank app.

Membership fees

Use a repeatable beneficiary with a payer-specific reference.

Donations

Leave amount empty when supporters choose EUR.

Cross-border suppliers

Reduce manual IBAN entry across SEPA markets.

Frequently asked questions

Is GiroCode the same as EPC QR?

GiroCode commonly refers to QR payment codes implementing the EPC SCT data guidelines.

Can I use CHF or GBP?

No. This EPC format is for EUR SEPA credit transfers.

Is BIC required?

Often not within SEPA, but requirements and app behavior can vary.

Why is content limited to 331 bytes?

The EPC guideline limits payload size to preserve practical QR density and interoperability.

Create a EPC QR / GiroCode payment code

Prepare a SEPA transfer and test it with the European banking apps your customers actually use.

Create an EPC QR code