Creating a Transaction
- 08 Oct 2024
- 3 Minutes to read
- DarkLight
- PDF
Creating a Transaction
- Updated on 08 Oct 2024
- 3 Minutes to read
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Android
Creating a Transaction
To create a transaction:
Tap the Create a new transaction icon on the Dashboard. That icon also appears in the top-right corner of the Transaction List.
On the New Transaction page, enter a name for the new transaction.
Add at least one document to the transaction by tapping the Document icon (the supported file types are PDF, PNG and JPG). You can add a document from any location that appears on the following dialog box:
Add at least one recipient to the transaction by tapping the Recipient icon. Specify information about the recipient using the following dialog box (e.g., the Authentication option permits you to select Email, SMS or Q&A as the authentication method for the recipient; the Allow change recipient option permits the recipient to delegate signing to another person):
If you want to add any of the following optional settings to the transaction, do so by clicking the Settings icon:
Add a description of the transaction
Enable In-Person signing
Review the transaction before completion
Specify an expiry date
Tap Next to prepare the added documents.
File Size Constraints
The maximum size of a single document is 16 MB. Smaller documents yield better performance — we recommend under 5 MB per document.
If your organization uses Salesforce or Microsoft SharePoint connectors, the file size maximum is 5 MB per document.
If your organization uses Salesforce connectors, the maximum number of documents that can be added to a transaction is ten (10).
If you enable email delivery while configuring a recipient, attachments larger than 5 MB are not supported.
File Name Constraints
Document file names should not contain any of the following comma-separated characters: *, /, \, :, <, >, |, ?, ".
A document's name cannot contain the string esigned.
General File Constraints
We recommend that you do not use PDF documents that make use of XML Forms Architecture. For more information, see XFA Support.
Do not upload password-protected or corrupted documents. These will generate an error.
OneSpan strongly recommends that you scan a PDF for syntax errors (e.g., by using Adobe's Preflight tool), and resolve any errors before you add the document to a transaction.
PDFs with the NeedAppearances flag set to true are not currently supported.
iOS
Creating a Transaction
To create a transaction:
Tap the Create a new transaction icon on the Dashboard. That icon also appears in the top-right corner of the Transaction List.
On the New Transaction page, enter a name for the new transaction.
Add at least one document to the transaction by tapping the Document icon. You can add a document from any location that appears on the following dialog box :
OneSpan Sign supports the following document types:
Adobe's Portable Document Format (*.pdf) — PDFs on which OneSpan Sign can act generally have at least these permissions enabled: (1) Changing the Document; (2) Signing; (3) Filling of form fields.
Microsoft Word (*.doc or *.docx)
Open Office (*.odt)
Text (*.txt)
Rich Text Format (*.rtf)
In addition, the OneSpan Sign Print Driver supports any document that can be printed from a Windows-based application (e.g., Microsoft Word, Microsoft Excel, Microsoft PowerPoint).
Add at least one recipient to the transaction by tapping the Recipient icon. Specify information about the recipient using the following dialog box (e.g., the Authentication option permits you to select Email, SMS or Q&A as the authentication method for the recipient; the Allow change recipient option permits the recipient to delegate signing to another person):
If you want to add any of the following optional settings to the transaction, do so by clicking the Settings icon:
Add a description of the transaction
Enable In-Person signing
Review the transaction before completion
Specify an expiry date
Tap Next to prepare for signing the documents you added.
File Size Constraints
The maximum size of a single document is 16 MB. Smaller documents yield better performance — we recommend under 5 MB per document.
If your organization uses Salesforce or Microsoft SharePoint connectors, the file size maximum is 5 MB per document.
If your organization uses Salesforce connectors, the maximum number of documents that can be added to a transaction is ten (10).
If you enable email delivery while configuring a recipient, attachments larger than 5 MB are not supported.
File Name Constraints
Document file names should not contain any of the following comma-separated characters: *, /, \, :, <, >, |, ?, ".
A document's name cannot contain the string esigned.
General File Constraints
We recommend that you do not use PDF documents that make use of XML Forms Architecture. For more information, see XFA Support.
Do not upload password-protected or corrupted documents. These will generate an error.
OneSpan strongly recommends that you scan a PDF for syntax errors (e.g., by using Adobe's Preflight tool), and resolve any errors before you add the document to a transaction.
PDFs with the NeedAppearances flag set to true are not currently supported.
Was this article helpful?