Pair Stripe payments with Zignature e-signatures — get agreements signed before charging, or trigger signing from Stripe events.
Free plan available · No credit card required · ESIGN Act compliant
Built-in features that save time and close deals faster.
Protect your business — require customers to sign a service agreement, subscription terms, or payment authorisation before a Stripe charge runs. Zignature and Stripe work together in a single checkout flow.
Gate Stripe charges behind completed e-signatures for service agreements.
When a Stripe payment succeeds, subscription activates, or customer is created, Zignature automatically sends the relevant document — service agreement, refund policy acceptance, or onboarding pack.
Stripe webhooks trigger Zignature document dispatch on payment and subscription events.
For regulated industries — lending, insurance, financial services — Zignature's signed payment authorisation forms provide irrefutable evidence of customer consent to charges, backed by timestamped audit trails.
Signed payment authorisations with court-admissible audit trails for regulated industries.
From simple agreements to complex multi-party workflows.
No training required. Send your first document today.
Link via Zapier or direct webhook in your Stripe Dashboard.
Choose Stripe events (payment.succeeded, customer.created, etc.) that fire signing requests.
Signing link sent by email — customer completes on any device.
Or confirmation sent post-signature — fully automated.
Free trial — no credit card required.
Everything you need to know.
Yes. The recommended pattern is to use Zignature's API to send the document, wait for the signed webhook confirmation, then initiate the Stripe charge via your server. This creates a clear gate: no signature, no charge.
Configure a Stripe webhook to call your server or Zapier when a payment event fires. Your server (or Zapier) then calls the Zignature API to send the relevant document template to the customer.
Yes. A signed payment authorisation with Zignature's audit trail (showing the customer reviewed and agreed to billing terms) is strong evidence in chargeback disputes. The timestamped audit log shows exactly when the customer consented.
Yes. ACH debit authorisation forms — required by NACHA rules before initiating direct debits — can be collected via Zignature. The signed form with audit trail satisfies NACHA authorisation documentation requirements.
Yes. Zapier has native Stripe and Zignature triggers and actions. You can build Zaps that send documents on new Stripe customers, payment successes, subscription activations, and more — no code required.
Yes. When a customer upgrades their Stripe subscription to a higher tier, trigger a Zignature signing request for the updated service agreement or pricing acknowledgement — creating documented evidence of the upgraded terms agreement.