API & integration
The six DPIP APIs, all hosted centrally (screening and feedback optionally at the Edge Node) and invoked by the participating institution.
DPIP API inventorycontract
| API | Hosted by | Called by | Purpose | Mode |
|---|---|---|---|---|
| /report | DPIP | Participating Institutions | Submit suspected entities to the Smart Registry. Status alert or suspect. | Async, batched |
| /check | DPIP or Edge | Participating Institutions | Screening the registry — onboarding, profile change, beneficiary addition, transaction. | Sync, real time |
| /feedback | DPIP or Edge | Participating Institutions | Communicates the outcome of a screening back to the registry. | Async |
| /revoke | DPIP | Participating Institutions | Withdraw a previously submitted report or linked identifier. | Async |
| /dispute | DPIP | Participating Institutions | Contest a report that pertains to a genuine customer of the disputing institution. | Async |
| /augment | DPIP | DPIP | Invokes an augmentation request from all PIs when an identifier is reported. | Async |
Not yet callable. Base URLs, client certificates, the salt-management scheme and the PI-ID are issued by IDPIC at onboarding. This console runs against a local simulation of the contract so the bank-side build and UAT can proceed before credentials land. Nothing here is a live registry connection.
Transport & authentication§7
Salting
Institution-held salt, rotated on a published schedule.
SHA-256
Every identifier hashed before it leaves the bank perimeter.
JWS
Payload signed with the institution key; kid carries the PI-ID.
mTLS
Mutual TLS on every call, client certificate issued at onboarding.
Onboarding milestones13 weeks to go-live
| Milestone | Target period | Outcome |
|---|---|---|
| Kick-off and requirements alignment | Week 1 to 4 | Team alignment · internal approvals · infrastructure readiness · SRS finalisation |
| API and environment setup | Week 5 to 10 | UAT setup · bank-side development against the Smart Registry · test run for ingestion and screening |
| UAT and go-live | Week 11 to 13 | Pre-live clearances and audit · go-live sign-off · production deployment |
| In production | Week 14 onwards | Post go-live tuning · maintenance and support |
Event logthis session
no calls yet…