BIAN · Party Reference Data

Party

:8085 · openbank-party

The customer identity behind the accounts — readable only with the ReadParty permission.

What it is

The Party microservice implements the BIAN Party Reference Data service domain and the OBIE /party resource. It returns the customer identity associated with an account, released only when the authorised consent carries the ReadParty (or ReadPartyPSU) permission.

DEPENDS ON ↳ openbank-consent

Key endpoints

Speaks the OBIE contract on the wire. A selection of the endpoints this service exposes:

Method	Path	Purpose
GET	`/accounts/{id}/party`	Read the party for an account (ReadParty permission)
GET	`/party`	Read the PSU party (ReadPartyPSU permission)

Run it — zero infrastructure

Clone the repo and start the service with an in-memory store. No database required to try it.

# clone and run (in-memory store, no infra)
git clone https://github.com/Sreenivas-Sadhu-Prabhakara/openbank-party.git
cd openbank-party && go run .

# it is now serving OBIE on :8085
curl localhost:8085/health

FAQ

What is Party Reference Data?

In BIAN, Party Reference Data is the service domain that manages the reference information about the people and organisations a bank deals with. Here it exposes the customer identity linked to an account.

How is access controlled?

Party data is released only when the authorised consent explicitly carries the ReadParty or ReadPartyPSU permission — consent scope is checked on every read.

Is it production-ready?

No — educational reference, FAPI stubbed, not certified.

Explore the estate

openbank-bian rebuilds UK Open Banking as five consent-first services. Explore the rest:

▲ openbank-bian — overview Consent :8081 Accounts :8082 Payments :8083 Funds :8084