ZapSign API
English
English
  • General Information
  • Getting Started
  • ZapSign Environments
  • Ready-to-use requests!
  • Authentication
    • Static token
    • JWT Authentication
      • Get access token
      • Refresh your access token
  • Types of Tokens
  • API versioning
  • Rate Limit Policies
  • Incident alerts
  • How Payment Works
  • Status Code
  • Account
    • Plan Information
    • List account users
    • Create account users
    • Delete account user
  • Documents
    • Create document via Upload
    • OneClick (ClickWrap)
      • Create document (OneClick)
    • Create document via Template
    • Add attachment (extra document)
    • Add attachment (extra document) via Template
    • Detail document
    • List documents
    • Delete document
    • Document Audit Trail
    • Optional: Place signatures
    • Reject Documents
  • Signers
    • Detail signer
    • Update signer
    • Add signer
    • Delete signer
    • Batch sign via API
    • Reject Documents by User
  • Templates
    • Create template (DOCX)
      • Configure Template Form
    • List templates
    • Get template
    • Update template
    • Delete template
  • Partnerships
    • Update Payment Status
    • Create Account
  • TIMESTAMP
    • Add timestamp
  • Background Check
  • Introduction
  • Understanding the Result
  • Creating a Background Check
    • Person Check
    • Company check
  • Retrieve a Check
  • Check details
  • Webhooks
    • How webhooks works
    • Testing webhooks on ZapSign
    • Create Webhook
    • Webhooks logs
    • Events
      • Document
        • Doc created
        • Doc deleted
        • Created signer
      • Signer
        • Signature request send
        • Document viewed
        • Reading confirmation
        • Doc signed
        • Doc refused
        • Email bounce
        • Failed Validation
      • Background check
        • Background check completed
    • Reprocessing Documents and Webhooks
    • Delete Webhook
  • Widget
    • How widget works
Powered by GitBook
On this page

Was this helpful?

How Payment Works

PreviousIncident alertsNextStatus Code

Last updated 5 months ago

Was this helpful?

Attention: To use the ZapSign integration in production you must have an active API plan. To learn more about the plans and for more documents .

To use the production environment, you need to subscribe to an API plan via credit card which is automatically renewed. You have the option to choose between monthly or annual payments. If you exceed the number of documents included in your plan, the excess will be charged to your registered credit card at the end of the month.

You are responsible for tracking the volume of documents used. We will only provide a usage report at the end of the month if you exceed the document volume of your plan.

Unsigned and deleted documents do not "recover" credits. Once created, the document will be counted towards your API Plan usage.

Remember that you will always need an API plan to integrate tools with ZapSign.

click here
contact our sales team
A user navigating within the platform goes to Settings > Plans and Pricing and subscribes to an API plan.