Participant Enablement
Participant Enablement Kits
PayNet will offer enablement kits to help reduce integration barriers and to accelerate Open Finance readiness by participants.
Benefits to the ecosystem:
Accelerate adoption of the open finance ecosystem by simplifying integration for participants.
Ensure consistency and interoperability across diverse participant systems through uniform implementation standards
Reduce technical barriers and cost of implementation through pre-built connectors and standardized guidelines.
Support future scalability by embedding extensibility and modularity in the design.
Improved user experience through certified UI/UX patterns and seamless app-to-app flows.
Participant Connector Approach
PayNet proposes to help lower integration costs and effort by offering a Connector for the Open Finance Platform, making it easier for participants to join and benefit from the Open Finance ecosystem.
UI/UX Guideline & Certification Approach
PayNet will provide UI/UX and design guidelines for key screens and user flows. This is to make it easier for participants to craft their journeys and build their front-end interface.
Please refer to the UIUX Guidelines for the detailed flow:
Centralised Consent Management Dashboard for DPs & DCs
PayNet proposes to provide a Centralised Consent Management Dashboard for both DC & DP.
Both DC and DP will access the same PayNet Consent Dashboard.
Dashboard is delivered as a responsive web app rendered within DP/DC app where the consent list is fetched directly from PayNet OFP
Unified Access
Both DC and DP access the same web-rendered Consent Management Dashboard from their applications, ensuring a consistent experience for all users.Consistent User View
Users see a single, unified display of all their active and historical consents of all parties, regardless of whether they enter from an DC or DP application, making it easy for users to review and manage their data sharing relationships.Direct Backend Connection to PayNet OFP
When a user chooses to revoke a consent from the dashboard, the action is sent directly to the OFP backend and processes the revocation in real time without having DP or DC trigger the revocation endpoint.
App-to-App & Web-to-App: Universal Link Approach
PayNet proposes using Universal Links as the sole method for authentication and authorizationredirection to the DP app, as this approach provides the best and most seamless user experience and follows best practice.
PayNet will provide a Universal Link specification document together with the sandbox availability at the end of Q4 2025.
Custom Endpoint for future scalability
A custom endpoint is a separate API or feed that allows Data Providers to share additional data beyondthe standard Open Finance fields.
This enables flexibility without changing the core API that everyone else uses.
Why it matters
Supports richer use cases: Enables DP to share data specific to their products or customer e.g loyalty points, without being limited by a fixed schema
Preserves standardisation: Keeps the core API lean and stable, so everyone can rely on a consistent baseline, while still allowing flexibility where needed
Accelerates innovation: Lets institutions respond to business or regulatory needs quickly, without waiting for industry-wide schema updates
Adoption is flexible: Data Providers and Consumers only integrate if relevant — ensuring flexibility without adding unnecessary complexity for others
How it works
Custom endpoint is set up by the Data Provider(e.g. /accounts/custom-endpoint)
It shares non-standard data related to accounts, transactions, or users
DC can call this endpoint if they have bilateral agreements with Data Provider
Delivery Methods Supported
JSON API
CSV feed
Not finding the help you need?