Introduction
Gravity Forms Stripe Add-On version v2.6 expanded the options for processing payments with Stripe. This article gives an overview of those payment collection methods, and provides you with links to other documents where you can review further information.
Settings
The “Payment Collection Method” option is set on the Stripe Add-Ons Settings page. The article linked here can give you more information on the settings presented there.
1. Stripe Field (Stripe Elements)
Description
The Stripe Field is hosted on Stripe’s servers and displayed on your form using an iframe. Your Gravity Form collects all data except the credit card (and optionally, the Cardholder Name) fields, which are collected securely by Stripe and transmitted over an HTTPS connection to their processing servers. Those Stripe-collected details are not stored with your entry data.
Benefits
- Reduces your responsibility for handling and securing sensitive payment information as that process is handled by Stripe.
- Is SCA ready as of version 3.3.1.
- Can help you meet your PCI compliance requirements, such as Stripe’s simpler PCI compliance process and Pre-Filled SAQ A.
- You can manage which payment methods are available for presentation from within your Stripe Dashboard Settings area. Refer to this article for more information on how Stripe presents payment methods (requires Stripe Add-On 5.0 or above)
Pre-Requisites
- The Stripe Add-On must be installed and active.
- Have selected Stripe Field as your payment collection method within the Stripe Add-On Settings.
- Your checkout page must be secure
https://address.
The Stripe field is available under the Pricing Fields section of the Gravity Forms Editor. Refer to this guide for more on that field, and check out this guide to building a Stripe compatible form.
Note: Stripe.com will render the card details input fields only if your form has an active Stripe feed configured. Also, if your Stripe feed has conditional logic, you will want to configure the Stripe field with the same logic.
Card Element vs. Payment Element
The Stripe Field renders using one of two Stripe Elements components. By default, it uses the Stripe Card Element, which collects only card details. Enabling Use Stripe’s Payment Element in the Stripe Add-On Settings switches the field to the Stripe Payment Element, which can present multiple payment methods based on your Stripe Dashboard configuration. The two are mutually exclusive.
The following table compares the two elements as of Stripe 7.0.
| Feature | Card Element | Payment Element |
|---|---|---|
| Payment methods presented | Card details only | Multiple, based on your Stripe Dashboard configuration |
| Entry created on failed payment | Yes (Stripe 6.0) | Yes (Stripe 7.0) |
| Post payment actions | Yes (Stripe 6.0) | Yes (Stripe 7.0) |
| Payment Processing message on the submit button | Yes (Stripe 6.0) | Yes (Stripe 7.0) |
| Timeout Confirmation | Yes | No |
| Customer Information on product feeds | Yes (Stripe 7.0) | Yes |
Where an entry is created for a failed payment, the result is recorded in the Payment Status field. The Customer Information section allows customers to be created on Stripe; see the Stripe Feed Settings Reference for details. The Card Element also uses AJAX for more reliable form submissions.
2. Stripe Payment Form (Stripe Checkout):
Description
Form submission will trigger the opening of a Stripe hosted form to collect all the payment details directly within Stripe’s domain, including required data such as email, billing address, or any other verification fields as demanded by your payment processing flow.
Note: This collection method will not make a Card field available in the Gravity Forms Form Editor Pricing fields, as a credit card field is not required for this collection method.
When using the Stripe Payment Form, Coupons can’t be applied to the first invoice of subscriptions. The only workaround for this limitation is switching to the Stripe Field payment collection method.
Benefits
- Reduces your responsibility for handling and securing sensitive payment and customer information, as none of the payment form collected data is stored by your Gravity Forms databases.
- Is SCA ready.
- Can help you meet your PCI compliance requirements, such as Stripe’s easier PCI compliance process, Pre-filled SAQ A.
- You can manage what payment methods are available to be presented from within your Stripe Dashboard Settings area. Refer to this article for more information on how Stripe presents payment methods (requires Stripe Add-On 5.0 or above)
Pre-Requisites
- Have the Stripe Add-On installed and active.
- Have Stripe Payment form (Stripe Checkout) selected as your payment method in Stripe settings.
- When using this method, you configure the payment collection form and fields in your Stripe account, not in the Gravity Forms editor.
- If any of your form notifications is intended to be sent when the payment is done, you would need to change the notification Event setting from the default “Form is submitted” to “Payment Completed” if you use a Products and Services feed, or “Subscription Created” for Subscription feeds.
3. Gravity Forms Credit Card Field (deprecated)
❗This collection method has been deprecated for Stripe. Refer to this document for more information.
Description
This field displays inputs for the credit card details. Gravity Forms turns the field values into a token in the browser just before submission. It then passes the token along to the payment gateway for processing. The last 4 digits of the card number are later stored in the entry details.
Warning: With this payment method, you (the website admin/owner) assume responsibility for the safe storage, handling, and transmission of sensitive payment data. The Gravity Forms Credit Card field collection method is not SCA capable and will complicate attempts to obtain PCI compliance or similar secure storage standards.