September 6 — NACHA, the Electronic Payments Association, has partnered with Afinis, a membership-based standards organization that brings together collaborators to develop implementable, interoperable and portable standards across operating environments and platforms. NACHA hopes Afinis will further the work of the association’s Payments Innovation Alliance Application Programming Interface (API) Standardization Industry Group (ASIG) to advance API standardization efforts across the financial services ecosystem through formal governance and includes the work of Interactive Financial eXchange Forum (IFX).
Utilizing the Herndon, Va.-based Afinis’ platform for standardized API product discovery, application testing and developer collaboration, API products are developed for use by financial institutions, fintechs and solution providers, businesses, and governments. Afinis employs a transparents governance process to provide confidence for standards use and development of products and solutions.
“The financial services industry is using APIs to broaden and enhance services, increase automation and strengthen security,” said NACHA President and CEO Janet O. Estep. “API standardization is critical for the financial services industry to reap its full potential beyond the confines of proprietary systems.
“Afinis … collaborates openly with groups from around the world to share learning, reduce duplicative efforts and create and adopt standards that lessen friction and improve the ability to bring innovations more quickly to market,” Estep continued.
ASIG was established in the spring of 2017 to support advancement and use of standardized APIs within the U.S. financial services industry. Within 15 months, the group had developed 16 initial API use cases, launched an online community, published “API Standardization – Shaping the Financial Services Industry,” and released the API standard for account validation and API standard for Get Bank Contact Information.
Current Afinis work includes the following API use cases:
- Get Transaction Status: An originator or originating depository financial institution wants to check the status of a transaction to verify that funds were deposited or withdrawn from the receiving account. This API use case allows an originator of an ACH transaction to check the status of a submitted payment instruction.
- B2B Payments Interopreability: B2B payment service providers want better interoperability so businesses (particularly small businesses) can receive and make B2B payments without multiple enrollments or learning multiple formats and systems. This API use case allows a company to obtain correct payment information and remittance requirements to pay another company via ACH.
- Originate ACH Payment: Standardized APIs allow businesses to submit ACH payment instructions without having to access multiple systems and track scheduling. Businesses gain consistency and continuity across multiple bank ACH relationships, improved reporting and access to faster payments.
Afinis seeks to provide a collaborative venue for stakeholders to:
- Broaden use of standardized APIs both in the U.S. and globally
- Develop a technical environment with the infrastructure needed to support discovery, testing and adoption of standards
- Provide governance to support decision-making on technologies, standard life cycles and user terms
- Leverage NACHA’s core competencies in developing and maintaining rules and standards, and as an impartial convener, educator and certification/accreditation authority
- Engage with other standards bodies, countries and market infrastructures to achieve interoperability, and develop, update and review relevant security, data and technical guidelines
- Support the IFX standards user community to foster better awareness and adoption, and to support existing IFX-based standards for web banking, mobile banking and ATM verticals
Access to the Afinis online community, developer sandbox and the Afinis interoperability standards are freely available for everyone. New members are welcome to join and should contact firstname.lastname@example.org.