Payment Collection Methods

Once you've set your Stripe integration, you may collect payments from your users.
Once you've set your Stripe integration, you may collect payments from your users.

Stripe Checkout Payment Collection

If you choose to collect payments through an embedded Stripe checkout session, all Stripe payment methods will be available to use and configurable in Stripe.
Once you set your Stripe integration settings to Stripe Checkout, you can go back to your form and create a button with the Collect Payment action. When this button is clicked, it'll automatically redirect your user to a Stripe Checkout session that has the products & quantities prepopulated.

Feathery-Native Payment Collection

If you configure your Stripe settings to collect payments natively in your Feathery form, the Payment Method field will become available to use.
This payment method field may be dragged anywhere onto your form and is the only way to enter payment/card information into your form to be passed securely to Stripe. The payment method field collects the card number, CVC, expiration month/year and postal code. It supports standard styling in Feathery.
A payment method field in a Feathery form
Once your end user fills the field and submits the step that holds it, the payment method will be automatically saved into the customer record in Stripe. Also, if the payment method is co-located on a step that also initiates a payment in Stripe, Feathery will first save the payment method into Stripe and then use it for the payment.
Typically, the payment method control is only used when building a custom checkout flow in a Feathery form. It is not typically used if you want to use Stripe Checkout because the Stripe checkout page collects the payment information.
Note that it is not always necessary to collect new payment information when designing a custom checkout flow in Feathery. Feathery will make use of existing payment methods previously set up in Stripe for the customer. However, when unsure if a payment method has been previously set up, it is always safer to require it to be input again in your custom flow design.