Verifier creates with Nats message on his side an authorization request link for Holder - this creates in Database a Record which gives this link the right to directly post presentations to this id
Verifier sends link over any channel to Holder or simply redirects to it
Holder Instance of Service will download request object, and stores it in db, notification is sent
---------------------OCM Part---------------------
API selects an identity and presentation can be completed over the internal routes by sending an presentation submission to the internal PUT endpoint
---------------PCM Cloud Part --------------------
redirect to the cloud wallet if the external link is configured
User authenticates and claims the proof request id
User can either fill out the presentation definiton or collect it for later
User clicks Transmit after selection, selects an identity and presentation can be completed over the internal routes by sending an presentation submission to the internal PUT endpoint
Redirect back to the redirect uri from the downloaded request object