Extending Docusign with Stripe to automate complex billing workflows

Paige RossiJun 2, 2025

Source: Stripe
Published: Jun 2, 2025
Added to Yomu: Aug 28, 2026

Summary

Docusign’s Stripe extension app addresses agreement workflows that continue beyond eSignature, where customer and billing data previously required manual transfer or complex integrations between platforms. The post shows how to install the app, start from the “Send new customer data to Stripe for invoicing” Maestro workflow template, and map web-form data to Stripe Customer, Invoice, InvoiceItem, and Email Invoice steps. It also explains how developers can switch the workflow to an API trigger, retrieve trigger requirements, and launch an instance with two authenticated API calls: one GET and one POST. The resulting flow collects customer information, creates a Stripe customer and draft invoice, adds an invoice item, and sends the invoice, while the returned instance URL can be opened or embedded for participants.

Context

After signing, agreement data has often been stored as a static PDF, requiring manual transfer between systems. Agreement processes can also involve multiple platforms, such as billing, cloud storage, or systems of record, and previously required complex API integrations to connect Docusign with external services like Stripe.

Approach / What changed

Use Docusign extension apps within Maestro workflows to package external authentication and API calls. The Stripe extension app is installed from the Docusign App Center and configured through a workflow template or the workflow designer. Developers can trigger the workflow through the Maestro API by retrieving its trigger requirements and then sending a POST request with the required inputs.

Takeaways

The Stripe extension app can create or update Stripe customer records and generate invoices from Docusign agreement data without custom integration code.
The example workflow maps web-form data to Stripe Customer, Invoice, InvoiceItem, and Email Invoice steps, using record IDs from earlier steps for subsequent operations.
A Maestro workflow can be triggered with two authenticated API calls: GET trigger requirements, followed by POST to the returned trigger URL; the response includes an instance ID and URL.

Architecture Developer Experience REST APIs

Read original post

Extending Docusign with Stripe to automate complex billing workflows

Paige RossiJun 2, 2025

Source: Stripe
Published: Jun 2, 2025
Added to Yomu: Aug 28, 2026

Summary

Context

Approach / What changed

Takeaways

The Stripe extension app can create or update Stripe customer records and generate invoices from Docusign agreement data without custom integration code.
The example workflow maps web-form data to Stripe Customer, Invoice, InvoiceItem, and Email Invoice steps, using record IDs from earlier steps for subsequent operations.
A Maestro workflow can be triggered with two authenticated API calls: GET trigger requirements, followed by POST to the returned trigger URL; the response includes an instance ID and URL.

Architecture Developer Experience REST APIs

Read original post

Related reading

Stripe · May 7, 2025
Introducing Stripe Workflows: Tailoring Payments to Your Business Needs
Stripe introduces Stripe Workflows, a Dashboard-based system for orchestrating Stripe products and APIs through responsive, end-to-end automation. It addresses the complexity of coordinating multiple Stripe products by replacing custom event-handling and dependency-management code with visual workflows that support real-time triggers, branching logic, dynamic fields, and more than 600 event triggers. Workflows includes execution monitoring with event-payload and step-level tracing, 30-day default log retention, exponential-backoff retries, built-in idempotency, and recursion protection capped at a depth of five. The post describes applications including reducing chargeback risk, routing high-value transactions for compliance review, and creating custom-priced subscriptions from finalized quotes without additional infrastructure.
Ben Smith
Stripe · Jul 22, 2025
Workflows: Automatically customize an object with metadata
Stripe Workflows can customize Stripe objects with metadata, adding contextual key-value information without changing the core data model or storing it separately. The example targets customers associated with successful Payment Intents that include a tip, so a customer can be labeled for business use, such as reconciliation, reporting, or internal integrations. To build it, the workflow retrieves the customer from the Payment Intent, emails a team member, checks whether the successful Payment Intent contains a non-empty tip amount, and updates that customer with the metadata key Tier and value VIP. Workflows runs a trigger and sequential actions or conditions in a visual Stripe Dashboard builder, while metadata can carry information to later workflow steps and support automation, analytics, and debugging.
Ashley Ansari
Stripe · Jul 10, 2025
Workflows: Creating early fraud alerts for streamlined refunds
Stripe Workflows can automate responses to early fraud warnings so potentially fraudulent charges receive refunds when disputing them would be more costly. The workflow starts when an early fraud warning is created in Radar, retrieves the related charge using its Charge ID, and checks whether the amount is less than 15 USD. If the condition is met, it creates a refund; if it is not met, an optional branch can email a team member for manual review. Workflows uses a visual builder in the Stripe dashboard, where triggers, actions, and conditions run sequentially across multiple Stripe products, while Stripe Radar provides real-time fraud protection and Radar for Fraud Teams adds customization and deeper insights.
Ashley Ansari
Stripe · Sep 11, 2025
Workflows: Automate compliance safeguards by flagging transactions
Stripe Workflows can automate additional compliance safeguards by flagging transactions that need review before order processing. The described pattern starts when a Payment intent succeeded event occurs, retrieves the customer, and checks whether the customer’s custom_status metadata is not “Approved” while the payment amount exceeds $5,000. When these conditions are met, the workflow emails one or more designated team members with instructions for assessing the order. The examples motivating review include unusually high order values, unfamiliar sales regions, and behavioral patterns commonly associated with fraud, such as a new customer order above a monetary threshold. Workflows uses a visual building interface in the Stripe dashboard to sequence actions across multiple Stripe products, helping enforce business rules, reduce manual effort, and support risk management.
Ashley Ansari