IFX Versions


IFX introduced Version 2 of the standard in 2008-09.

Version 2 is the "go-forward" architecture for the IFX standard.


IFX is committed to maintaining backwards compatibility so that implementations are reliable even as new capabilities are added. The stated policy of IFX is that all specification changes that impact IFX messages must be fully compatible with the previous point revision level of the specification. Specification changes must not require changes by an implementation in order to continue processing at the same level of functionality within a major release level.

IFX introduced Version 2 of the standard in 2008-09. Version 2 is the "go-forward" architecture for the IFX standard.

IFX continues to support v1.x and, within limits, adds new data elements and functionality as required by members to maintain the viability of implementations based on that architecture.

 

Backwards Compatibility

IFX is committed to maintaining backwards compatibility so that implementations are reliable even as new capabilities are added. The stated policy of IFX is that all specification changes that impact IFX messages must be fully compatible with the previous point revision level of the specification. Specification changes must not require changes by an implementation in order to continue processing at the same level of functionality within a major release level.

There are 2 types of compatibility that we are concerned with:

Syntactic compatibility: is the consistent representation of message and data structure, i.e., formats, tag names, and element definitions between old and new levels of the specification.

Semantic compatibility: is the consistent operation of message function, i.e., behavioral consistency between old and new levels of the specification.

There are currently 2 major revision levels supported by IFX commonly referred to as v1.x and v2.x. Consistent with our policy, every point release in the v1.x family from 1.1.0 – 1.8.1 is compatible with lower version releases. We are proud to have maintained that record for over 10 years.

Version 2.x is not directly compatible with version 1.x. The version 2.x framework imposes new structural constraints on IFX Objects; more readily adapts to modern SOA environments and deprecates elements that had been identified as obsolete in version 1. Version 2 is the "go-forward" architecture for the IFX standard.

IFX continues to support v1.x and, within limits, adds new data elements and functionality as required by members to maintain the viability of implementations based on that architecture.

IFX Version 2.x

Version 2 is an architecturally improved version of IFX Business Message Specification (BMS) including refined adaptation to SOA, a consistently applied object model and important new content.  IFX Version 2 continues the Forum's commitment to a business-first, service-oriented approach to standards development.  It deals with shortcomings in Version 1 that could only be effectively addressed by breaking backward compatibility.

IFX Forum recognizes that stability in a standard is imperative; therefore, support for IFX Version 1 will continue for the foreseeable future, including enhancements and additional content driven by the Working Groups.

IFX Version 2.3

IFX 2.3 includes improvements to the automated XSD generator that is available to Forum members and IFX subscribers, and additional material in several areas of the specification, such as the initial submissions from the Loans Working Group that was launched in 2012.

IFX Version 2.2

IFX 2.2 expands the applicability of IFX to new scenarios and situations, such as mobile and Internet banking, making it more flexible and useful for financial services in the 21st century.  Operational improvements and some corrections to existing material have also been also made. 

Important extensions to IFX in Version 2.2 include:

  • Marketing support, such as features for incorporating and tracking marketing campaigns and offers
  • Valuable specific additions, such as provisions for recurring payments and issuing alerts to account holders
  • Administrative enhancements, such as loss tracking and support for card inventory management
  • Provision for parent-child account-to-account relationships
  • Added functionality for account pricing, delinquency tracking, and portfolio segmentation of customers and accounts

IFX Version 2.1

Key updates in IFX 2.1 included:
  • Support of the latest ISO 20022 payment initiation messages and improved mapping of IFX data to ISO 20022
  • Significant improvements to support for services-oriented architecture (SOA), including user-definable services and improved message header support for routing to internal and external service nodes
  • Additional support for card management capabilities, which have greatly expanded the definition of the IFX Card object (credit, debit, rewards, etc.)
  • Improved support of transaction authorizations, including multiple party authorizations
  • Important enhancements for foreign currency conversions and alternate currencies in payment scenarios
  • Improved definition of recurring models for payments, transfers and orders
  • Finalized list of deprecated items from IFX Version 1.x

IFX 2.1 also fixed errata in 2.0.

IFX Version 1.x

For over a decade IFX Forum built upon its service-based architecture and business-first content maintaining backwards compatibility throughout. As SOA principles matured industry-wide and important design patterns within the standard became more clear, IFX Forum members made the important determination in 2007 that it was time to break with backwards compatibility architecturally while maintaining a decade's worth of valuable content development. More than a year of careful analysis and thoughtful design effort following that decision led to the introduction of Version 2.

Version 2 is an architecturally improved version of IFX Business Message Specification (BMS) including refined adaptation to SOA, a consistently applied object model and important new content.  IFX Version 2 continues the Forum's commitment to a business-first, service-oriented approach to standards development.  It deals with shortcomings in Version 1 that could only be effectively addressed by breaking backward compatibility.

IFX Forum recognizes that stability in a standard is imperative; therefore, support for IFX Version 1 will continue for the foreseeable future, including enhancements and additional content driven by the Working Groups.

IFX Version 1.9

Version 1.9 is an enhancement release of the IFX Business Message Specification (BMS), Version 1.  Honoring the Forum's commitment to continued support for IFX Version 1 after the launch of Version 2, the new version's enhancements focus on ATM implementations and compliance with the PCI Data Security Standard.  Operational improvements and some corrections to existing material were also made.

Extensions include:

  • Support for devices that can operate in multiple modes (i.e., clerk/teller-operated vs. customer-operated, depending on the time of day), allowing more dynamic interaction between the terminal and the server
  • Message extension that allows a device to customize operations based on the services a customer is enrolled in, such as mortgage, investment, etc.
  • Europe-focused ATM enhancements, such as support for local security requirements that exceed those covered by the common industry security standards, and support for Germany's Modular Merkmal (MM) card security token
  • Removal of any sensitive authentication data, as defined by the PCI DSS, from consumer-initiated Reverse and Modify messages – applicable across all IFX implementations
  • Support for ATM overdraft notification to customers
  • Enhancements to ATM cash dispensing and check processing modules

IFX License Statement

IFX Forum hereby grants to all users of the IFX Business Message Specification and Data Dictionary (the "Specification") a perpetual, worldwide, royalty-free, nonexclusive, nontransferable license to (a) use the specification in the development of software and/or data compilations which facilitate electronic transmission of information in accordance with the Specification and otherwise implement the Specification in user's products, and (b) market, reproduce, display, and distribute (in any medium known now or in the future) the Specification as implemented in user's products. The foregoing rights may be sublicensed through multiple tiers of distribution, including resellers.

Other than as licensed herein, the IFX Forum shall retain all right, title and interest to any patent, copyrights, trade secrets or other proprietary rights ("Intellectual Property Rights") in the Specification. Subject to all patent rights preserved by IFX Forum members pursuant to Section 5.1 of the "Membership Rules of the Interactive Financial Exchange Forum, Inc.", users shall retain all right, title and interest to the Intellectual Property Rights in any products of user created using the Specification and any modifications, extensions or derivative works of the Specification that user develops or has developed on its behalf as permitted under this Agreement (the "Derivatives"), provided, however, that, users may not hold Derivatives out as being endorsed, sponsored by or affiliated with the IFX Forum.