Scribd
Upload
348 views1 page

User Flow - API + Callback Privy ID

The document describes the user registration and document signing workflow between a user, merchant, and Privy system. It involves the following key steps: 1. A user registers with the Privy system by providing registration data to the merchant API which is received by the Privy system. 2. The Privy system conducts a verification process and notifies the merchant API of the registration status. 3. If verified, the user can upload documents to the Privy system through the merchant API by providing the document PDF, Privy IDs of the owner and recipients. 4. The Privy system receives the uploaded document, shares it with recipients, and provides a document token and signing URL to the merchant

Uploaded by

Nurfitri Anbarsanti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
348 views1 page

User Flow - API + Callback Privy ID

The document describes the user registration and document signing workflow between a user, merchant, and Privy system. It involves the following key steps: 1. A user registers with the Privy system by providing registration data to the merchant API which is received by the Privy system. 2. The Privy system conducts a verification process and notifies the merchant API of the registration status. 3. If verified, the user can upload documents to the Privy system through the merchant API by providing the document PDF, Privy IDs of the owner and recipients. 4. The Privy system receives the uploaded document, shares it with recipients, and provides a document token and signing URL to the merchant

Uploaded by

Nurfitri Anbarsanti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

User Merchant Privy ID

Start

User registration

Input User API Privy System Receive


Registration Data Registration User's Data

Response:
userToken

Verification
Process in Privy

Input
userToken

API Registration
Verified
Status

Yes No

Email:
Verified User
PrivyID+Password

Email:
Invalid User
Invalid User

Submit
Supporting
Documents

Email:
Rejected User
Rejected User

Callback
Registration
Status

Merchant
Webhook URL

Upload Doc

Input
Document PDF +
Privy ID owner +
Privy ID recipient

Privy System Receives


API
Uploaded Document &
Upload Document
Share to Recipients

Response:
- DocToken
- URL Doc Signing
iframe
Email:
Doc needs to be
signed by recipients
URL Signing
Privy
Mobile App
Doc Signing by
iframe
User

Privy
Website
Doc
Token
Input
DocToken

API Check
Completed
Doc Status

No
Yes

Yes

Yes
Email:
Doc is Completed - Doc Status (Completed)
(Doc Owner Only) - URL Download (only
when doc is completed) - Callback Doc
*) Signers can download valid for 15 minutes Status
Signed Document

Doc Status
(In Progress)

You might also like