Glossary
Term |
Meaning |
ACCP |
An ISO20022 payment status - Accepted Customer Profile, this means the customers profile allows the payment to happen. |
ACH |
An Automated Clearing House (ACH) is a computer-based electronic network used for processing financial transactions between participating financial institutions. They are often referred to as CSMs and while they are the most common type of CSM, it is not true to say all CSMs are ACHs. There is also an ACH in the USA called ACH. |
ACSP |
An ISO20022 payment status - Accepted Settlement In Process. |
ACTC |
An ISO20022 payment status - Accepted Technical Checks. |
Action |
Something that is done as result of a state transition in a flow defined in flow designer. |
Action Timeout Events |
An Action Timeout event that is configured to occur when a given time period has passed without an action completing. The flow can react to this event to handle the timeout scenario. |
Active Dynamic Configuration |
A dynamic configuration that is approved and is active at the time of the request. A dynamic configuration is deemed active if it has ActiveFromDate in past or the ActiveFromDate has reached at the time of the request and does not have a past ActiveToDate. |
ActiveFromDate |
Date and time value that specifies when a dynamic configuration will become active. The dynamic configuration will not be considered active before this time. |
ActiveToDate |
Date and time value when a dynamic configuration will stop being active. The dynamic configuration will not be considered active beyond this time. |
Actor |
An Akka programming entity that has a state, a behaviour, an address to receive messages and a mailbox to store received messages in the order they arrive. An Actor is responsible for performing a discreet piece of system behaviour, and is the basic unit of the Akka Actor System. |
Actor System |
An actor system in Akka is like a highly organized company where every employee (actor) specializes in a specific task and communicates strictly via messages. |
Adapter |
A piece of java code that implements a DSL concept that can’t be entirely specified in the DSL (e.g. an external domain adapter will do all necessary format conversion between the flow and the external system). |
Additional Event |
A type of event that is raised by the flow itself. When an additional event is raised, the system will process it as though it has been received into the application via an instruction or response. |
Additional Optional Module (AOM) |
On top of the core IPF license, Additional Optional Modules can be utilised; for example ODS or scheme packs. |
Additional Optional Services (AOS) |
A concept in the SEPA payment schemes. They are optional services supported by some CSMs which members may choose to adopt or not. IPF scheme packs usually cover the mandatory functionality by default and AOS via specific agreement. |
ADMI |
ADMInistration messages in ISO20022. |
Agent |
In IPF terminology, an Agent is an entity which the Processing Entity holds a settlement relationship in one or more Transfer Currencies. The Agents and Processing entities agree to settle transactions between themselves through settlement accounts and without the need of another party getting involved for the settlement. |
Aggregate |
The aggregate is a group of data objects that can be treated as a single unit for the purpose of data changes and Events in the context of a flow. The aggregate is the live, in memory, data store for the payment instance being processed |
Aggregate Function |
An Aggregate Function performs some kind of logic when an event is received and/or upon the data received in an event for later use in a flow. |
Akka |
An open source framework for building concurrent, distributed, and resilient message-driven applications on the JVM, via microservice-style components. |
Akka Cluster |
A group of interconnected actor systems (nodes) that work together as a single, fault-tolerant application. |
Akka streams |
A toolkit for processing real-time data flows with high levels of reliance. |
Alpakka |
A toolkit for processing real-time data flows in Akka-based systems. |
Amazon Web Services (AWS) |
Cloud computing service that can be used as the deployment environment for IPF solutions. |
API |
Application Programming Interface: a set of clearly defined methods of communication between software components. |
Asciidoc |
Asciidoc is a lightweight markup language (like Markdown) for writing structured documents. HTML in comparison is also a markup language but is heavyweight. Asciidoc is used in IPF to produce documentation, such as this page you are reading now. |
Association ID |
The Association ID within the Processing Context associates a point-in-time event (such as a message-log or system event emission etc.) with a local context such as an IPF Processing Flow. This way we can state "this message log was caused by this Flow" rather than just linking to a single unitOfWork that may span multiple services and flows. |
Asynchronous |
A processing model where tasks operate independently without waiting, as opposed to synchronous. |
Automatic Retries |
One possible Resiliency Strategy in IPF, see here for more. |
Azure |
Cloud computing service from Microsoft that can be used as the deployment environment for IPF solutions. |
Backpressure |
One possible Resiliency Strategy in IPF. It’s a safety mechanism in data systems where a slow consumer signals to fast producers to pause or slow down, preventing overload. See here for more. |
Bank Directory Plus |
A SWIFT directory product that consolidates comprehensive reference data required by banks and corporates to prepare, validate, and process payments globally. It includes essential details such as BIC (Bank Identifier Code) information, branch data, and clearing system participation. It is being replaced by the new Identifiers Directory. |
Bank filtering |
A service that offers the means to filter transactions based on criteria defined through dynamically configurable rules. Enables "emergency breaks" on processing of payments that match a particular criteria. See here for more. |
BBAN |
Basic Bank Account Number. Each country can have its own BBAN format, e.g. in the UK it’s sort code & account number, while in the United States of America it’s routing number and account number. |
Bean |
A Java Bean is a reusable software component in Java programming that follows specific conventions. It’s essentially a standardized way of creating objects that can be easily understood and used by different parts of a software application or by different applications altogether. Java Beans are designed to be simple, flexible, and easy to work with, making them useful for both developers and software tools. |
Behaviour Driven Development (BDD) |
A software development approach that promotes the use of a shared, simplified language for the specification and testing of systems that deliver verifiable business value. It specifies requirements in a testable format using given, when & then statements. |
Beneficiary Bank |
The bank that receives funds as part of a payment. Referred to as Creditor Bank in ISO20022. |
BOM |
Bill of Materials, a concept in Maven that is used to manage and centralise versions of technical dependencies. |
BSON |
A binary-encoded version of JSON designed for efficiency in data storage and processing. |
BU ID |
A Business Unit ID is an identifier used to manage access control and permissions within an organization’s security framework. |
Bulking/De-Bulking |
Bulking is a capability which groups one or more payment instructions or messages into a bulk file. Bulking is required when the bank sends multiple transactions into the same scheme for processing a specific type of payment (Bulk files) or when it’s a scheme mandatory requirement to send a bulk payment message e.g. SEPA Credit transfer. De-bulking is a capability which splits a bulk message into individual instructions. |
Business data |
A piece of business data that a flow makes use of (e.g. payment initiation, selected CSM, FX deal details etc.). |
Business Identifier Code (BIC) |
A BIC is universal identifier for financial and non-financial institutions, used for addressing messages, routing business transactions and identifying business parties. The BIC format is defined by ISO standard 9362:2014. BICs are issued by SWIFT in its role as the ISO registration authority. Note: Under earlier versions of the ISO 9362 standard, BIC stood for Bank Identifier Code and this term is still widely used. |
CAMT |
Cash Account ManagemenT messages from ISO20022, e.g. camt.056 is a request to cancel. |
Checkpoints |
Refers to an identifier for the last "processing event" that occurred for a given Processing Context. The Checkpoint implementation in IPF captures internal events which happen when processing progresses, for example when a ConnectorMessage is passed between Connector processing stages - see Checkpoints |
Circuit Breaker |
Circuit breakers protect systems from being bombarded with messages at a rate they would not be able to cope with. |
Clearing and Settlement Mechanism (CSM) |
A means by which a payment can be cleared and settled, typically it is an automated clearing house (ACH) but can also be used to refer to bilateral arrangements between banks. |
Client Port |
Provides a port/interface for client code to call an external or embedded IPF Business Function. |
Client Request ID |
The Client Request ID is a field that is reserved for allocation to a client-specific value that will allow association and inquiry to an IPF unit of work. |
Collection |
A grouping of documents in a NoSQL document database, broadly analogous to a table in a relational database. Typically, all documents in a collection have a similar or related purpose. |
Completing |
This defines whether the calling request should be considered completed when this response arrives. This is particularly useful when more than one response is expected during the interaction. For example, consider a request where the external system sends a technical acknowledgement followed by a final business response. In this case we would define two responses - one to represent the technical ack (non-completing) and one for the final business response (completing). |
configurable enumerations |
Some dynamic configurations on IPF support configurable enumerations. Client implementations can define their own enumeration values for some dynamic configuration attributes while also providing default enumeration values. |
Connector framework |
A connector is simply a set of common interfaces that provide a means for a flow to communicate with external systems. |
Consumer |
The user of an API. |
Container |
An immutable collection of software (application & supporting components, not operating system), packaged in a standardised format. Allows applications to be rapidly deployed in a repeatable and efficient way (since many containers can share a single operating system instance while remaining isolated). |
Correlation |
Establishing a link between messages, e.g. linking a PACS2 status report to a previously sent PACS8 payment. |
Cosmos DB |
A Microsoft document database that strives to be compatible with Mongo DB. |
Counterparty |
A counterparty is the other party involved in a payment transaction. For example, if your company makes a payment to a supplier for services or goods received, the supplier is the counterparty to your company in that payment. Similarly, if you receive a payment from a customer for a product sold, the customer is your counterparty. Each counterparty has an obligation to fulfill their part of the transaction�making or receiving payment as agreed. The concept highlights that payment transactions always have two sides, each with responsibilities and risks, such as the risk that payment may be delayed or not made on time. |
CQRS |
|
Creditor |
The ISO20022 term for entities that receive funds as the result of a payment. Also known as the beneficiary or payee. |
Cron |
Cron is a time-based job scheduler used in Unix-like operating systems to automate repetitive tasks. |
CRUD |
Create Read Update Delete, an alternative approach to CQRS. |
CS Agent Selection Settings |
CS agent selection settings are the dynamic configurations defined by client implementations to provide a preference of which CSM Agents should be considered first for checking reachability of a payment. The clients can specify a selection order of CSM Agents based on currencies, payment types, service levels and settlement methods. |
CSFLE |
IPF supports MongoDB’s Client-Side Field Level Encryption (CSFLE). CSFLE is a security feature that encrypts specified sensitive data fields (e.g. Personally Identifiable Information) held in the database. It works in such a way that the database itself along with its administrators cannot see the data. Only the application that uses MongoDB to store information can see the data. |
CT |
An abbreviation for Credit Transfer. |
Cucumber |
Automated testing tool - Cucumber runs automated acceptance tests written in the behaviour-driven development (BDD) style, using a Given When Then syntax. |
CVF |
Credit Validation File. A STEP2-standard file transmitted by the Central System to the Direct Participant in response to an ICF. A CVF contains information regarding the success or failure of the application of Validation Rules to that ICF. |
Cypress |
Cypress is a JavaScript-based testing framework designed for modern web applications, enabling developers and QA teams to automate GUI testing, including end-to-end (E2E), component, and integration tests. Unlike traditional tools like Selenium, Cypress runs directly in the browser, offering real-time execution and debugging. |
DB |
Abbreviation of database. |
DD |
Abbreviation of direct debit. |
Dead letter / DLQ |
A dead-letter queue (DLQ) is a secondary message queue that stores messages which fail to be processed in a primary queue, acting as a safety net for distributed systems. It isolates faulty or misdirected messages to prevent disruptions, enabling debugging and reprocessing. |
Debtor |
The ISO20022 term for entities that send funds as the result of a payment. Also known as the remitter or payer. |
Decision |
A decision allows us to perform some logic programmatically and then take different processing routes based on the outcome of that decision. For example, we may only want to run a fraud check if the value of the payment is over 50. In this case we can use a "Decision". |
Decision Events |
These event are used to drive the path a flow takes as the result of a decision. |
Developer App |
This is a lightweight simple example application that provides a view across the data generated by IPF. It’s not a production utility, but is used to assist development. |
Direct Debit Mandate |
A mandate is an approval that gives the authority to process direct debits from an account for a given Creditor. |
Direct Participant |
A participant of an ACH (A type of CSM). A direct participant holds a settlement account for the ACH and can settle payments with other participants using the settlement account. |
DN |
A Distinguished Name (DN) is a unique identifier used in LDAP (Lightweight Directory Access Protocol) and X.500 directory services to locate and organize entries (such as users, groups, or devices) in a hierarchical directory structure. |
Docker |
Software packaging and deployment tool - Docker packages all elements of a software product (binaries, configurations, scripts, utilities etc.) into a single, lightweight container. This ensures that the software will always run the same, regardless of its environment. Because the Docker container is operating-system neutral, the packaged software can be deployed to different environments and on different flavours of Unix / Linux. |
Domain event |
Domain events are persisted facts about something which has occurred in your system. They cause a change of state in a flow. |
Domain Functions |
A domain function is a piece of logic within the domain of the flow that carries out processing useful to the flow. E.g. determine payment type. |
Domain Specific Language |
A Domain-Specific Language (DSL) is a specialized programming or scripting language designed for a specific application domain, unlike general-purpose languages (e.g., Python, Java). DSLs optimize efficiency and readability for narrow use cases by adopting syntax and abstractions tailored to their domain. |
DVF |
Debit Validation File. A STEP2-standard file transmitted by the Central System to the Direct Participant in response to an IDF. A DVF contains information regarding the success or failure of the application of Validation Rules to that IDF. |
DVF |
Debit Validation File. A STEP2-standard file transmitted by the Central System to the Direct Participant in response to an IDF. A DVF contains information regarding the success or failure of the application of Validation Rules to that IDF. |
Dynamic Processing Settings (DPS) |
|
EBA |
EBA Clearing is a provider of pan-European payment infrastructure such as STEP2 and RT1. It derives its name from the Euro Banking Association. Sometimes it is referred to as ABE or ABE-EBA which relate to the French version of its name. |
Egress |
Egress Traffic refers to data flowing out of a network or system to an external destination (e.g., the internet, another server, or a client device). It contrasts with ingress traffic, which involves incoming data. |
EMF |
Eclipse Modelling Framework: a language modelling format (similar to MPS) to allow the definition of Meta-Models. |
Endpoint |
An endpoint is any device or software component that connects to a network, serving as an entry or exit point for data communication. It enables interactions between systems, users, or services. |
Enum |
An enum (short for enumeration) is a custom data type that represents a fixed set of named constants, making code more readable and maintainable by replacing "magic numbers" or strings with meaningful labels. |
EOD |
End of Day. |
E-Repo |
ISO20022 E-Repository: a 100Mb binary file containing all the ISO20022 data in the EMF Meta-Model format. |
ESB |
Event Sourced Behaviour (or also an Enterprise Service Bus). |
EuroSIC |
Swiss (RTGS) system for euro payments between banks within Switzerland, operated by SIX Interbank Clearing Ltd. |
Eurosystem |
The monetary authority of the Euro area. The www.ecb.europa.eu/ecb/orga/escb/eurosystem-mission/html/index.en.htmlEurosystem] comprises the European Central Bank and the national central banks of the Member States whose currency is the Euro. |
Event Behaviour |
This is the behaviour that specifies what actions should be taken on receipt of an event. It is the core logic of a flow, e.g. when in State A if domain event 2 is received then do action X and move to State B. |
Event Criteria |
Used to control movement between states in a flow as part of Event Behaviour. On - this movement will happen upon the arrival of a single event (e.g. we may transition when receiving "Event 1") On any of - this movement will happen upon the arrival of one of multiple events (e.g. we may transition when receiving either of "Event 1" or "Event 2") On all of - this movement will only occur upon the arrival of multiple events (e.g. we may transition only after receiving both "Event 1" and "Event 2") |
Event sourced |
Event Sourcing is an architectural pattern where changes to an application’s state are stored as an immutable, append-only sequence of events (facts) rather than overwriting the current state. Each event represents a discrete action (e.g., OrderPlaced, PaymentReceived) and includes contextual metadata (timestamp, user ID, etc.). |
Eventually consistent |
Eventual consistency is a data consistency model in distributed systems where updates to a data item propagate asynchronously across replicas, guaranteeing that given enough time without new changes all nodes will converge to the same state. It prioritizes availability and partition tolerance over immediate consistency. |
External Domain |
Represents some business domain - not our current flow’s - that we need to interact with. For example, let’s assume that we need to talk to a sanctions system during part of the flow. To support this, we would model that sanctions system as an external domain. |
External message |
A message exchanged between a flow and an external domain. |
Fan-out/Fan-in |
The Fan-Out/Fan-In pattern is a concurrency model in distributed systems that parallelizes task processing for efficiency, then consolidates results. Key Concepts Fan-Out: Distributes tasks across multiple workers (threads, processes, or services) for parallel execution. Fan-In: Aggregates results from all workers into a consolidated output. |
Fednow |
An American instant payment scheme. |
Flo-Lang |
One of the domain specific languages in IPF, it is used to define orchestration flows. |
Flo-lang solution |
This is effectively an overall project. A solution can contain many models. |
Flow |
The flow is the foundation of an IPF application, its the glue holding together the orchestration steps. |
Flow Designer |
The IPF product name for the Jetbrains MPS editor that is used to define a Flow. Flow Designer is included in the IPF core licence. |
Freemarker |
FreeMarker is a Java-based template engine for generating text output (HTML, emails, configuration files, source code, etc.) by merging dynamic data with pre-defined templates. It uses the FreeMarker Template Language (FTL), a lightweight, domain-specific language designed for presentation logic. |
FX |
Foreign eXchange, e.g. converting USD to GBP. |
Generation |
Converting a model specified in an IPF domain specific language into executable code. |
Gherkin |
Gherkin is a domain-specific language (DSL) used in Behaviour-Driven Development (BDD) to write executable specifications in plain, human-readable text. It bridges the gap between technical and non-technical stakeholders by describing software behaviour without implementation details. |
Git |
Software version control system - Open-source, distributed, software version control system. Used in IPF to perform version control across the IPF development environments. |
Global state |
A higher level state that the states found in flows. |
Grafana |
Grafana is an open-source observability and data visualization platform designed for real-time monitoring, analytics, and alerting. It enables users to query, visualize, and correlate metrics, logs, and traces from multiple sources through interactive dashboards. |
Graphviz |
Graphviz is an open-source tool for visualizing graphs and networks from structured data. It uses a declarative DOT language to define nodes, edges, and their relationships, which it then renders into diagrams (e.g., flowcharts, hierarchies, network topologies). |
HMAC |
HMAC (Hash-Based Message Authentication Code) is a cryptographic mechanism used in many places, such as within the SWIFT network to verify the integrity and authenticity of financial messages and within the IPF GUI to sign JWTs. It combines a secret key with a hash function (e.g., SHA-256) to generate a unique signature for each message. |
HOCON |
Human-Optimized Config Object Notation. A human-friendly configuration file syntax, used to define IPF configuration. |
HTM |
Human Task Manager. A component of IPF that allows flows to request humans to execute tasks and optionally return the result to the flow. |
IBAN |
International Bank Account Number. For more background see here. |
IBAN Plus |
IBAN Plus is a SWIFT-managed data product that enables financial institutions to validate IBANs, derive associated BICs (Bank Identifier Codes), and ensure compliance with cross-border payment standards (e.g., SEPA). It is part of SWIFT’s reference data suite, alongside products like SEPA Plus and Payments Plus. |
IBAN Structure |
The IBAN Structure file (IBANSTRUCTURE_FULL_[YEAR].txt) is a SWIFT-provided resource that defines the technical format of IBANs for each country, ensuring compliance with ISO 13616. It is used by banks and financial software to validate and parse IBANs correctly. It is part of IBAN Plus. |
ICF |
Input Credit File. STEP2-standard file that is used to transmit payment instructions for processing from Direct Participants to the Central System. |
IDE |
Integrated Development Environment. E.g. Eclipse or IntelliJ. |
Idempotency |
Idempotency ensures that performing the same operation multiple times (e.g., due to retries or network issues) produces the same result as a single execution. It is critical for preventing duplicate transactions, erroneous charges, or inconsistent states in financial systems. |
Identity Resolution |
A feature of IPF that allows comparisons of names and addresses. |
IDF |
Input Debit File. STEP2-standard file that is used to transmit debit instructions for processing from Direct Participants to the Central System. |
Immutable object |
Immutability is the property of data or objects that prevents modification after creation. Instead of altering existing data, operations generate new instances, ensuring consistency, security, and traceability. |
Indirect Participant |
A participant to an ACH (a type of CSM). An indirect participant does not hold a settlement account for the ACH and relies on a direct participant to provide the means to settle the payments with other participants through the ACH. |
Industry Data |
Industry data are dynamic configurations that are maintained using data provided by industry sources through files. Examples of industry data are CSM Participants (populated using membership files from CSMs), Party Entity Directory and IBAN Plus directory (populated from SWIFTRef files). |
Ingest |
Data ingestion is the process of collecting, importing, and processing raw data from various sources into a storage or processing system (e.g., databases, data lakes, or streaming platforms). It is the first step in building data pipelines and analytics workflows. |
Ingress |
Ingress refers to the process of data entering a system from external sources. It is the first step in data pipelines, enabling collection and processing for analytics, storage, or real-time applications. |
Initiation Behaviour |
This is a behaviour that specifies the behaviour for each input that starts a flow. |
Input Behaviour |
Converts an input (an instruction or a response) combined with a response code to a domain event. E.g. Accounting system responded with code 404 > Domain Event "Account not Found". |
Input Enricher |
An Input Enricher generates (or updates) business data elements to be stored on a received event. The key point to understand in the difference to the "aggregate" type of mapping is that this data will be added to the event and persisted. This means for example that it will be sent and made available within the processing data stream for use outside of IPF. |
Instruction |
Instructions are the simplest thing flows receive from an external domain. It can be triggered by the external domain at any time and we will start processing. This can be thought of as the external domain pushing information to us. |
IntelliJ |
|
Intra Entity Party |
An entity that shares ledger with the processing entity. Intra entity parties are usually branches of the processing entity. |
Intra-entity payment |
A payment within one ledger, often referred to as an 'on us' payment. |
IPF |
|
IPF ISO20022 Model |
A Java representation of the IS20022 Model. |
IPF Mapping Framework |
The IPF Mapping Framework translates between the flow data model and that of external systems in a configuration-driven, low-code way. |
IPF Scaffolder |
The IPF scaffolder is a java module that provides engineers with a quick and efficient way to bootstrap a new project using the IPF SDK. It can be executed via maven to generate a new IPF project that includes all the necessary dependencies and configuration to be able to run as a standalone project. |
IQF |
Input Inquiry File. A STEP2-standard file that is used to transmit inquiry messages for processing from Direct Participants to the Central System. |
ISO 20022 |
ISO 20022 Financial Services - Universal financial industry message scheme. A standard for electronic data interchange between financial institutions, published by the International Organization for Standardization. ISO 20022 defines a common platform for the development of financial messages. |
ISO 3166 |
ISO3166 is a standard that defines codes for the names of countries, dependent territories, and special areas of geographical interest. |
ISO 4217 |
This standard establishes internationally recognized codes for the representation of currencies that enable clarity and reduce errors. |
ISO20022 Meta-Model |
Concepts, rules, types and relationships that formally map the interaction for Financial Message exchange. |
Jackson |
JSON/XML processor - Open-source Java-based library used to serialize or map Java objects to JSON and vice versa. |
JaCoCo |
Java Code Coverage library. Used as part of internal quality assurance. Provides analysis of unit test coverage in Development environment. |
JAVA |
Programming language used extensively in IPF. |
Java Development Kit (JDK) |
A software development environment used for developing Java applications. |
Java Virtual Machine (JVM) |
Virtual machine environment under which IPF runs. |
JAXB |
JAXB (Java Architecture for XML Binding) is a standardized framework for mapping Java objects to XML (marshalling) and XML to Java objects (unmarshalling). It simplifies XML handling by automating conversions, eliminating manual DOM/SAX parsing. |
Jenkins |
Build server - Located on the server where the project’s main build is created, Jenkins triggers a new build every time a user checks in changes to the source code. This supports the process of continuous integration for testing and development. Icon use Jenkins internally for managing IPF builds. |
Jest |
Jest is a zero-configuration, batteries-included JavaScript testing framework developed by Facebook. It excels at unit, integration, and snapshot testing for frontend (React, Vue) and backend (Node.js) JavaScript applications. |
JetBrains MPS |
The tool used to develop IPF’s domain specific languages and to use the languages to build solutions. |
Jitter |
In the context of retrying a failed network transmission, jitter refers to intentionally adding a small, random delay before retrying the request. This randomness helps prevent multiple clients from retrying simultaneously, which could overwhelm the server again. |
JMS |
Java Message Service (JMS) is a Java API that enables applications to create, send, receive, and read messages, facilitating loosely coupled, reliable, and asynchronous communication between components of a distributed system. |
Journal |
A journal is like a digital logbook that keeps track of important actions or changes made within a system or application. It records events, transactions, or updates to help developers understand what happened and when. Think of it as a way to keep everything organized and traceable, so if something goes wrong, it’s easier to figure out why. |
JSON |
JSON (JavaScript Object Notation) is a simple text-based format for storing and exchanging data. It organizes information in key-value pairs (like "name": "John") and supports basic data types such as strings, numbers, arrays, and objects. JSON is widely used because it’s easy for both humans to read and machines to process. |
JUnit |
JUnit is a free, widely used testing framework for Java applications, designed to help developers write and run automated tests for small, isolated pieces of code (like individual methods or classes). It ensures each component works correctly before integrating it into larger systems. |
JWT |
JWT (JSON Web Token) is a compact, secure way to transmit information between systems as a JSON object. It’s commonly used for authentication and data exchange in web applications. |
K8s |
Kubernetes (because there are 8 letters between the K and the S). |
Kafka |
Kafka is a distributed, open-source platform designed for handling real-time data streams at scale. It acts as a high-throughput, fault-tolerant system that ingests, stores, and processes continuous data flows (e.g., logs, transactions, or sensor data) from multiple sources. |
Kubernetes |
Kubernetes (K8s) is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. Developed by Google and now maintained by the Cloud Native Computing Foundation (CNCF), it groups containers into logical units (like pods) for easy coordination across clusters of machines. |
LAC |
Liquidity Adjustment Checkpoint (SEPA) / Cycle (SEPAInst): a period during which liquidity transfers can take place |
LAU |
LAU Keys are a security mechanism used in systems like SWIFT to ensure the authenticity and integrity of messages exchanged between parties. They work by generating a unique digital signature, called a Local Message Authentication Code (LMAC), for each message. This signature is created using a pre-shared secret key and a secure algorithm (e.g., HMAC-SHA256). The receiving system verifies the signature to confirm that the message has not been tampered with and comes from a trusted source. |
LDAP |
Lightweight Directory Access Protocol is a standardized protocol used to access and manage directory services over a TCP/IP network. A directory service acts like an organized "phonebook" for network resources, storing hierarchical information about users, devices, roles, permissions, and other organizational data. LDAP simplifies the process of querying, updating, and authenticating against these directories. |
LEI |
A Legal Entity Identifier (LEI) is a unique, standardized 20-character alphanumeric code assigned to distinct legal entities such as companies, funds, or trusts. It is used to globally identify these entities in financial transactions and regulatory reporting, helping to clearly distinguish organizations even if they have similar names. The LEI system is based on an international standard (ISO 17442) |
Lightbend |
Lightbend (now operating as Akka) is a software company originally founded in 2011 by Martin Odersky (creator of Scala), Jonas Bonér (creator of Akka), and Paul Phillips. Headquartered in San Francisco, it specializes in tools for building reactive, distributed, and cloud-native applications on the Java Virtual Machine (JVM). |
Low-code |
Low-code is a software development approach that minimizes manual coding by using visual tools (like drag-and-drop interfaces) and prebuilt components to create applications. It accelerates development by abstracting complex code into reusable modules, enabling both professional developers and non-technical users ("citizen developers") to build functional apps faster than traditional methods. |
Mapping Function |
A mapping function is a piece of logic that is used to transform business data elements into different business data elements. They can be used in one to one, one to many or many to many examples. |
Maven |
Maven is an open-source build automation and project management tool primarily used for Java applications. Developed by the Apache Software Foundation, it standardizes the build process by automating tasks like compilation, dependency management, testing, and packaging. |
Maven plugin |
Maven Plugin is a modular component in Apache Maven that extends its core functionality by executing specific build tasks (called goals). Plugins enable reusable automation for tasks like compiling code, packaging artifacts, running tests, or generating documentation. |
MDR |
Message Definition Report: reference documents that are published by the ISO20022 Registration Authority. |
MDS |
Message Data Structure, a data structure for use within flows based on the ISO20022 message definitions. |
Message Components |
Message Definitions are comprised of Message Components. |
Message Definition Identifier |
ISO20022 identifiers, e.g. pacs.008.001.08. |
Message Definitions |
ISO20022 message definitions, e.g. FIToFICustomerCreditTransferV08. |
Message log |
A log of all messages sent and received by an IPF solution. |
Message Schema |
A message schema is a structured blueprint that defines the format, structure, and rules for data exchanged between systems. It ensures that both the sender and receiver understand and interpret the data consistently. Message schemas are commonly used in formats like JSON and XML. |
Metrics Processor |
The IPF Metrics Processor exists to assist in answering questions about IPF payment processing such as "How many payments have finished in the last hour?". |
Modal |
Modal refers to a GUI window or dialog that temporarily blocks interaction with the rest of the application until the user completes a required action or dismisses it. It forces focused attention by disabling the parent window’s functionality, often dimming the background for visual emphasis. |
MongoDB |
Document-oriented database. MongoDB's document storage model is ideally suited for ISO20022 XML-style messages used for instant payments. It offers fast access and data retrieval for online transaction processing. IPF uses MongoDB for Transaction logging and enquiry, Message logging and enquiry, operational data such as States of endpoints, scheme participant availability, scheme specific data (for example, settlement cycles), Reference data, such as sorting code and participant directories. |
Mutable object |
Mutable Object is a programming concept referring to an object whose internal state or data can be modified after its creation. Unlike immutable objects, which remain constant once instantiated, mutable objects allow alterations to their properties, values, or structure without creating a new instance. |
Nack |
Negative ACKnowledgement. Also sometimes referred to as a NAK or a NOK (Not OK). |
Namematcher |
A Netowl product that is used in Identity Resolution. |
NCCs |
National Clearing Codes. E.g. in the UK, sort codes. |
Netowl |
The company that produces Namematcher, the software used in IPF’s Identity Resolution. |
Nexus Repository Manager |
Nexus (Sonatype Nexus Repository Manager) is an enterprise-grade repository management platform designed to centralize, secure, and streamline the storage, distribution, and governance of software artifacts (e.g., binaries, libraries, containers) across the development lifecycle. |
Node |
A single application instance which is configured within a cluster of multiple instances. |
Notification |
Notification are the opposite of instructions in the flo DSL. These are used when we want to push our data out to an external domain. |
Oauth |
OAuth (Open Authorization) is an open-standard framework for secure, token-based authorization that allows third-party applications to access user data on another service (e.g., Google, Facebook) without exposing the user’s credentials. |
On Us Payment |
A payment where both the debtor account and the creditor account are held with the same financial institution (or within the same group). |
Open API |
De-facto standard for API documentation. |
Operational Data Store (ODS) |
|
OQF |
Output inQuiry File - A STEP2-standard file of inquiry messages that have been successfully processed and are transmitted by the Central System to the receiving Direct Participant. |
Original reason code |
The original (e.g. that of an external domain) reason for something. E.g. account closed, insufficient balance. |
Original reason text |
The original (e.g. that of an external domain) explanatory text relating to the result of an action. |
Original response code |
The original (e.g. that of an external domain) status of something. E.g. accepted, rejected, blocked. |
Originating Bank |
The bank that originates (sends) a message (Outbound Customer Credit Transfer). In ISO20022 terms, for a credit transfer it’s the Debtor Bank and in direct debit it’s the Creditor Bank. |
Orika |
Orika is a Java-based bean mapping framework that automates the copying of data between objects with different structures (e.g., DTOs, domain models, API responses). It eliminates manual boilerplate code by dynamically generating optimized mappers at runtime using bytecode generation, offering performance close to hand-written mapping. |
Orphan |
An unexpected message e.g. getting a clear and settle response without having sent a request, or getting a timeout status report without having received the payment that is being timed out. |
PACS |
PAmyent Clearing and Settlement messages from ISO20022, e.g. pacs.008 is an interbank customer credit transfer, pacs.003 is an interbank direct debit. |
PAIN |
PAyment Inititation messages from ISO20022, e.g. pain.001 is a customer credit transfer initiation. |
PART |
An ISO20022 group payment status that means the file was partially accepted. |
Participant |
A member (generally a bank) of a payment scheme/Automated Clearing House. |
Party entity directory |
Party Entity Directory is a dynamic configuration that can be used to look up Party Entities to retrieve the party entity details like identifiers and address details. Party entity directory can be populated with varios industry data sources as well as custom client specific source of reference data. Party entity data retrieved from party entity directory can be used for payment enrichment purposes. |
Passivation |
A flow passivates when it moves to a specified state and the Action from the Event Behaviour table is executed. Passivating essentially removes the flow entity from memory, to be rehydrated (i.e. reloaded) and activated at a later point, e.g. future dated payments or lengthy sanctions investigations. |
Payment journey |
IPF and ODS will refer to a collection of processing flows as a Journey Type. The currently available Journey types are as follows: PAYMENT > Pacs.008, Pain.001, Pacs.002, Camt.054 based RECALL > Camt.056, Pacs.004, Camt.029 BULK > Pain.001 group header or Pacs.008 group header BATCH > Pain.001 Payment Information |
Payment Scheme |
A payment scheme is a set of rules which have agreed upon to execute transactions through a specific payment instrument (such as credit transfer, direct debit, card, etc). It is different from a payment system, which is a technical infrastructure that processes transactions in line with the rules defined in a payment scheme. Generally there is one payment system that implements the scheme, but not always, most notably in the case of SEPA. |
Payment Services Provider (PSP) |
Payment Services Provider - this is the entity which owns and runs the Payments Processing capability (aka Payments Processor). This might not be a bank or a Financial Institution, it could be run by another entity. |
Payment Status Report (PSR) |
The ISO20022 "FI to FI Payment Status Report" message (pacs.002), which is principally used to respond (accept, reject, etc.) to a payment request. |
Payment Type |
In IPF a payment type is a classifier for payments that is completely determined by the user of IPF. |
PCF |
In STEP2 it is (optionally) transmitted reporting pre and post-settlement cancellations. It is a CAMT56. |
PDS |
Processing Data Structure. Allows users of IPF to create completely bespoke data structures, which are often based on the ISO20022 business model, but do not have to be. |
PII |
PII, or Personally Identifiable Information, refers to any data that can be used to identify, contact, or locate a specific individual. This can include a wide range of information, from basic details like names and addresses to more sensitive data like social security numbers and financial information. Essentially, if information can be used to distinguish one person from another, it’s likely considered PII. |
Pod |
A group of one or more co-located containers, deployed together as a unit, with shared storage, shared network resources, and run in a shared context. |
Pojo |
POJO (Plain Old Java Object) is a term for a simple Java class that adheres to basic Java conventions without being tied to specific frameworks, interfaces, or annotations. It emphasizes minimalism and reusability by avoiding external dependencies. |
Port |
An interface to provide entry and exit point to the core application, agnostic of the specific external connection implementation. |
Processing context |
IPF’s Processing Context is an object which contains a collection of unique identifiers related to IPF processing (including UowId, AssocationId & ClientRequestId) |
Processing entity |
An organisational subdivision within a deployment of IPF. E.g. a client may have a branch in Germany and a branch in France. Each branch is a different processing entity and so can have different configuration, user access etc. |
Processing Settings |
Processing settings are dynamic configurations that are specific to a client implementation and maintained by client teams using IPF DPS capability. Examples of processing settings are Processing Entity, Generic Processing Settings, Agent Settings, Agent Clearing & Settlement Settings, CS Agent Selection Settings. |
Producer |
In a reactive system, a producer (or Publisher) is a component that emits data streams (events, messages, or values) asynchronously to one or more consumers (Subscribers). It adheres to the Reactive Streams specification, enabling non-blocking, event-driven data flow with backpressure control. |
Prometheus |
Prometheus is an open-source monitoring and alerting toolkit designed for cloud-native and dynamic environments (e.g., Kubernetes, microservices). It collects, stores, and analyses time-series metrics numeric data points recorded with timestamps enabling real-time performance tracking and issue detection. |
PromQL |
PromQL (Prometheus Query Language) is the functional query language used in Prometheus to select, aggregate, and analyse time-series metrics in real time. Designed for monitoring dynamic systems, it enables users to extract insights, create alerts, and visualize data through expressive syntax tailored for temporal data. |
QVF |
Inquiry Validation File. A STEP2-standard file transmitted by the Central System to the Direct Participant in response to an IQF. A QVF contains information regarding the success or failure of the application of Validation Rules to that IQF. |
R transactions / R messages |
Messages relating to a payment, e.g. Request to cancel, Return, Refund etc. |
RA |
|
Reachability |
Participants of a scheme/ACH are reachable. This is the reachability of the scheme. |
Reactive |
Reactive Programming is a declarative programming paradigm cantered on asynchronous data streams and automatic propagation of change. It enables applications to dynamically respond to real-time events (e.g., user inputs, sensor data) by modelling data flows as composable, event-driven sequences. |
Reactive streams |
Reactive Streams is a standardized asynchronous stream processing specification designed for handling data flows with non-blocking backpressure ensuring that fast producers don’t overwhelm slow consumers. |
Read side |
Read Side (in Event Sourcing & CQRS) refers to the part of a system optimized for querying data, where materialized views or projections are generated from an event log to serve fast, structured responses to clients. Unlike the write side (which handles commands and stores events), the read side focuses solely on efficient data retrieval. |
Reason code |
A "Reason Code" is a reason why the response code is set. So for example your response code could be "Rejected" with a reason "Incorrect Currency". In ISO 20022 this is a status reason. |
Reason text |
The IPF implementation (NOT that of an external domain) explanatory text relating to the result of an action. |
Recall |
A request to return funds previously sent, typically uses a CAMT56. |
Regional Brands |
The EBA STEP2 term for Indirect Participants |
Rehydrated |
Rehydration is the process of rebuilding an object’s current state by replaying a sequence of past events from an event log. It’s a core concept in event-sourced systems, caches, and frontend state management. |
Remember Entities |
Remembered Entities (or Recoverable Entities) are objects in an event-sourced system that maintain their state by storing and replaying a sequence of past events. Unlike traditional databases that persist only the latest state, these entities "remember" their entire history |
Request |
A request is used when a flow needs a response back from the external domain in reply. |
Request To Pay (R2P, RTP) |
An additional value-added service offered by some instant payment schemes (including TCH in the USA, GIRO in Hungary). The Request To Pay is a message initiated by a party (business or individual) that wants to be paid, containing all relevant details of the payment required. The request to pay is sent from the requester’s bank to the bank of the party being asked for payment, via the central infrastructure of the instant payment scheme. The receiver of the request can then simply review details and either accept or reject it. Accepting the request will trigger the sending of an instant payment using the details contained in the request to pay. |
Requester |
In a scheme that verifies Creditor names prior to payment initiation (e.g. Confirmation of Payee in the UK or Verification of Payee for SEPA), the requestor is the organisation from where the payment will be initiated should the identity be confirmed. |
Resolution of investigation (ROI) |
A resolution of investigation in payment processing is typically used to respond to a recall and uses a CAMT29. Usage varies by scheme, e.g. in SEPA ROI is only used for a negative answer for a recall, whereas in TCH RTP it used for negative and positive. |
Responder |
In a scheme that verifies Creditor names prior to payment initiation (e.g. Confirmation of Payee in the UK or Verification of Payee for SEPA), the responder is the organisation that holds the correct name information. |
Response code |
A "Response Code" is an expected outcome code for a response that could be used for onward processing. E.g. Rejected, Accepted, Posted, Blocked etc. In ISO 20022 this is a Status. |
REST |
REpresentational State Transfer. REST is an architectural style for designing networked applications, emphasizing simplicity, scalability, and stateless communication over HTTP. It standardizes how systems expose and interact with resources (data or services) using uniform interfaces. |
Return |
Typically a PACS4, this returns funds previously received to the originator of the payment. In some schemes the recipient of the funds can initiate a return, in some schemes a return can only be sent when the originator has requested so via a recall. |
RJCT |
An ISO20022 payment status - Rejected. |
RRR (See also R transactions / R messages above) |
Recalls, Returns and Results Of Investigations. |
RSF |
Results of Settlement File. This file is sent to both sides of the transaction. It lists details of both successful (for SDD, optional for SCT) and failed settlement of Debit messages. |
RT1 |
EBA Clearing's clearing and settlement infrastructure for SCT Inst. Currently banks and other PSPs can connect to RT1 via SIAnet or EBICS. |
RU |
Request Unit (RU) is the performance currency of Azure Cosmos DB, representing the computational resources (CPU, memory, IOPs) required to execute database operations like reads, writes, queries, and updates. It abstracts infrastructure complexity into a single measurable unit for cost and capacity planning. |
S3 |
A file storage mechanism offered as part of Amazon Web Services (AWS). |
SAML |
SAML (Security Assertion Markup Language) is an XML-based open standard for securely exchanging authentication and authorization data between parties typically between an Identity Provider (IdP) (e.g., Azure AD, Okta) and a Service Provider (SP) (e.g., SaaS apps like Salesforce). It enables Single Sign-On (SSO), allowing users to access multiple services with one set of credentials. |
SCALA |
Programming language - Object-oriented programming language (Scalable Language) in which Akka is written. |
SCF |
Settled Credit File. STEP2-standard file of payment instructions that have been successfully processed by CGS and are transmitted by the Central System to the receiving Direct Participant |
Scheduled Dynamic Configuration |
A scheduled dynamic configuration on DPS is a dynamic configuration that will become active at a future date and time. |
Scheduler |
Scheduler ensures that the execution of payments is started at a time that allows any needed value added services (Future dated payments, Batch payments etc) to be applied and their value date time to be met. The scheduler monitors the payment data store for individual and bulk payments whose value date & time and associated value added services (Netting, Bulking, Enrichment, Remittance handling etc.) makes them eligible for execution. The scheduler also monitors the payment data store for any re-occurring payment schedules that require a payment to be created and executed in order for value added services to be applied and the value date & time schedule to be met. Whenever a payment is found or created that is eligible for execution the scheduler invokes any needed value added services and triggers the execution of the payment. Scheduler is usually used for make payments, e.g. 1. Future Dated Payments 2. SEPA CT Payments 3. SEPA DD etc. |
Schematic |
Schematics in Angular are like automated instructions or "recipes" that developers use to create or modify parts of a GUI project. They help streamline repetitive tasks, ensuring consistency and saving time. |
Scheme Pack |
Scheme Packs are a specific type of Additional Optional Module each related to the processing concerns for a specific CSM within a scheme. Each available Scheme Pack is licensed separately. A Scheme Pack can be developed by Icon or a client and includes the functionality that is required to process outgoing and incoming payments/transactions with respect to a specific CSM. |
SCT Inst |
SEPA Credit Transfer Instant Payments. Scheme layer of Euro instant payments. Based on SEPA Credit Transfer. The scheme is defined and managed by the European Payments Council and implemented by multiple CSMs. |
SEPA |
|
SIC |
|
Sinks |
A data sink is the destination endpoint in a data flow system where processed or collected data is stored, forwarded, or consumed. It acts as the final repository or output for data after it passes through sources, transformations, or pipelines. |
Six Bank Master |
An industry directory listing participants in Swiss Interbank Clearing (SIC). SIX is the technology provider for SIC. |
Snapshot |
A snapshot is a static, point-in-time copy of a dataset or system state, used to preserve historical data, enable recovery, or analyse changes over time. It captures the exact state of data at a specific moment, often for auditing, backups, or incremental processing. |
Sources |
In stream processing, sources are the entry points that generate or emit real-time data streams. They feed raw data into a streaming pipeline for processing, analysis, or storage. |
Split Brain |
Split brain is a critical failure scenario in distributed systems where a cluster of nodes becomes partitioned due to network issues, causing subsets of nodes to operate independently without recognizing each other. This leads to data inconsistency and potential corruption as each partition makes conflicting decisions. |
Split Brain Resolver |
A split brain resolver is a mechanism in distributed systems designed to detect and recover from network partitions (split brain scenarios) by enforcing policies that maintain data consistency and cluster stability. It ensures that only one partition remains active or authoritative, preventing conflicting updates. |
Splunk |
Splunk is a data analytics platform designed to ingest, index, search, and visualize machine-generated data (logs, metrics, events) in real time. Its architecture is highly scalable, supporting deployments ranging from single-server instances to distributed, multi-site clusters. |
Spring |
Spring (and Spring Boot/Spring Cloud) is a Java-based framework for building distributed systems, offering tools to implement common patterns like microservices, event-driven architectures, and resilience mechanisms. |
SSO |
|
Standard Settlement Instructions (SSI) |
These are details about standard banking relationships between banks by currency. Note: "SWIFT Ref SSI Plus" is a SWIFT supplied set of reference files. It is possible for customer preferences ("Correspondent Bank Preferences") to override those published by the Bank, as these only reflect the Banks agreements with other Banks. Where a customer (i.e. an agency bank) has other agreements in place, these may override the Banks agreements. |
State |
States represent a point in the processing of your system. Sometimes referred to as a DSL state to distinguish from Global States. |
State Transition |
When a flow moves from one state to another. |
Status Request Scheduler (SRS) |
The Status Request Scheduler (SRS) is a feature of the CSM Service that allows users to automate the sending of status request messages (typically PACS28s) after initiating certain payment actions. |
STEP2 |
Straight Through Euro Processing 2. A batch based SEPA clearing system run by the EBA. |
STET |
STET is a provider of SEPA clearing services. |
Subflow |
A subflow is a reusable flow component. It is essentially the same as a flow in that it has states, input behaviours and event behaviours. However, a subflow has no life of it’s own and is only used as a mechanism of reuse and therefore MUST be contained within an outer flow. |
Swagger |
Swagger is an open-source toolset for designing, documenting, and testing RESTful APIs based on the OpenAPI Specification (OAS). It standardizes API descriptions in machine-readable formats (YAML/JSON), enabling automation in documentation, client SDK generation, and testing. |
SWIFT |
The Society for Worldwide Interbank Financial Telecommunication. A key part of global payments infrastructure. |
SWIFT AGI |
SWIFT Alliance Gateway Instant is a connectivity plugin or adapter used to integrate financial applications with SWIFT Alliance Gateway, a centralized messaging hub for secure and scalable communication across SWIFT networks (FIN, InterAct, FileAct). |
Swift BICDir2018 |
BIC Directory 2018 is a simplified version of BIC Plus file that provides limited information on the BIC8 value, branch code, value added services and address information. BIC Directory 2018 will be replaced by BIC Directory in 2025. |
Swift Exclusion List |
The SWIFT exclusion list refers to financial institutions (typically banks) barred from accessing the SWIFT messaging network, often as part of international sanctions. This disrupts their ability to conduct cross-border transactions, trade, or access global financial markets. |
System Event |
These occur when something happens to the system. There are a set of default events but they can also be tailored to be specific to individual needs. |
T2-RTGS |
|
TARGET Instant Payment Settlement service (TIPS) |
TARGET Instant Payment Settlement service is a SEPA Inst CSM. |
TCH |
The Clearing House. Long-established US payments clearing and settlements provider, |
TCK |
A Technology Compatibility Kit (TCK) is a standardized test suite used to verify that software products (e.g., interfaces, applications) comply with specific technical requirements, ensuring interoperability within a defined ecosystem. |
Technical Duplicate Check |
Technical duplicate check for an inbound or outbound payments message using hash techniques or any other solution to ensure that a file is not duplicate. Technical duplicate check is intended to detect files/messages that are totally identical which are usually caused by malfunction application or middle ware. This service is often provided by the channel. Technical duplicate check is different from business duplicate check. If a payment is found to be a duplicate (with same payment reference, amount, sender and beneficiary etc) then the payment is rejected back to the originator. |
Test-FW |
Either the IPF test framework or the Icon Test Framework. |
Throttling |
Throttling (or rate limiting) is a technique to control request throughput in APIs, services, or networks preventing overload, ensuring fairness, and maintaining system stability. |
Transport |
A means of transferring data between systems, e.g. Kafka, MQ, http etc. |
TTL |
Time to Live. TTL is a database feature that automatically expires and deletes records after a specified duration or at a fixed timestamp. It optimizes storage, reduces costs, and complies with data retention policies. |
Twelve-Factor App |
The Twelve-Factor App methodology is a set of best practices for building modern, scalable, and maintainable software-as-a-service (SaaS) applications. Originally proposed by Heroku in 2011, it emphasizes portability, resilience, and automation in cloud-native environments. |
UETR |
Unique End-to-end Transaction Reference, universally unique identifier to provide an end-to-end reference of a payment transaction. |
Unified Modelling Language (UML) |
|
Uniform Resource Identifier (URI) |
|
Unit of work ID (UOWID) |
The default unique identifier for a transaction in an IPF solution. |
Upsert |
Upsert (a portmanteau of update + insert) is a database operation that automatically inserts a new record if it doesn’t exist, or updates an existing one if it does. It eliminates the need for separate INSERT and UPDATE statements, improving efficiency and atomicity. |
UUID |
Universally Unique Identifier. Also known as GUID (Globally Unique Identifier). |
Verification of Payee (VOP) |
An IPF service that allows participants to verify the identity of a creditor account before their client initiates a payment to that account. Note it also the name of one of the schemes that the IPF function VOP supports, being the verification scheme for SEPA. |
Write side |
In Command Query Responsibility Segregation (CQRS), the write side (or command side) handles all data modifications (inserts, updates, deletes) and enforces business rules, while the read side serves queries. This separation optimizes performance, scalability, and domain logic clarity. |
XJC |
XML to Java Compiler is a command-line tool included in the Java Development Kit (JDK) as part of JAXB (Java Architecture for XML Binding). It compiles XML Schema (XSD) files into annotated Java classes, enabling seamless conversion between XML and Java objects. |
XML |
eXtensible Markup Language is a markup language designed for structuring, storing, and transporting data. Unlike HTML, which focuses on displaying data, XML defines custom tags to describe content in a machine and human readable format. |
Xms |
The initial amount of memory allocated. |
Xmx |
The maximum amount of memory that can be allocated. |
XSD |
XML Schema Definitions are a standard format for expressing a schema, XSDs are provided for each Message Definition by the ISO20022 Registration Authority. |
XSL |
eXtensible Stylesheet Language is a language for styling and transforming XML documents, primarily through XSLT (XSL Transformations). It consists of three parts: XSLT: Transforms XML into other formats (HTML, XML, text). XPath: Navigates XML nodes (used within XSLT). XSL-FO: Formats XML for print/PDF (now largely replaced by CSS). |
YAML |
YAML Ain’t Markup Language is a human-readable data serialization format designed for configuration files and data exchange. It prioritizes simplicity and readability, using indentation and minimal syntax compared to XML or JSON. |