User Guide Cancel

WhatsApp authentication

Last updated on 22 Apr 2025

Adobe Sign

Open app

Adobe Acrobat Sign Guide

What's New

Get Started

Administer

Admin Console Overview
User Management
1. Adding users
2. Create function-focused users
  1. Technical accounts - API driven
  2. Service accounts - Manually driven
3. Check for users with provisioning errors
4. Change Name/Email Address
5. Edit a user's group membership
6. Edit a user's group membership through the group interface
7. Promote a user to an admin role
8. User Identity Types and SSO
9. Switch User Identity
10. Authenticate Users with MS Azure
11. Authenticate Users with Google Federation
12. Product Profiles
13. Login Experience
Account/Group Settings
1. Settings Overview
2. Global Settings
  1. Account tier and ID
  2. New Recipient Experience
  3. Self Signing Workflows
  4. Send in Bulk
  5. Web Forms
  6. Custom Send Workflows
  7. Power Automate Workflows
  8. Library Documents
  9. Collect form data with agreements
  10. Limited Document Visibility
  11. Attach a PDF copy of the signed agreement
  12. Include a link in the email
  13. Include an image in the email
  14. Files attached to email will be named as
  15. Attach audit reports to documents
  16. Merge multiple documents into one
  17. Download individual documents
  18. Upload a signed document
  19. Delegation for users in my account
  20. Allow external recipients to delegate
  21. Authority to sign
  22. Authority to send
  23. Power to add Electronic Seals
  24. Set a default time zone
  25. Set a default date format
  26. Users in Multiple Groups (UMG)
    1. Upgrade to use UMG
  27. Group Administrator Permissions
  28. Replace recipient
  29. Audit Report
    1. Overview
    2. Allow unauthenticated access on the transaction verification page
    3. Include reminders
    4. Include view events
    5. Include agreement page/attachment count
  30. Transaction Footer
  31. In Product Messaging and Guidance
  32. Accessible PDFs
  33. New authoring experience
  34. Healthcare customer
3. Account Setup
  1. Add logo
  2. Customize company Hostname/URL
  3. Add company name
  4. Post agreement URL redirect
4. Signature Preferences
  1. Well formatted signatures
  2. Allow recipients to sign by
  3. Signers can change their name
  4. Allow recipients to use their saved signature
  5. Custom Terms of Use and Consumer Disclosure
  6. Navigate recipients through form fields
  7. Restart agreement workflow
  8. Decline to sign
  9. Allow Stamps workflows
  10. Require signers to provide their Title or Company
  11. Allow signers to print and place a written signature
  12. Show messages when e-signing
  13. Require signers to use a mobile device to create their signature
  14. Request IP address from signers
  15. Exclude company name and title from participation stamps
  16. Apply Adaptive Signature Draw scaling
5. Digital Signatures
  1. Overview
  2. Download and sign with Acrobat
  3. Sign with Cloud Signatures
  4. Include metadata for Identity Providers
  5. Restricted Cloud Signatures Providers
6. Electronic Seals
7. Digital Identity
  1. Digital Identity Gateway
  2. Identity Check policy
8. Report Settings
  1. New report experience
  2. Classic report settings
9. Security Settings
  1. Single Sign-on settings
  2. Remember-me settings
  3. Login password policy
  4. Login password strength
  5. Web session duration
  6. PDF encryption type
  7. API
  8. User and group info access
  9. Allowed IP Ranges
  10. Account Sharing
  11. Account sharing permissions
  12. Agreement sharing controls
  13. Signer identity verification
  14. Agreement signing password
  15. Document password strength
  16. Block signers by Geolocation
  17. Phone Authentication
  18. Knowledge-Based Authentication (KBA)
  19. Allow page extraction
  20. Document link expiration
  21. Upload a client certificate for webhooks/callbacks
  22. Timestamp
10. Send Settings
  1. Show Send page after login
  2. Require recipient name when sending
  3. Lock name values for known users
  4. Allowed recipient roles
  5. Allow e-Witnesses
  6. Recipient groups
  7. CCs
  8. Recipient Agreement Access
  9. Required fields
  10. Attaching documents
  11. Field flattening
  12. Modify Agreements
  13. Agreement name
  14. Languages
  15. Private messages
  16. Allowed signature types
  17. Reminders
  18. Signed document password protection
  19. Send Agreement Notification through
  20. Signer identification options
    1. Overview
    2. Signing password
    3. Knowledge-based authentication
    4. Phone authentication
    5. WhatsApp authentication
    6. One-Time Password via Email
    7. Acrobat Sign authentication
    8. Cloud-based digital signature
    9. Government ID
    10. Signer Identity reports
  21. Content Protection
  22. Enable Notarize transactions
  23. Document Expiration
  24. Preview, position signatures, and add fields
  25. Signing order
  26. Liquid mode
  27. Custom workflow controls
  28. Upload options for the e-sign page
  29. Post-sign confirmation URL redirect
11. Message Templates
12. Bio-Pharma Settings
  1. Overview
  2. Enforce identity authentication
  3. Signing reasons
13. Workflow Integration
14. Notarization Settings
15. Payments Integration
16. Signer Messaging
17. SAML Settings
  1. SAML Configuration
  2. Install Microsoft Active Directory Federation Service
  3. Install Okta
  4. Install OneLogin
  5. Install Oracle Identity Federation
18. Data Governance
19. Time Stamp Settings
20. External Archive
21. Account Languages
22. Email Settings
  1. Email header/footer images
  2. Permit individual user email footers
  3. Customize the Signature Requested email
  4. Customize the To and CC fields
  5. Enable Linkless Notifications
  6. Customize email templates
23. Migrating from echosign.com to adobesign.com
24. Configure Options for Recipients
Guidance for regulatory requirements
1. Accessibility
2. HIPAA
3. GDPR
4. 21 CFR part 11 and EudraLex Annex 11
5. Healthcare customers
6. IVES support
7. "Vaulting" agreements
8. EU/UK considerations
Download Agreements in Bulk
Claim your domain
Report Abuse links
System Requirements and Limitations
1. System requirements
2. Transaction limits

Send, Sign, and Manage Agreements

Recipient Options
1. Cancel an email reminder
2. Options on the e-signing page
Send Agreements
1. Send (Compose) page
  1. Overview of landmarks and features
  2. Group selector
  3. Adding files and templates
  4. Agreement name
  5. Global Message
  6. Completion Deadline
  7. Reminders
  8. Password protect the PDF
  9. Signature type
  10. Locale for the recipient
  11. Recipient signature order/flow
  12. Recipient roles
  13. Recipient authentication
  14. Private message for the recipient
  15. Recipient agreement access
  16. CC'd parties
  17. Identity check
2. Send an agreement only to yourself
3. Send an agreement to others
4. Written Signatures
5. Recipient signing order
6. Send in Bulk
Authoring fields into documents
1. In-app authoring environment
2. Create forms with text tags
3. Create forms using Acrobat (AcroForms)
  1. AcroForm creation
  2. Creating accessible PDFs
4. Fields
  1. Field types
    1. Common field types
    2. E-signature fields
    3. Initials field
    4. Recipient name field
    5. Recipient email field
    6. Date of signing field
    7. Text field
    8. Date field
    9. Number field
    10. Checkbox
    11. Radio button
    12. Drop-down menu
    13. Link overlay
    14. Payment field
    15. Attachments
    16. Participation stamp
    17. Transaction number
    18. Image
    19. Company
    20. Title
    21. Stamp
  2. Field content appearance
  3. Field validations
  4. Masked fields values
  5. Setting show/hide conditions
  6. Calculated fields
5. Authoring FAQ
Sign Agreements
Manage Agreements
Audit Report
Reporting and Data exports
1. Overview
2. Grant users access to reporting
3. Report charts
4. Data Exports
5. Rename a report/export
6. Duplicate a report/export
7. Schedule a report/export
8. Delete a report/export
9. Check Transaction Usage

Advanced Agreement Capabilities and Workflows

Webforms
Reusable Templates (Library templates)
Transfer ownership of web forms and library templates
Power Automate Workflows
1. Overview of the Power Automate integration and included entitlements
2. Enable the Power Automate integration
3. In-Context Actions on the Manage page
4. Track Power Automate usage
5. Create a new flow (Examples)
6. Triggers used for flows
7. Importing flows from outside Acrobat Sign
8. Manage flows
9. Edit flows
10. Share flows
11. Disable or Enable flows
12. Delete flows
13. Useful Templates
  1. Administrator only
  2. Agreement archival
    1. Save your completed documents to SharePoint
    2. Save your completed documents to One Drive for Business
    3. Save your completed documents to Google Drive
    4. Save your completed documents to DropBox
    5. Save your completed documents to Box
  3. Webform agreement archival
    1. Save completed web form documents to SharePoint Library
    2. Save completed web form documents to OneDrive for Business
    3. Save completed documents to Google Drive
    4. Save completed web form documents to Box
  4. Agreement data extraction
    1. Extract form field data from your signed document and update Excel sheet
  5. Agreement notifications
    1. Send custom email notifications with your agreement contents and signed agreement
    2. Get your Adobe Acrobat Sign notifications in a Teams Channel
    3. Get your Adobe Acrobat Sign notifications in Slack
    4. Get your Adobe Acrobat Sign notifications in Webex
  6. Agreement generation
    1. Generate document from Power App form and Word template, send for signature
    2. Generate agreement from Word template in OneDrive, and get signature
    3. Generate agreement for selected Excel row, send for review and signature
Custom Send workflows
Share users and agreements
1. Share a user
2. Share agreements

Integrate with other products

Acrobat Sign Developer

Support and Troubleshooting

Add an extra layer of security by sending a one-time passcode (OTP) to the recipient’s smartphone via WhatsApp.

WhatsApp authentication is a premium two-factor verification method that adds strong identity protection. A one-time passcode is sent to the recipient’s phone through the WhatsApp app, and they must enter this code to access the agreement.

The recipient must have an active WhatsApp account, and the phone number linked to that account must be provided to the sender to set up authentication.

Availability:

Acrobat Standard and Acrobat Pro: Not Supported
Acrobat Sign Solutions: Supported; Disabled by default
Acrobat Sign for Government: Not Supported

WhatsApp authentication is a premium method and incurs a per-use charge.

Transactions must be purchased in advance through your Adobe sales representative.
Transactions are managed at the account level—all groups draw from the same shared pool.
WhatsApp authentication shares this pool with Phone/SMS authentication methods.

Configuration scope:

Administrators can enable this feature at the account and group levels.

Access this feature by navigating the administrator's configuration menu to Send Settings > Signer Identification Options

How it's used

When WhatsApp authentication is configured, recipients receive an email message prompting them to enter a verification code to access the agreement. This message includes:

The last four digits of the phone number that was configured during the agreement setup so the recipient can confirm where the code will be sent.
The sender's name (or designated contact), in case the recipient needs help—for example, to update the phone number on file.

When ready, the recipient selects Send Code to receive the one-time passcode via WhatsApp.

After the recipient selects Send Code:

The page refreshes to display a field for entering the verification code.
A six-digit code is sent via WhatsApp to the phone number provided during setup.
- The code is valid for 10 minutes. If it expires, the recipient must return to the original email and request a new code.
- The recipient has a limited number of attempts to enter the correct code. If they exceed this limit, the agreement is automatically canceled, and the sender is notified.

When the authentication is passed, the recipient can interact with the agreement.

If the recipient closes the agreement for any reason before completing their action, they must re-authenticate to continue.

Configuring the WhatsApp authentication method when composing a new agreement

When WhatsApp authentication is enabled, the sender can select WhatsApp from the Multi-factor authentication drop-down in the Recipient settings section of the Compose page:

The Recipient settings section highlighting the WhatsApp authentication method and phone number

To use WhatsApp as an authentication method, the recipient must have a phone number registered with WhatsApp. That phone number must be shared with the sender to configure the authentication properly.

Notes:

If the recipient delegates their role, they must also provide the new recipient’s WhatsApp-registered phone number.
The sender can update the phone number for in-progress agreements by editing the authentication method from the Manage page.

WhatsApp authentication requires that the recipient has an active WhatsApp account linked to a valid phone number.

If the recipient doesn’t have a WhatsApp account or if the phone number provided is invalid, the process will stop, and an error message will appear, blocking the sending process:

Consumption of premium authentication transactions

WhatsApp authentication requires that transactions be purchased and added to the account before they can be used. These transactions are consumed on a per-recipient basis.

Each recipient using WhatsApp authentication consumes one transaction.
Example: Three transactions are used if an agreement includes three recipients using WhatsApp authentication.
Adding multiple recipients to an agreement reduces the account’s total available transactions by one per recipient using WhatsApp.
Canceling a draft agreement returns all WhatsApp authentication transactions to the account’s available balance.
Canceling an in-progress agreement does not return the used transactions.
Changing the authentication method to WhatsApp (from any other method) consumes one transaction.
Switching back and forth between WhatsApp and other methods for the same recipient consumes only one transaction total.
Changing from WhatsApp to another method does not return the transaction.
Each recipient uses only one transaction, regardless of how often they attempt the authentication process.

Track available volume

To monitor the volume of WhatsApp authentications available to the account:

Navigate to Send Settings > Signer Identification Options
Select the Track Usage link:

The Send Settings page highlighting the Track Usage link with the information pop-out exposed

Note:

WhatsApp authentication and Phone/SMS authentication and link delivery share the same pool of transactions. Usage of the transactions is broken down in the pop-out ballon to show the volume consumed by SMS delivery and Phone authentication transactions.

Audit Report

The Audit Report clearly identifies that WhatsApp sent a one-time passcode to a phone number for identity verification.

Only the last four digits of the phone number are exposed.

The audit report highlighting the What'sApp authentication events.

If the agreement is canceled due to the recipient being unable to authenticate, the reason is explicitly stated:

Best Practices and Considerations

If second-factor signature authentication isn't required for your internal signatures, consider the Acrobat Sign Authentication method instead of WhatApp authentication to reduce the friction of signing and save on the consumption of the premium authentication transactions.
The phone number tied to the authentication attempt can only be changed for in-process agreements by editing the authentication type on the sender's manage page.

Configuration

WhatsApp authentication includes two sets of controls that can be configured at both the account and group levels:

Send Settings – Manage sender access to WhatsApp authentication and configure related options.
Security Settings – Set limits on the number of attempts a recipient has to enter the correct verification code.

**Enable WhatsApp authentication in Send Settings.**

To allow senders to use WhatsApp authentication, enable the option in Send Settings under Signer Identification Options.

The following settings are available:

WhatsApp authentication – When this box is checked, WhatsApp becomes an available authentication option during agreement setup.
Default country code – Set a default country code for recipients in the group. This helps ensure proper phone number formatting when agreements are sent.
Personalize your support contact – Replace the default sender’s email with a custom contact value, such as your support team’s email address. If left blank, the sending user’s email will be used as the contact by default.