Questions before you send?

PocketESign is a browser-based electronic-signature service for individuals, freelancers and businesses that want to upload an existing PDF, place signing fields, send it to recipients and keep the completed record without paying a monthly subscription.

PocketESign is designed for individuals, freelancers, independent professionals and businesses with low, irregular or seasonal signing volume, especially people who already create their PDFs elsewhere and mainly need a simple signing workflow.

No. PocketESign uses one-time credit packs instead of a recurring monthly e-signature subscription.

Newly verified accounts receive 3 free credits so they can use the real document workflow before buying a paid pack.

Yes. PocketESign is designed around the PDF you already use. You can visually place signature, initials, text, date and checkbox fields before sending.

No. Recipients open the secure signing link they receive and can complete the document without creating a PocketESign account.

Yes. The signer-facing workflow is browser based and can be used from common mobile and desktop devices.

No. PocketESign and the signer workflow are browser based. You do not need a desktop application simply to prepare or sign a standard request.

Yes. PocketESign supports multiple recipients on the same signing request.

Yes. When signing order is enabled, later recipients wait until the earlier eligible signer has completed their step.

The visual editor supports Signature, Initials, Text, Date and Checkbox fields.

Yes. The PocketESign PDF editor lets you place, move and resize signing fields directly on the rendered document.

You choose an expiration period when preparing the request. PocketESign currently offers common options ranging from 1 to 30 days.

Yes. For eligible pending requests, PocketESign can resend the signing invitation to a recipient who is currently able to sign.

Eligible active requests can be cancelled. Cancelling prevents the request from completing and releases a reserved PocketESign credit when applicable.

Sent means the signing request has been issued, Viewed means the signing workflow recorded that the document was opened, and Completed means all required signing steps have finished.

The request remains active until all required signing steps are complete. If signing order is enabled, the next eligible signer can continue after the prior signer finishes.

Yes. Save a prepared document as a template, then reuse signer roles and field placement for future recipients without rebuilding the layout each time.

Template details can preserve the prepared PDF setup, signer roles, field positions, signing order and expiration settings associated with that reusable workflow.

No. Templates are best for genuinely repeatable documents. If the source terms, page layout or scope materially change, review or create a fresh document instead of reusing a stale template.

Yes. Template Details shows information such as pages, signer roles, field counts and types, signing order, expiration and usage history before you send it again.

No. PocketESign does not retain your uploaded source PDF in the WordPress Media Library. The document is processed by the specialized signing infrastructure used to deliver the signing workflow.

Unsent drafts can use the supported deletion workflow, including provider-side draft deletion where available. Sent or completed records may have retention and audit implications and are handled differently.

Completed signing requests provide access to the completed-document workflow from your PocketESign account.

An audit trail is a chronological record of signing activity such as document events, recipient actions and timestamps. It complements the completed PDF by helping document how the signing process occurred.

A credit represents one signing request/document that can be completed through the PocketESign workflow. It is not charged separately for each recipient on the same request.

No. A PocketESign credit applies to the signing request/document, not to each signer, even when the request contains multiple recipients.

A credit is reserved while a signing request is active and permanently consumed only when the document reaches Completed.

The reservation is released back to Available instead of becoming a Used credit.

PocketESign credit packs are designed not to expire, subject to the current Billing & Credits Policy.

PocketESign currently lists 10 credits for $4.90, 30 for $11.70 and 100 for $29, in addition to 3 free credits for newly verified accounts. Check the Pricing page for the current offer.

PocketESign does not use a recurring per-seat subscription for its standard credit-pack model.

PocketESign paid credit packs are available internationally in countries supported by our payment provider. Checkout availability and payment methods can vary by country.

Paid credit packs use Stripe-hosted Checkout with Managed Payments. Stripe acts as merchant of record for supported transactions, while PocketESign receives the transaction metadata needed to credit the account and does not store full payment-card numbers on its own servers.

No. Provider credentials are kept server-side and are not exposed to the browser.

PocketESign uses signed provider-to-server webhook events and verifies the webhook signature before applying lifecycle updates such as Viewed or Completed.

See the Data Retention & Deletion page for the current PocketESign workflow and how to request review of account or provider-side data.

Federal law generally provides that a signature, contract or record may not be denied legal effect solely because it is electronic, but specific transactions can have additional requirements or exceptions. PocketESign does not provide legal advice.

No. Some documents, regulated transactions or high-risk uses may require additional formalities or may be unsuitable for ordinary electronic signing. Review the Acceptable Use Policy and obtain legal advice for sensitive use cases.

Yes. Signed-in users can download an account-data export from Account & Billing. Provider-hosted PDFs, signatures and certificates are not embedded in that JSON export.

Use the PocketESign password-recovery flow from the Account page. Reset messages are sent through the configured authenticated account-email channel.

Use the Support page or email support@pocketesign.com.