aplonAPI

What is aplonAPI?

aplonAPI is an API-management framework tailor-made for banks and financial institutions. It covers the regulatory side of PSD2 — the interfaces banks must open to licensed third parties — and goes further, letting a bank build, manage, distribute and monetise its own APIs for Banking-as-a-Service (BaaS) and Banking-as-a-Platform (BaaP) offers. It is powered by ACI Worldwide and delivered and integrated by Infosistema.

What are Open Banking and PSD2?

Open Banking is the practice of sharing financial information electronically, securely and with the customer's prior approval: a third party can only access a customer's data after the customer opts in. In Europe it arrived with the second Payment Services Directive (PSD2), which came into effect on 13 January 2018, with banks required to implement it by 14 September 2019.

Under PSD2, banks — ASPSPs (account servicing payment service providers) — must give licensed third parties access through APIs:

• AISPs (account information service providers) read account data, with the customer's consent;
• PISPs (payment initiation service providers) initiate payments from the customer's account;
• funds-availability checks confirm whether an amount is available for a card-based payment.

Access must be protected by strong customer authentication (SCA) and limited to third parties whose identity is verified with eIDAS qualified certificates issued by a QTSP (qualified trust service provider) and checked against the regulators' registers.

What problem does aplonAPI solve?

Banks had to open these interfaces on regulatory deadlines, with SCA, consent and third-party verification in place, and without exposing the core banking system. Most stopped at the regulatory minimum. Yet the same API layer can become a distribution channel: products offered through partners, integration with point-of-sale systems for easier credit, or with bookkeeping and ERP solutions so business customers can bank from the tools they already use. aplonAPI covers both the compliant layer and the commercial API programme on top of it.

How does aplonAPI work?

aplonAPI is organised in three stages:

Build - a complete set of ready APIs to use immediately; - a flexible connectivity layer that connects to the bank's existing core systems; - the bank's own or third-party custom APIs can be added for its digital projects; - everything needed to run internal or public bank APIs that are PSD2-compliant.

Manage - an API store to administer multiple exposed APIs; - granular control of users' roles and permissions; - client-app registration to safeguard API access; - real-time usage logging for detailed auditing and reporting.

Distribute - a branded developer portal with complete documentation and code examples, customisable to match the bank's website; - a streamlined registration process, integrated with the API-management module; - a sandbox with sample users and accounts, so third parties can develop and test with minimal support; - billing and SLA modules to monetise API usage.

Which standards and APIs does aplonAPI support?

• PSD2 / SCA — strong customer authentication, consent management and TPP verification.
• Account Information (AIS), Payment Initiation (PIS) and Funds Availability APIs.
• OAuth2 consent flows.
• eIDAS / QTSP certificate verification, with real-time EBA-register checks.
• Berlin Group and Open Banking UK API standards.
• Value-added APIs — for example KYC, account opening or reconciliation — exposed and billed through the portal.

Who is aplonAPI for?

Banks and other financial institutions acting as account servicing payment service providers (ASPSPs) that must comply with PSD2 and want to turn their APIs into a product. On the other side of the portal, it serves the third-party providers (AISPs and PISPs) and fintechs that consume the bank's APIs.

Who develops aplonAPI?

aplonAPI was developed by Payment Components, a fintech founded in 2014 that specialises in API management, Open Banking and financial messaging, and Infosistema's strategic partner for PSD2 since 2018. ACI Worldwide acquired Payment Components in November 2025, including its technology, intellectual property and team, and is integrating it into its payments platform. Infosistema continues to deliver and integrate aplonAPI for banks.

What can aplonAPI do?

Where is aplonAPI used?

How does Infosistema deliver aplonAPI?

Open Banking projects succeed or stall on integration. Infosistema pairs aplonAPI with its enterprise integration and data experience and covers the full cycle — from publishing the APIs to connecting fintechs and their use by customers:

• Strategy and architecture — defining the information-systems strategy and service architecture for the bank's API programme;
• Core integration — connecting the API layer to core banking and payment systems without exposing them directly;
• Security and compliance — setting up SCA, consent and TPP verification, real-time transaction monitoring, alerting and audit trails for regulatory reporting;
• Go-live and operation — opening the sandbox and developer portal to third parties, then supporting production;
• Extension — adding the bank's own value-added APIs and commercial models.

At Banco Invest, Infosistema delivered full PSD2 compliance on schedule through a secure aplonAPI-based API layer, with real-time monitoring and a complete audit trail.

aplonAPI in production

Related products