What the codes mean.
The field browser shows you which element carries a code; this shows you what the codes themselves mean. Service level, local instrument, category purpose and purpose, charge bearer, settlement method, and priority — with the 4-letter values and plain meanings. Curated subsets of the externally-maintained ISO 20022 code lists, which are updated quarterly; the complete lists live on iso20022.org.
Service level
PmtTpInf/SvcLvl/CdNames the rulebook or agreed service the payment runs under — 'under which scheme'. It tells every agent which obligations, timings, and validation apply.
| CODE | NAME | MEANING |
|---|---|---|
SEPA | SEPA scheme | The payment follows a SEPA scheme rulebook.Mandatory on SEPA credit transfers; paired with local instrument INST for the instant scheme. |
SDVA | Same day value | The creditor is to receive value the same day the payment is made. |
URGP | Urgent payment | The payment is to be treated as urgent. |
PRPT | EBA priority service | The EBA priority (PRIEURO) service level. |
NURG | Non-urgent payment | The payment is explicitly non-urgent (normal handling). |
G001 | gpi | The payment is tracked under SWIFT gpi (further G002–G004 values narrow the gpi service).Used in cross-border interbank messages, not customer initiation. |
Sources for Service level3
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Local instrument
PmtTpInf/LclInstrm/CdNarrows the service level to a specific clearing variant — 'which variant of the scheme'. Values are largely community- or scheme-specific.
| CODE | NAME | MEANING |
|---|---|---|
INST | Instant | The SEPA Instant Credit Transfer variant (settlement in seconds, 24/7).Used with service level SEPA on SCT Inst. |
CORE | SDD Core | The SEPA Direct Debit Core scheme (consumer direct debits). |
B2B | SDD B2B | The SEPA Direct Debit Business-to-Business scheme (no refund right). |
Sources for Local instrument3
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Category purpose
PmtTpInf/CtgyPurp/CdThe high-level kind of payment, read by the banks in the chain to apply special handling or routing — 'what kind of payment, for the banks'. Distinct from Purpose (customer-facing).
| CODE | NAME | MEANING |
|---|---|---|
SUPP | Supplier payment | Payment to a supplier for goods or services. |
SALA | Salary payment | Payroll — often triggers priority or bulk handling.Some banks give SALA batches dedicated processing windows. |
PENS | Pension payment | Payment of a pension. |
SSBE | Social security benefit | A government benefit paid to an individual. |
TAXS | Tax payment | Payment of taxes. |
INTC | Intra-company payment | A payment between two entities of the same group. |
TREA | Treasury payment | A treasury/liquidity-management payment between financial parties. |
CORT | Trade settlement | Settlement of a trade (e.g. the cash leg of an FX or securities trade). |
DIVI | Dividend | Payment of a dividend. |
GOVT | Government payment | A payment to or from a government. |
CASH | Cash management | A general cash-management transfer between accounts. |
TRAD | Trade services | Settlement of a trade-finance transaction. |
LOAN | Loan | Transfer of a loan to a borrower. |
EPAY | ePayment | A payment made through online banking. |
Sources for Category purpose2
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Purpose
Purp/CdThe reason for the payment stated by the debtor and carried unchanged to the creditor — 'why, for the customer'. Informational; the creditor's system can auto-post on it. Not used by the banks to route.
| CODE | NAME | MEANING |
|---|---|---|
SUPP | Supplier payment | Payment of a supplier invoice. |
GDDS | Purchase of goods | Payment for goods. |
SCVE | Purchase of services | Payment for services. |
TRAD | Trade services | Trade-related payment. |
SALA | Salary payment | Salary paid to an employee. |
RENT | Rent | Payment of rent. |
LOAN | Loan | Loan disbursement or repayment. |
CHAR | Charity payment | A charitable donation. |
TAXS | Tax payment | Payment of taxes. |
INSU | Insurance premium | Payment of an insurance premium. |
ELEC | Electricity bill | Payment of an electricity bill. |
GASB | Gas bill | Payment of a gas bill. |
WTER | Water bill | Payment of a water bill. |
Sources for Purpose2
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Charge bearer
ChrgBrWho pays the banks' fees on the payment. The ISO codes correspond to the MT103's field 71A values OUR / BEN / SHA.
| CODE | NAME | MEANING |
|---|---|---|
DEBT | Borne by debtor | The debtor pays all transaction charges (MT: OUR).The creditor receives the full instructed amount. |
CRED | Borne by creditor | The creditor pays all transaction charges (MT: BEN). |
SHAR | Shared | Each side pays its own side's charges (MT: SHA). |
SLEV | Following service level | Charges follow whatever the scheme's service level prescribes.The SEPA schemes require SLEV. |
Sources for Charge bearer2
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Settlement method
SttlmInf/SttlmMtdHow the interbank settlement of the payment actually happens.
| CODE | NAME | MEANING |
|---|---|---|
INDA | Instructed agent | Settled on an account the instructed agent services for the instructing agent. |
INGA | Instructing agent | Settled on an account the instructing agent services for the instructed agent. |
CLRG | Clearing system | Settled through a clearing and settlement system. |
COVE | Cover | Settled by a separate cover payment; the reimbursement agents name where the cover moves. |
Sources for Settlement method2
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Instruction priority
PmtTpInf/InstrPrtyThe processing urgency the instructing party requests (a coarser signal than service level).
| CODE | NAME | MEANING |
|---|---|---|
HIGH | High | Process with high priority. |
NORM | Normal | Process with normal priority (the default). |
Sources for Instruction priority2
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: A curated subset of the commonly-used codes with plain-language meanings — not the full externally-maintained list, which is updated quarterly (Feb/May/Aug/Nov) on iso20022.org.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.