Open Banking API

Open Banking exposes the institution's data + payment rails to third-party providers (fintechs, aggregators, accounting tools) under PSD2-style consent. AISP (account information) + PISP (payment initiation).

TPPs list — Registered TPPs — third-party providers with status, scopes and consent counts.

How a TPP onboards

A third-party provider registers a client, the suite issues credentials, and the TPP can then make AISP / PISP calls scoped by the consent each member grants them.

TPP fills the onboarding form (or admin creates manually).
Admin approves in Open Banking → TPPs.
Suite issues client ID + secret; TPP receives via secure email.
TPP can now request consent from any member to call AISP / PISP on their behalf.

Reference

Feature checklist

OAuth2 authorization server
AISP + PISP endpoints
Member consent capture with revoke
TPP onboarding + certificate management

Configuration reference

Where	What to set
OAuth client config	Issuer, JWKS URI, supported scopes
TPP registration	Self-service or manual approval

Roles & permissions

Group	Capability
mfi_open_banking_api.group_ob_admin	TPP onboarding

Accounting integration

PISP-initiated payments inherit standard transfer postings.

Tip. Test consent flow end-to-end before publishing TPP onboarding — broken consents create silent payment failures.