`POST /v1/recipient/consents/start`
POST/v1/recipient/consents/start
Start consent.
start consent authorization.
The two-ledger recipient flow (bank8-open-ca DESIGN.md §1 + §4 consent-flow
sequence): the recipient-side open-banking instance writes its OWN registry
(a pending row in recipient_consents, in the recipient tenant),
ensures its per-provider OAuth client exists at the provider's
authorization server (DCR, cached in open_ca.recipients), and pushes a
PAR request whose state carries "<consent handle>|<app origin>".
The AS's authorize screen runs the ceremony; the browser redirect
comes back to THIS instance's /fdx/consents/callback (the
registered redirect_uri), which activates the row and exchanges the
code. The provider's grant row is seeded by the provider's OWN
auth-family consumer from sentin8:auth:grant:created - never by
this side.
Request
Responses
- 200
- 403
OK
Missing fdx:read scope