Scope & reliance — 🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. OLO requirements are set out in EPC guidelines and national scheme rulebooks. Requirements may be updated — verify against the latest EPC documentation and relevant national CSM rules. Not a substitute for legal or compliance advice. Deterministic logic · no inference · zero PII · CC BY 4.0.

Mandate Live — SEPA OLO requirements became mandatory for EU PSPs handling cross-border payments with non-EEA legs from October 2025. Non-compliant transactions may be rejected by CSMs or the beneficiary PSP. Key obligations: (1) ISO 20022 StructuredPostalAddress on all OLO transactions, (2) BIC mandatory on SWIFT OLO transactions, (3) currency conversion disclosure (CCD) elements required where FX applies, (4) Purpose Code mandatory for many OLO transaction types.

OLO Volume Profile

Cross-Border OLO Transactions as % of Total Volume

Monthly OLO Transaction Count (estimate)

Primary OLO Payment Rail

ISO 20022 Structured Address Compliance

% of OLO transactions using StructuredPostalAddress (not unstructured)

% of OLO transactions with mandatory BIC populated

StreetName field populated separatelyNot concatenated into AddressLine — violates structured address requirement TownName field always presentMandatory in StructuredPostalAddress for OLO transactions Country code (ISO 3166-1) always present2-character country code mandatory on all OLO transactions PostCode populated where applicableRequired where jurisdiction uses postal codes Address validation in origination flowSystem validates completeness before submission to CSM Unstructured address migration project in progressActive programme to migrate legacy unstructured addresses

Purpose Code & Remittance Information

% of applicable OLO transactions with Purpose Code populated

EPC/ISO 20022 Purpose Code list implementedUsing current ExternalPurposeCode list (ISO 20022 External Code Set) Mandatory purpose code flows identifiedKnow which OLO transaction types require purpose code per receiving jurisdiction Structured remittance information usedRmtInf/Strd rather than Ustrd where invoice references present

Currency Conversion Disclosure (CCD)

FX rate disclosed to payer before authorisationPSD2 Art.45 / PSD3 equivalent — pre-transaction rate disclosure All currency conversion charges itemisedMark-up over ECB reference rate disclosed separately ISO 20022 CCD fields populated in pacs.008XchgRate, ChrgBr, and InstrAmnt fields correctly populated Post-execution statement includes CCD detailsTransaction confirmation references rate applied and charges deducted

SEPA One-Leg-Out Readiness Checker