2FA setup (sign with SMS OTP code)

What is 2FA?

Two Factor Authentication (2FA) is simply an additional layer of security, fortifying access safety by requiring a second (factor) authentication. This authentication method drastically improves user identity legitimacy.

Use of 2FA for Contract Signatures

When 2FA is enabled, you can verify the signatory's legitimacy when a document is being signed; the signatory will receive a one-time password (OTP) on their mobile device (phone number) and will have to submit the OTP in order for the document to be signed.

How to set up 2FA on Contract Signatures

Depending on which provider you choose, you will need a few things to get started.

  • An SMS provider supported by Contract Signatures; currently available ones are:

    • MessageBird

    • Plivo

    • Sinch

    • Twilio

    • Vonage

Once you select your SMS provider, you will need the following:


  • API key

  • Phone number (Provided by MessageBird)


  • Auth ID

  • Auth Token

  • Phone number (Provided by Plivo)


  • Service Plan ID

  • API Token

  • Virtual number (Provided by Sinch)


  • Account SID

  • Auth Token

  • Phone number (Provided by Twilio)


  • API key

  • API secret

  • Phone number (Provided by Vonage)

How do I get this information?

Most of the required information is accessible on your SMS provider account. Below you can access specific guides for each provider to help you gather this information.

The recipient number is obtained from the signatory party as they will need access to this number in order to sign the contract.

The recipient number in Global Settings is for testing purposes only.

Recipient Number(s)

This value is added during contract creation. The signatory will need to have access to this number in order to sign the contract. OTPs will be sent to this number.

Depending on the number of signatories, an option will be available to enable 2FA for each individual.