Skip to main content

PTI and Open Banking

Open banking regimes enable consented access to financial account data through standardized APIs — account information services (AIS), payment initiation services (PIS), and emerging open finance extensions. PTI does not replace open banking rails; it consumes and orchestrates financial data signals into portable trust intelligence across institutions.

1. What open banking is​

Open banking is a regulatory and technical framework requiring banks to expose customer-permissioned data and payment services to third-party providers (TPPs). Key elements:

  • Consent management — explicit, revocable customer authorization
  • AIS APIs — account balances, transaction history, categorization
  • PIS APIs — payment initiation from non-bank applications
  • Technical standards — UK Open Banking, PSD2, Nigeria Open Banking, Brazil Open Finance, etc.
  • TPP registration — licensed or registered third-party access

Open banking answers: What financial account data can this customer share with this provider, under what consent?

2. What problem open banking solves​

ProblemOpen banking response
Data locked in incumbent banksStandardized TPP access
Manual bank statement uploadsAPI-driven income verification
Payment frictionAccount-to-account initiation
Innovation barrier for fintechsLevel playing field for data access

Open banking solves data access and payment initiation. It does not inherently provide cross-institution trust scoring, context isolation, or multi-domain signal composition (rental + employment + merchant alongside cash-flow).

3. What PTI adds​

Open banking

  • Consented account and transaction data
  • Payment initiation
  • Per-consent, per-TPP access scope

PTI adds

  • Cash-flow as trust signals — categorized inflows/outflows → lending context events
  • Cross-source fusion — open banking + partner repayment + community validation
  • Portable pti_id — financial behavior linked to subject graph
  • Institution lookup API — decision-time trust report, not raw transaction dump

Open banking data is often high-sensitivity and consent-bound. PTI ingests derived trust signals — income stability bands, recurring obligation patterns — not raw account numbers in consumer lookup responses, aligning with Privacy minimum-necessary disclosure.

4. How they compose together​

Integration pattern:

  1. Customer grants open banking consent to a trust producer (fintech, aggregator, or bank subsidiary).
  2. Producer derives non-raw trust events — e.g., income.regular, obligation.recurring, balance.volatility_band — and emits to PTI under lending context.
  3. Other partners contribute complementary signals (MFIs, utilities, merchants).
  4. Lending institution requests PTI lookup — receiving explainable drivers without re-implementing open banking connectivity.

Open banking remains the data access rail; PTI is the trust orchestration layer above it.

5. When to use each​

ScenarioOpen bankingPTI
Income verification for loan appRequired (data source)Recommended (signal orchestration)
Account-to-account loan disbursementPIS RequiredNot involved
Portable trust across multiple lendersOB alone insufficientRequired
Rental application without bank linkOB optionalPTI rental context
Regulatory AIS consent auditRequiredPTI respects consent gates

Institutions should not expect PTI to substitute for open banking consent UX or TPP licensing — PTI composes what producers lawfully ingest.

See also​