In this article

• Objective

• Steps

  • Create a Client ID and Secret pair

  • Complete integration setup within Coconut

• Hot Tips!

• A note on access and visibility

Objective

Enable customers to complete document signing within a Connect call by integrating OneSpan™ Sign with Coconut Connect.

NOTE: Coconut Connect is an add-on feature. Please connect with your Customer Success Manager to get started.

Steps

Integrating OneSpan Sign with Coconut Connect requires creating a Client ID and Secret pair for Connect in your organization’s OneSpan account and then completing integration setup within Coconut using this information.

Create a Client ID and Secret pair

A Client ID and Secret for Coconut Connect are required within your OneSpan Sign account. To create a Client ID and Secret pair, login to your OneSpan Sign account owner’s sender portal and complete steps 1 and 2 in this article.

Complete integration setup within Coconut

Once the Client ID and Secret pair are created, integration setup within Coconut can be completed. To complete setup:

1. From the navigation menu, click Settings

2. From Integrations & API, click E-signatures

3. From E-signature Platforms>OneSpan Sign, click Connect

4. Enter the Client ID and Secret, as created in OneSpan Sign

5. Select the Account URL for your organization’s OneSpan Sign account

6.  

   • NOTE: If none of the provided options matches your organization’s OneSpan Sign account, it is often because a custom URL has been implemented for the account; click Custom URL and then enter your organization’s custom OneSpan Sign URL

7. Click Connect

Enter the OneSpan Client ID & Secret pair you created to connect the integration with Coconut Connect

The integration setup is complete. Staff members can now access their OneSpan Sign account when using Connect to collect e-signatures from call participants.

Hot Tips!

Some items to note for your organization’s OneSpan Sign + Coconut Connect users:

• Coconut Connect meetings must be associated with either an appointment or a walk-in to leverage e-signature workflows during a Connect call

• Only OneSpan Sign transactions that are both sent and unsigned are accessible from Coconut Connect

• Only OneSpan Sign transactions that are accessible in OneSpan Sign by the logged-in user will display in Coconut Connect for that user

• A signer in OneSpan Sign and participant in Coconut Connect are matched by email address; if no match is found, the Coconut Connect call organizer is asked to select the correct Connect participant to match the OneSpan Sign signer

A note on access and visibility

Admin users can integrate OneSpan Sign as an e-signature provider within Coconut Connect by accessing Settings.