Select an organization. The organization ID will be used as the tenant_id in the webhook registration.

Select a document to monitor for merged document events.

DocupletionForms is a conditional logic contact form program to build and manage your online forms.

DocupletionForms

Instantly build dynamic interfaces that connect to Zaps and a data source (like Tables). Interfaces gives you a drag-and-drop way to build visual workflows for any business process, without writing code.

Zapier Interfaces

If **True**, charges related to a payment intent will be ignored. This could prevent potential duplications when also using the New Payment trigger.

Select an event from the list of supported events.

We strongly recommend using this field. Select up to 20 event types to trigger on. If you leave this empty, we will trigger on all event types. If you have a very active Stripe account with more than 100 events per minute, this Trigger will likely miss some events. To fix this, use this field to select only the events you are interested in. You can learn more about each event type [here](https://docs.stripe.com/api/events/types).

Defaults to `open`. If you select `draft`, your Zap might trigger before you have finished filling in all of the other fields of your invoice in Stripe. This is because a draft invoice is available via Stripe's API (which Zapier uses to trigger your Zap) the moment you add a customer to an invoice.

Only return invoices for the customer specified by this customer ID.

You can select one or more products. If you use this field, the Zap will only trigger for new payment links that include all of the products you selected.

Enter the Stripe Account ID (e.g. `acct_1234567890abcdef`).

Enter the Stripe ID of the charge to find. (e.g. `ch_51kxCxb1NFWajM`)

Enter the Stripe ID (e.g. `cus_51kxW2Z0qQHpGc`) or the email address of the customer to find.

Enter the Stripe ID of the invoice to find. (e.g. `in_51kxCxb1NFWajM`)

Enter the Stripe ID of the payment intent to find. (e.g. `pi_51kxCxb1NFWajM`)

If this field is left empty, Zapier will search for subscriptions that have not been canceled.

The subscription will be canceled immediately. The customer will not be charged again for the subscription. Note, however, that any pending invoice items that you've created will still be charged for at the end of the period, unless manually deleted. [Learn more](https://stripe.com/docs/api/subscriptions/cancel).

Be careful when using this Action because it can charge money to the customers in your Stripe account using the [Confirm PaymentIntent API](https://docs.stripe.com/api/payment_intents/confirm).

We recommend defining the customer and the payment method when the PaymentIntent is created. If you need to define the payment method using this field, make sure the payment method belongs to the customer that was used when the PaymentIntent was created. To get the default payment method for the customer associated with a PaymentIntent, we suggest the following approach: Add a "Find Customer" step earlier in this Zap, followed by a "Filter by Zapier" step. Find the Stripe customer by email using "Find Customer", then use "Filter by Zapier" so that your Zap only continues if the `invoice_settings.default_payment_method` property exists for the customer. Map that `invoice_settings.default_payment_method` property to this field. 

Set to `true` to fail the payment attempt if the PaymentIntent transitions into `requires_action`.

Two-letter country code ([ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2))

The delivery service that shipped a physical product, such as Fedex, UPS, USPS, etc.

The tracking number for a physical product, obtained from the delivery service. If multiple tracking numbers were generated for this purchase, please separate them with commas.

The ID of the Price or Plan to add to this Checkout Session.

The quantity of the price/product being purchased.

The URL to redirect customers when payment or setup is complete.

The URL to redirect customers when they click the back button.

ID of an existing Customer. If provided, the customer information will be prefilled.

If provided, this email will be prefilled in the Checkout form.

A list of payment method types that customers can use. If not set, Stripe will dynamically show relevant payment methods.

Three-letter ISO currency code (e.g., usd). Only required for payment mode if not using existing prices.

Configure whether to collect the customer's billing address.

List of allowed countries for shipping address collection (e.g., US, CA, GB). If provided, shipping address collection will be enabled.

Enables a promotion code field on the Checkout form.

Enable automatic tax calculation for the session.

A unique string to reference the Checkout Session. This can be a customer ID, cart ID, or similar.

The timestamp at which the Checkout Session will expire.

Enter a [two-letter country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2).

Enter a [two-letter language code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes).

The prefix for the customer used to generate unique invoice numbers. Must be 3-12 uppercase letters or numbers.

An integer amount in cents that represents the customer's current balance. A negative amount represents a credit that decreases the amount due on an invoice. (e.g. `-2000` decreases invoice amount by $20.00) A positive amount increases the amount due on an invoice. (e.g. `1000` increases invoice amount by $10.00)

If you are using fields in the "Invoice Items" section, you must specify a Customer ID.

A positive integer in minor units (e.g. cents) or `0` for a free price. For example, if your currency is USD, enter `100` to charge $1.00. If you specify a "Unit Price", you should leave the "Amount" field empty.

If you specify the "Amount", leave the "Unit Price" and "Quantity" fields empty. For this field, enter a positive integer in minor units (e.g. cents) or `0` for a free price. For example, if your currency is USD, enter `100` to charge $1.00.

Only required if a [default tax behavior](https://stripe.com/docs/tax/products-prices-tax-categories-tax-behavior#setting-a-default-tax-behavior-(recommended)) was not provided in the Stripe Tax settings.

When set, the "Default Tax Rates" on the invoice do not apply to the invoice item.

Controls whether discounts apply to this invoice item. Defaults to false for prorations or negative invoice items, and true for all other invoice items.

The "Is Discountable?" field must be set to `true` for these coupons to be applied. The coupons will be applied at the line item level.

Must be a [supported three-letter ISO currency code](https://stripe.com/docs/currencies).

The ID of a subscription to add this invoice item to. When left blank, the invoice item will be be added to the next upcoming scheduled invoice. When set, scheduled invoices for subscriptions other than the specified subscription will ignore the invoice item. Use this when you want to express that an invoice item has been accrued within the context of a particular subscription.

A [tax code](https://stripe.com/docs/tax/tax-codes) ID.

The coupons to redeem into discounts for the invoice. If not specified, inherits the discount from the invoice's customer. These coupons are applied at the invoice level, not the line item level.

The tax rates that will apply to any remaining line items that do not already have tax rates set at the line item level.

The date on which payment for this invoice is due.

The number of days from when the invoice is created until it is due.

Controls whether Stripe performs [automatic collection](https://stripe.com/docs/invoicing/integration/automatic-advancement-collection) of the invoice. If `false`, the invoice's state doesn't automatically advance without an explicit action.

This must belong to the customer associated with the invoice. If not set, defaults to the subscription's default payment method, if any, or to the default payment method in the customer's invoice settings.

A list of up to 4 custom fields to be displayed on the invoice.

The account Tax ID(s) associated with the invoice. A Tax ID starts with `txi_`. To find a Tax ID, go to [https://dashboard.stripe.com/settings/billing/invoice?tab=tax](https://dashboard.stripe.com/settings/billing/invoice?tab=tax) and select "Copy object ID" next to the Tax ID you want, then paste it here.

Use the "Shipping Details" fields to ship to an address that is different to the one on file.

This field is required if you fill in any of the other "Shipping Details" fields.

Two-letter [country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2).

The ID of the subscription to invoice. If set, the created invoice will only include pending invoice items for that subscription. The subscription's billing cycle and regular subscription events won't be affected.

Whether Stripe automatically computes tax on this invoice. Note that incompatible invoice items (invoice items with manually specified tax rates, negative amounts, or `tax_behavior=unspecified`) cannot be added to automatic tax invoices

The date when this invoice is in effect. Same as `finalized_at` unless overwritten. When defined, this value replaces the system-generated "Date of issue" printed on the invoice PDF and receipt.

The list of payment method types (e.g. card) to provide to the invoice's PaymentIntent. If not set, Stripe attempts to automatically determine the types to use by looking at the invoice's default payment method, the subscription's default payment method, the customer's default payment method, and your [invoice template settings](https://dashboard.stripe.com/settings/billing/invoice).

How line-item prices and amounts will be displayed with respect to tax on invoice PDFs.

Extra information about a charge for the customer's credit card statement. It must contain at least one letter. If not specified and this invoice is part of a subscription, the default `statement_descriptor` will be set to the first subscription item's product's `statement_descriptor`.

Defaults to `include`. How to handle pending invoice items on invoice creation. `include` will include any pending invoice items, and will create an empty draft invoice if no pending invoice items exist. `exclude` will always create an empty invoice draft regardless if there are pending invoice items or not.

If you want this action to create a draft invoice, leave all of the fields below empty.

Stripe automatically finalizes drafts before sending invoices and before attempting payment on invoices. However, if you'd like to finalize a draft invoice manually, set this field to `true`.

Stripe will automatically send invoices to customers according to your [subscriptions settings](https://dashboard.stripe.com/account/billing/automatic). However, if you'd like to manually send an invoice to your customer out of the normal schedule, you can do so. When sending invoices that have already been paid, there will be no reference to the payment in the email.

Stripe automatically creates and then attempts to collect payment on invoices for customers on subscriptions according to your [subscriptions settings](https://dashboard.stripe.com/account/billing/automatic). However, if you'd like to attempt payment on an invoice out of the normal collection schedule or for some other reason, you can do so. If this field is `true`, you can use the "Pay Invoice" fields below to further customize the payment attempt.

In cases where the source used to pay the invoice has insufficient funds, passing `forgive=true` controls whether a charge should be attempted for the full amount available on the source, up to the amount to fully pay the invoice. This effectively forgives the difference between the amount available on the source and the amount due. Passing `forgive=false` will fail the charge if the source hasn't been pre-funded with the right amount. An example for this case is with ACH Credit Transfers and wires: if the amount wired is less than the amount due by a small amount, you might want to forgive the difference. Defaults to `false`.

Indicates if a customer is on or off-session while an invoice payment is attempted. Defaults to `true` (off-session).

Boolean representing whether an invoice is paid outside of Stripe. This will result in no charge being made. Defaults to `false`.

Be careful when using this Action because it can charge money to the customers in your Stripe account using the [Create PaymentIntent API](https://docs.stripe.com/api/payment_intents/create).

How much to charge in the [smallest currency unit](https://docs.stripe.com/currencies#zero-decimal) (e.g. `100` to charge $1.00 or `100` to charge ¥100, a zero-decimal currency). The minimum amount is $0.50 US or [equivalent in charge currency](https://docs.stripe.com/currencies#minimum-and-maximum-charge-amounts). The amount value supports up to eight digits (e.g., a value of 99999999 for a USD charge of $999,999.99).

A three-letter lowercase [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html) For example, `usd`. Must be a [supported currency](https://stripe.com/docs/currencies).

We strongly recommend providing a value for this field even though it is not required.

We strongly recommend using this field. We suggest the following approach: Add a "Find Customer" step earlier in this Zap, followed by a "Filter by Zapier" step. Find the Stripe customer by email using "Find Customer", then use "Filter by Zapier" so that your Zap only continues if the `invoice_settings.default_payment_method` property exists for the customer. Map that `invoice_settings.default_payment_method` property to this field. If you leave this field empty, and set the "Confirm Payment Immediately?" field to `true`, the `default_source` of the customer provided in the "Customer ID" field will be used as the PaymentIntent's payment instrument. This Zap step will fail if this field is empty, the "Confirm Payment Immediately?" field is `true`, and the customer provided in the "Customer ID" field does not have a `default_source`. We do not recommend relying on the legacy `default_source` property. Instead, we recommend that you explicitly provide a Payment Method ID to this field.

WARNING: This field controls whether this Zap step charges money or not. This field defaults to `false` as a precaution. However, most users will probably want to set this field to `true`. If you select `true`, Stripe will attempt to [confirm this PaymentIntent](https://docs.stripe.com/api/payment_intents/confirm) immediately, which typically results in money being charged.

Set to `true` to fail the payment attempt if the PaymentIntent transitions into `requires_action`. This field can only be used if the "Confirm Payment Immediately?" field is `true`. If you have set the "Confirm Payment Immediately?" field to `true`, we recommend setting this field to `true` as well.

Set to `true` to indicate that the customer isn't in your checkout flow during this payment attempt and can't authenticate. This parameter can only be used when the "Confirm Payment Immediately?" field is `true`. If you have set the "Confirm Payment Immediately?" field to `true`, we recommend setting this field to `true` as well.

For card charges, use "Statement Descriptor Suffix". Otherwise, you can use this value as the complete description of a charge on your customers' statements. It must contain at least one letter and be 1-22 characters long.

Provides information about a card payment that customers see on their statements. Concatenated with the prefix (shortened descriptor) or statement descriptor that's set on the account to form the complete statement descriptor. The concatenated descriptor must contain 1-22 characters.

Defaults to `automatic`. Controls when the funds will be captured from the customer's account. For `automatic`, Stripe automatically captures funds when the customer authorizes the payment. For `automatic_async`, Stripe asynchronously captures funds when the customer authorizes the payment. For `manual`, place a hold on the funds when the customer authorizes the payment, but [don't capture the funds until later](https://docs.stripe.com/payments/capture-later). (Not all payment methods support this.)

You can add a [Price Description](https://cdn.zappy.app/5f20b10aed1174cb5506b06c39cc3409.png) to the Price of a Product in Stripe to make it easier to find in Zapier.

By default this value is 0. You can specify a value up to 98. If you do not want to let customers adjust quantity, leave this field empty, or pass an empty line item value.

By default this value is 99. You can specify a value up to 99. If you do not want to let customers adjust quantity, leave this field empty, or pass an empty line item value.

To use this option, you must first enable "Automate taxes" at [https://dashboard.stripe.com/setup](https://dashboard.stripe.com/setup)

The maximum number of checkout sessions that can be completed with the link.

If set to `true`, customers will be required to enter their business tax ID number. 

Enable creating an invoice on successful payment.

If set to `true`, customers will be required to check a terms of service checkbox before being able to pay. There must be a valid terms of service URL set in your Stripe [Dashboard settings](https://dashboard.stripe.com/settings/public).

A positive integer in minor units (e.g. cents) or `0` for a free price. For example, if your currency is USD, enter `100` to charge $1.00.

A subscription can be created with up to 20 items. Selecting the same item more than once will result in an error.

When charging automatically, Stripe will attempt to pay this subscription at the end of the cycle using the default source attached to the customer. When sending an invoice, Stripe will email your customer an invoice with payment instructions.

Select “Yes” to [stop this Zap step](https://help.zapier.com/hc/en-us/articles/20505304170637-Review-Zap-run-statuses#h_01HD20969HPZ01ENM30NQR79X5) if the app returns an error and enable automatic authentication refresh. Select “No” to run the Zap step regardless of errors. Learn more about [API Request action error handling](https://help.zapier.com/hc/en-us/articles/12899473501453#h_01JKRBY68EDXBB1V817DSTRZ0N).

Requests can only be made to domains associated by this application. Read more about [API Request Setup](https://help.zapier.com/hc/en-us/articles/12899607716493).

Any parameters added to a URL will be URL-encoded and appended to the request URL to pass additional data to the API request.

These headers and values will be applied to the request in addition to any headers created as part of authentication. Authentication headers are added automatically.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Stripe is a developer-friendly way to accept payments online and in mobile apps. Stripe's suite of APIs powers commerce for thousands of companies of all sizes, processing billions of dollars for businesses each year.

Stripe

Create subscriptions in Stripe from new forms submitted in DocupletionForms

DocupletionForms + Stripe

Create subscriptions in Stripe from new forms submitted in DocupletionForms

Supported triggers and actions

New Form Submitted

New Merged Document

About DocupletionForms

Related categories

Similar apps

Zapier Interfaces

About Stripe

Related categories

Related Zap Templates

Related Zap Templates