Unterschreiben mit FP Sign
Geschäftsdokumente unterschreiben, versenden und tracken.
Enable Direct Document Signing with FP Sign DSS Intents
Prepare a FP Sign link for the creator to sign a document directly. This use-case is simply for users with FP Sign account to sign a document in FP Sign and return to your application.
-
You are sending the document(s) and some configuration to FP Sign.
-
You'll receive a token.
-
The token equals the later batch-Id.
-
-
The token gets opened in a browser by the user. There you can self-sign a document.
-
The user gets redirected to the given redirect-url.
-
You are checking the status and waiting for the batch to finish.
-
You are downloading the signed file and optional the signature report.
TABLE OF CONTENTS
loading...
Step 1 (optional)
Check recipients signature capabilities
Before preparing a signature, it is recommended to verify the signers’s available signature methods. This endpoint returns information about a user’s registered authentication and signing capabilities.
Use this to avoid errors, for example when requesting a signature with mobile TAN for a signer who does not have a mobile number stored in their account OR requesting a qualified signature without having the capabilities for it.
Step 2
Create a DSS
This endpoint creates a DSS-intent. There's no need to self-build an user-interface to sign. The signature creation gets "delegated" to FP Sign's UI.
When calling this endpoint, the only required data is the originator/signer of the signature and documents for FP Sign. Once created the token equals your batch-Id.
*required
originator* Owner of the signature process
processes* List of documents and for the signature process
canChange{...} All "can change"-settings allow your application to control whether the user is allowed to change parameters when opening the intent
navigationDetails Redirect and button-naming after batch-intent has been created and send
Step 3
Open the browser
You have received a token. Open the token in a browser using this link:
/tokens/dss-intents/{token}
Step 4
Get dss status
Get the current status of a dss. It allows you to determine whether the dss has finished or moved into another state. Getting the status by polling can later be reduced by f.e. reacting on the user's redirect/redirect-url, implementing webhooks or optimizing the logic: The older the dss the less you can poll for it's status.
In addition, the endpoint returns the individual status of each document within the batch, providing insight into the progress of each document inside the signature process.
Save each "dssProcessId".
Step 5
Get files
For each dssProcessId download the file and optional the signature report.
Ready to build your own FP Sign integration?
Find an online appointment with our FP Sign consultants. Solve necessary integration steps instantly.