Value proposition

The Contract Signature API provides the operations required to handle the e-signature process on a prepared contract.

Key features

The main service allows the launch of a signature process. It thus involves the creation of the contract document (in PDF format), the creation of the e-signature envelop and the initiation of the e-signature process itself.

The e-signature process being asynchronous, the BPLS systems provides notification to the partner on each event happening. On reception of these notifications (on the partner-provided callback API), the GET service offers access to the new (detailed) status of the e-signature.

In the current version, the e-signature process is launched once and only once and no modification are allowed on the envelop after the process has be initiated.

Events

The following events generate a notification (see Notification Subscription for details on their reception and see the OAS Doc for details on these statuses).

• In progress (any change during the e-signature process, as long as it is not complete or in error)
• Expired (the e-signature process is no longer valid, after a set period).
• Refused (one signatory has refused to sign).
• Cancelled (the envelope has been cancelled by BPLS)
• In error (with various cases, including at the signatory level)
• Complete (all signatories have signed successfully)

Use cases

The initialization of the signature is possible when the prepared contract has been created and populated with valid bank information and at least one authorized signatory. It launches the e-signature process on the contract.

On reception of notifications of a status change on the e-signature (pushed through the partner-provided callback API), the partner should access to the signature to capture the current status. At a minimum, they should handle the completion of the e-signature, both in case of success and failure.