EU EPC QR Builder — connector documentation

MCP endpoint: https://eu-epc-qr.connectorbay.com/mcp
REST API: POST https://eu-epc-qr.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://eu-epc-qr.connectorbay.com/openapi.json
Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
Health: https://eu-epc-qr.connectorbay.com/health · Tool schemas: https://eu-epc-qr.connectorbay.com/tools.json
Publisher: Unify Dynamics LLC · connectorbay.com/eu-epc-qr · agent@connectorbay.com

What EU EPC QR Builder is for

EU EPC QR Builder turns invoice payment details into the EPC069-12 v3.1 'BCD' payload that European banking apps read to pre-fill a SEPA credit transfer. build_epc_payload assembles the payload (version 002 or 001, character set 1 to 8) from beneficiary name, IBAN, amount, purpose and one remittance reference, and refuses anything that breaks a field limit, the literal EUR amount format or the 331-byte cap. validate_epc_payload parses a pasted payload and names the broken element per line. render_epc_qr returns an SVG or PNG QR at error correction level M within QR version 13. validate_iban checks length per country from the ISO 13616 registry and the mod 97-10 check digits, make_rf_reference builds or validates an ISO 11649 creditor reference, choose_remittance_mode explains the structured versus unstructured remittance rule, and field_limits returns the element table with its source. It builds a payload only: it never initiates, sends or stores a payment, and some banking apps ignore optional fields.

Ask your assistant things like:

"Make me an EPC QR code for invoice 20260142: EUR 480.00 to my company account"
"Is this SEPA QR payload valid, and which line is wrong?"
"Should the invoice number go in the reference field or the free text?"
"Create an ISO 11649 RF creditor reference for invoice number 20260142"
"Is this IBAN well-formed before I put it on the invoice?"
"What are the maximum lengths of each field in a SEPA QR code?"

What it does

build_epc_payload: Assemble the EPC069-12 BCD payload from beneficiary name, IBAN, amount, purpose and one remittance field, enforcing field limits and the 331-byte cap.
validate_epc_payload: Parse a pasted EPC QR payload and report which EPC069-12 element each problem is in.
render_epc_qr: Render a valid EPC QR payload as SVG or PNG at error correction M, checking it fits QR version 13.
validate_iban: Check an IBAN's characters, per-country length (ISO 13616 registry) and mod 97-10 check digits before it goes into a QR.
make_rf_reference: Build an ISO 11649 RF creditor reference from a body, or validate one, for the structured remittance field.
choose_remittance_mode: Explain the EPC rule that only one of structured or unstructured remittance may be filled and which field fits what you have.
field_limits: The EPC069-12 v3.1 element list: order, mandatory or conditional flag, maximum length and content rule, plus payload limits.

Data sources

Reference data from official sources (europeanpaymentscouncil.eu, swift.com); every answer states its source, date and validity period.

What it is not

EU EPC QR Builder is independent; not affiliated with, endorsed by or operated by any government body, central bank, standards body or scheme operator. Names of rails, schemes and standards are used only to say what a tool works with. It is read-only: it never sends, pays, files or signs anything for you, and it never looks up private individuals.

Not advice. General information only, not legal, tax, accounting or payment advice. EU EPC QR Builder is an independent tool: it is not affiliated with, endorsed by or operated by any government body, central bank, standards body or scheme operator. Rates, thresholds and rules change; check the cited official source and confirm with a qualified professional before you rely on a result.

Built for: European Union. Languages: English.

Tools

Look up & validate

validate_epc_payload — Parse a pasted EPC QR payload and report which EPC069-12 element each problem is in. Use for "Is this SEPA QR text valid, and what is wrong with it?". Args: payload.

validate_iban — Check an IBAN's characters, per-country length (ISO 13616 registry) and mod 97-10 check digits before it goes into a QR. Use for "Is this IBAN well-formed before I print it on the invoice?". Args: iban.

Build & format

build_epc_payload — Assemble the EPC069-12 BCD payload from beneficiary name, IBAN, amount, purpose and one remittance field, enforcing field limits and the 331-byte cap. Use for "Build the EPC QR payload for EUR 480.00 to my company account for invoice 20260142". Args: name, iban, amount, reference, text, bic, purpose, info, version, charset.

render_epc_qr — Render a valid EPC QR payload as SVG or PNG at error correction M, checking it fits QR version 13. Use for "Give me the QR image for this payment request to print on the invoice". Args: payload, format, border.

make_rf_reference — Build an ISO 11649 RF creditor reference from a body, or validate one, for the structured remittance field. Use for "Create an ISO 11649 RF creditor reference for invoice number 20260142". Args: body, reference.

Reference & guides

choose_remittance_mode — Explain the EPC rule that only one of structured or unstructured remittance may be filled and which field fits what you have. Use for "Should the invoice number go in the reference field or in the free text?". Args: have_structured_reference, have_free_text.

field_limits — The EPC069-12 v3.1 element list: order, mandatory or conditional flag, maximum length and content rule, plus payload limits. Use for "What are the maximum field lengths in an EPC QR code?".

Conventions

Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/eu-epc-qr/support