Open Banking Compliance Solution
Salt Edge
Salt Edge provides an Open Banking and PSD2 Compliance (Europe, UK, Australia, Brazil) solution covering all essential components required by regulators: Testing and Live environment for the TPPs for Account Information API & Payment Initiation API, the TPP Developer Portal, the TPP Management & Verification API, Consent Management SDK for banks web interface, a fallback channel and/or exemption from it. Additionally, we provide mobile-first application to comply with SCA and Dynamic Linking requirements.
Open Banking regulatory requirements are complex, and their implementation requires specific expertise that is not available in majority of banks. Development and maintenance are costly and developing the PSD2 APIs in-house can take up to 1 year – but regulators pressurize the Financial Institutions to meet deadlines.
Minimal Resources
Spare the cost of development, maintenance, and support. With Open Banking Compliance Solution, the client has minimal involvement in the technical implementation.
Be compliant with PSD2/OB requirements in 1 month
Pre-integration with Fusion Essence and Equation using APIs on FusionFabric.cloud allows clients to go live in one month.
Proven off-shelf solution
Salt Edge’s OB Compliance solution has a proven track record of success with more than 100+ API implementations for financial institutions globally. All TPP verification, communication, developer portal, API versioning and alignment with regulatory requirements are done by the vendor. SE PSD2 Solution was audited by third parties.
General information
How it works
TPP Dedicated API
TPP Dedicated API includes a set of services that allow seamless TPP interaction with a bank’s Compliance API. The solution is managed by Salt Edge and includes The Developer Portal, sandbox and production environments, detailed documentation for fast TPP integration, first line of support for TPPs, and much more.TPP Verification System
Banks must grant regulated TPPs access to their AISP & PISP channels. Bank should check the validity of the eIDAS/OBIE certificates of each TPP willing to on-board or request access to the APIs based on the user consent.Compliance Core
This is the processing part of the solution. Includes the: Basic APIs (Account Information API, Payment Initiation API and PIISP API for Confirmation of funds), the value-added APIs (Availability API and Consent Management API) and the Authorization API.ASPSP Dashboard
The bank dashboard enables the managers to be in full control of the compliance system - monitor the latest activity of Bank, TPPs, and end-users that are using such third parties: TPP Management and Monitoring, Ticketing system, Roles management and Automatic statistics and reports extraction that are requested by the regulator.Consent management API
Banks can help end-users gain control over the data shared with TPPs by adding a consent management feature to existing banking channels that handles the following: store the list of all active consents and log the historical consents, manage consents and notify TPPs in case the user has revoked a consent in ASPSP's domain.
How it looks
ASPSP Dashboard
In this environment, a Bank can view all currently active consents, revoke any of them at any time, and review the history of all granted consents. Show lessConsent Management API
The consent management API is a value-added part of the compliance solution, banks will be provided with the API endpoint. This will help the bank to add an additional page in its current mobile/web-interfaces for end-users, allowing them to manage all the consents. Show less
