Author 诗语

Creating a Feed for the PayPal Pro Add-On

SummaryCreate a FeedFeed Settings Screen

DEPRECATION NOTICE: The PayPal Pro Add-On is no longer being updated by Gravity Forms, and is no longer available for download. It uses a legacy PayPal API no longer being actively developed by PayPal, and is not compatible with modern PayPal accounts. It has been replaced in our plug-in library by other PayPal add-ons.
Summary
Once you have a form configured and ready to interact with PayPal Pro, it』s time to bring it all together by configuring the form to integrate with PayPal Pro. Just like all of Gravity Forms Add-Ons, this integration is done by creating a feed.
Create a Feed
To create a feed to PayPal Pro using the PayPal Pro Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with PayPal Pro.
Once within your desired form, hover over Settings and click on PayPal Pro.
Click Add New to create a new feed. You will be presented with the PayPal Pro feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
Select the PayPal Pro Transaction Type. Choose from Products and Services, which is a single one time payment, or Subscriptions if you have enabled PayPal Pro』s Recurring Billing option in the PayPal Pro Add-On Settings.
Select the Gravity Form you would like to integrate with.
If you have chosen Subscription as your Transaction Type, you will be given options for the Recurring Amount, Billing Cycle, Recurring Time, Trial Period, and Setup Fee. These are used to setup the recurring payment profile. The Trial Period and Setup Fee should not be used together; you would use one or the other.
Map Fields: Map each of the PayPal Pro fields to the desired form field that will contain that information.
Conditional Logic: If unchecked, every successful form submission will be sent to PayPal Pro. If you wish to set specific conditions for sending form data to PayPal Pro, then check the 「Enable Condition」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Note: You can create multiple PayPal Pro feeds for your form; however, you must configure conditional logic on them. The PayPal Pro Add-On will only process one feed during submission; if conditional logic is not configured, it will use the first feed it finds.

Deleting Cached Entry Data

This snippet will allow the cached entry data for products to be deleted when viewing an entry. Note that the cached data should only be removed if absolutely necessary, as it will impact performance.
add_action( 'gform_entry_detail_content_before', function ( $form, $entry ) {
GFFormsModel::refresh_product_cache( $form, $entry );
}, 10, 2 );

Creating a PayPal Payments Pro Sandbox Account

IntroductionPrerequisitesCreating a PayPal Sandbox Test AccountGetting Your Sandbox CredentialsSetting Up the PayPal ManagerCheckout Page SettingsFraud Protection SettingsCredentialsTest Credit Card Number

Introduction
When setting up the PayPal Payments Pro Add-On, it is recommended that you test it using a sandbox developer account first. This helps reduce unexpected surprises when you start processing live transactions.
In this article, we are going to show you how to create a new PayPal Payments Pro sandbox account.
This is a Paypal process, and screen layout and behavior may be changed by Paypal without our knowledge. If you run into any issues, we recommend you contact Paypal Developer Support for resolution.
Prerequisites
A PayPal Payments Pro account
Creating a PayPal Sandbox Test Account
The first step is to create a new PayPal Sandbox Test Account. Here』s how to do so:

Access the PayPal Developer site and log in with your PayPal personal or business account. If you don』t have one, feel free to create one. It will only be used to create a new sandbox account.
Locate the Sandbox setting on the left side navigation menu, and click on Accounts.
You should see any existing sandbox accounts listed. To create a new one, click Create Account on the right side of the page.

Under Account Type select Business (Merchant Account). This is required for Gravity Forms.

Select the Country.
Click the Create button to save your account settings.
Once the new account is created, it needs to be upgraded to a PayPal Payments Pro account so that it is able to be tested with PayPal Payments Pro. To do so, hover over the listing for the newly created account, then click on View/Edit Account under Manage Accounts.

From the Profile tab of the Account Details page, locate the Account Type header. Click on the Upgrade to Pro link.

Click the Enable button to upgrade this sandbox account to PayPal Payments Pro.

Getting Your Sandbox Credentials
Now that you have a PayPal Payments Pro sandbox account, you will need to setup the credentials.

From the Profile tab of the Account Details page, click the Edit button.

Locate the Email ID header and enter the email address you would like to use with this sandbox test account.
Locate the System Generated Password header and make note of the account password. Alternatively, you can click the Change Password link to change the password to something more memorable.
Note: This is not a live account. Setting something like a very basic password is usually a good thing in these scenarios as it will be easier to remember, and security of sandbox accounts is not a high priority.

Click the Save button to commit your changes.

You』re now ready to follow the next section which will take place in the PayPal Manager.
Setting Up the PayPal Manager
After getting your sandbox credentials set up, you』ll need to configure the PayPal Manager to use those credentials.
Checkout Page Settings

Log into the PayPal Manager with your PayPal account.
At the top of the page, click on Service Settings, then on Hosted Checkout Pages. Select Set Up to begin the setup.

Under Choose your settings, ensure Transaction Process Mode is set to Test. If not already set, change it accordingly.

Under Display options on payment page, an Error URL needs to be defined. As this will be overridden with the API, enter a placeholder such as https://example.com.

Under the PayPal Express Checkout header, locate the PayPal Sandbox email address option. Within this field, enter the email address for the sandbox account you created in the previous section of this article.
Note: Be sure that this step is accurate, and there are not any spaces before or after the email address in the field, as this will cause errors when testing.
Within the Billing Information section, set any fields that you want to collect as Required as well as Editable.
Skip down to the Payment Confirmation section. You will see an option labeled Show confirmation page. Set this to On my website.

At the bottom of the page under Security Options, find the Enable secure token option and set it to Yes.

Once all of your settings are configured, click the Save Changes button at the bottom of the page.

Fraud Protection Settings
As this is a test account and is not processing live transactions, it』s a good idea to remove the fraud protection as it eliminates the possibility of test transactions being flagged as fraud.
To do so, access the Fraud Protection menu item at the top of the page. From there, go to the Test Setup page, then Edit Standard Filters.
Once on the standard filters page, uncheck each of the checkboxes and save your changes. Fraud protection filters are now disabled.
Credentials
Your PayPal Payments Pro sandbox credentials will be the same as your current credentials used to log into the PayPal Manager.
Test Credit Card Number
To access your test card number, log into the PayPal Developers site and access the sandbox account you previously created in this article. Within this, you will see card numbers that can be used for testing purposes.

Creating a Feed for the Help Scout Add-On

SummaryCreate a FeedFeed Settings ScreenUpdating Customer InformationAdd-On Hooks

Summary
Before the Help Scout Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, automatically creating and assigning a customer conversation to your support team when a form is submitted.
Create a Feed
To create a feed to Help Scout using the Help Scout Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Help Scout.
Once within your desired form, hover over Settings and click on Help Scout.
Click Add New to create a new feed. You will be presented with the Help Scout feed settings screen where you can configure the behavior of the feed.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshots below.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
Select the Help Scout Destination Mailbox that the conversation will be sent to.
Assign To User: Select a user if you would like to automatically assign a specific Help Scout user to the conversation, or choose Do Not Assign if you would like the conversation to be unassigned when created.
Under Customer Details, map each of the fields to the desired form field that will contain the customer』s information
Note: With Help Scout』s Mailbox API 2.0, used by Gravity Forms Help Scout Add-On v1.6+, the customer First Name field is now required; if a value is not passed, Help Scout will not create the conversation.
Under Message Details, you can format the conversation that will be created. Subject and Message Body will affect the content. Multiple Tags can be added, and a CC may be included. Note that the Attachments field will only show up here if you have a File Upload field on your form. Warning: The Help Scout API only accepts files up to 10MB in size, and a larger attachment will prevent the creation of the conversation. We recommend configuring your form field to ensure the max file size setting is less than this Helpscout limit.
Under Message Options, select the Message Status and Type to be used for the new conversation. For most use cases this will simply be Email. You can also add a Note and send an Auto Reply.
Conditional Logic: If unchecked, every successful form submission will be sent to Help Scout. If you wish to set specific conditions for sending form data to Help Scout, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Updating Customer Information
The Help Scout Add-On now supports updating customer information in the customer』s profile based on the email address.

Name
The first name/last name will be replaced with any new value for a customer match (submission using the same email).

Phone Number
Any phone number sent will be appended as an additional phone number for a customer match (submission using the same email).

Add-On Hooks
The Help Scout Add-On provides hooks that can be used to modify the default functionality or extend it. For more information, review the Help Scout Add-On Hooks.

Database Structure

Tableswp_gf_addon_feedwp_gf_addon_payment_callbackwp_gf_addon_payment_transactionwp_gf_draft_submissionswp_gf_entrywp_gf_entry_metawp_gf_entry_noteswp_gf_formwp_gf_form_metawp_gf_form_viewChanges from Gravity Forms 2.2IntroductionChangesThe Migration Process

Here』s how Gravity Forms is structured within your database:

Note: This structure applies to Gravity Forms version 2.3 or higher.

Tables
wp_gf_addon_feed
Contains Gravity Forms feeds.

id
Contains the unique feed ID.
form_id
Contains the ID of the form that the feed is associated with.
is_active
Defines if the feed is active or not. Integer is used as a boolean (0 is false, 1 is true).
feed_order
The order in which the feed is processed if multiple feeds exist.
meta
Meta information related to the feed. Stored as JSON.
addon_slug
The slug of the add-on that the feed is associated with.

wp_gf_addon_payment_callback
Contains information related to payment callbacks that have been received.

id
The row ID.
lead_id
The entry ID associated with the callback.
addon_slug
The add-on associated with the callback.
callback_id
The callback ID.
date_created
The date that the callback was received.

wp_gf_addon_payment_transaction
Contains transaction details.

id
The transaction ID.
lead_id
The entry ID associated with the transaction.
transaction_type
The transaction type.
transaction_id
The unique transaction ID.
subscription_id
The subscription ID, if applicable.
is_recurring
Defines if this is a recurring subscription. Integer is used as a boolean (0 is false, 1 is true).
amount
The amount of the transaction.
date_created
The date the transaction was created.

wp_gf_draft_submissions
Holds draft submissions created by the save and continue feature.

uuid
The unique ID of the draft submission.
email
The email address associated with the draft submission.
form_id
The form ID that the draft submission is associated with.
date_created
The date the draft submission was created.
ip
The IP address that created the draft submission.
source_url
The URL that was used to submit the draft submission.
submission
Submission details regarding the draft submission.

wp_gf_entry
Contains Gravity Forms entries.

id
The unique entry ID.
form_id
The form ID that the entry is associated with.
post_id
The ID of the post that was created from the entry, if applicable.
date_created
The date that the entry was created.
date_updated
The date that the entry was last updated.
is_starred
If the entry is starred. Integer is used as a boolean (0 is false, 1 is true).
is_read
If the entry has been marked as read. Integer is used as a boolean (0 is false, 1 is true).
ip
The IP address that submitted the entry.
source_url
The URL of where the submission took place.
user_agent
The user agent of the entry submitter.
currency
The currency used in the entry, if applicable.
payment_status
The status of the payment, if applicable.
payment_date
The date that the payment took place, if applicable.
payment_amount
The amount of the payment, if applicable.
payment_method
The transaction method used to process the payment, if applicable.
transaction_id
The transaction ID associated with the entry, if applicable.
is_fulfilled
If the transaction has been fulfilled, if applicable.
created_by
The ID of the user that created the entry, if applicable.
transaction_type
The transaction type, if applicable.
status
The current entry status.

wp_gf_entry_meta
Contains additional metadata related to entries. Details from fields as well as add-ons are stored here.

id
The unique ID.
form_id
The form ID that the entry meta is associated with.
entry_id
The entry ID that the meta is associated with.
meta_key
The meta key.
meta_value
The value stored under the meta key.
item_index
The item index.

wp_gf_entry_notes
Contains notes that were placed on an entry.

id
The note ID.
entry_id
The entry ID that the note is associated with.
user_name
The user name that created the note.
user_id
The user ID that created the note.
date_created
The date that the note was created.
value
The contents of the note.
note_type
The type of note that was left, if applicable.
sub_type
The secondary note type, if applicable.

wp_gf_form
Contains the forms that exist within Gravity Forms.

id
The form ID.
title
The form title.
date_created
The date that the form was created.
is_active
If the form is active. Integer is used as a boolean (0 is false, 1 is true).
is_trash
If the form is trashed. Integer is used as a boolean (0 is false, 1 is true).

wp_gf_form_meta
Contains metadata associated with forms.

form_id
The form ID that the metadata is associated with.
display_meta
Meta related to how the form and fields are configured.
entries_grid_meta
Additional meta related to entries and how they will be displayed.
confirmations
Confirmation configuration.
notifications
Notification configuration.

wp_gf_form_view
Contains details on form views.

id
The ID.
form_id
The form ID that the data is associated with.
date_created
The date that the row was created.
ip
The IP that accessed the form.
count
The number of times that the IP accessed the form.

Changes from Gravity Forms 2.2
Introduction
The database schema was changed in Gravity Forms 2.3 to enable significant performance enhancements and to allow key features to be added. Code that uses the Gravity Forms API (GFAPI) will not be affected and will continue to work as before. However, custom code and add-ons that access the database tables directly will need updating.
Changes
The following changes were made to the tables and columns.

rg_lead -> gf_entry
rg_lead_details + rg_lead_meta tables -> gf_entry_meta
All lead_id columns -> entry_id
rg_form -> gf_form
rg_form_view -> gf_form_view
rg_form_meta -> gf_form_meta
rg_incomplete_submissions -> gf_draft_submissions

Note: Despite of tables gf_addon_feed, gf_addon_payment_callback and gf_addon_payment_transaction are using the gf_ prefix, they』re not part of the changes done in this version. If for any reason you need to delete the new tables to run the upgrade from scratch again, make sure to skip these tables.

The Migration Process
The automatic migration process creates the new tables and copies all the data over to the new tables in a series of background tasks. If the task stops, for example, due to a server restart then the migration will continue with a scheduled cron task. If there』s a database error then the migration will stop and try again later.

Creating a Feed for the Mollie Add-On

IntroductionPre-RequisitesCreate/Edit A Mollie FeedFeed SettingsBasic Feed SettingsProducts & Services SettingsOther Settings Conditional LogicUser Registration OptionsNotes

Introduction

The last step of integrating Mollie with Gravity Forms is creating a feed. A feed communicates information to Mollie each time a visitor successfully submits your form. This is a critical step. If it is not completed, nothing is sent to Mollie for processing.

Pre-Requisites

Set-up the Mollie Add-OnCreate a Mollie Compatible Form

Create/Edit A Mollie Feed

Note that a pre-configured feed will be automatically created for the Mollie Add-On when a form containing a Mollie Field is saved, and a feed for Mollie does not already exist.

To access your Mollie feeds list:

Click on Forms in the left side menu.Select the form that you want to use with Mollie.Hover over Settings and click on Mollie.Click Edit to edit the existing Mollie feed, or Add New. You will be presented with the feed settings screen pictured below.Complete the settings you require. See below for descriptions of all the available feed settings.Click Update Settings to save your feed.

Feed Settings

Mollie Feed Settings screen

Basic Feed Settings

SettingDescriptionNameA descriptive name so you can clearly identify this feed within the feed list page. Required.Transaction TypeProducts and Services are single one time payments. (Subscriptions/recurring payments are not currently available for the Mollie Add-On).

Products & Services Settings

SettingDescriptionPayment AmountDefine what to use for the payment amount. For example, you could choose a specific product Field, or the form Total. Required.

Other Settings

SettingDescriptionBilling InformationMap your form fields to the Mollie billing fields they will send data to. Mostly Required.

Note: Billing information fields are almost all required (only the Address Line Two and State are optional) to create an Order with a Payment. Customer data only appears in Order details within the Mollie dashboard.

Conditional Logic

SettingDescriptionEnable Conditional LogicIf enabled, allows you to set conditions on when this feed will be triggered. Allows you to configure multiple feeds with different behaviors, and trigger one of them based on conditional logic criteria. Refer to this article for more.

User Registration Options

This setting is applicable if you are utilizing the User Registration Add-On.

SettingDescriptionDelay User RegistrationDelay registration of a user (based on the submitted details), until the payment has been received.

Notes

Your Gravity Forms Currency Settings must match the Currency Settings in your Mollie account or you will not be able to create a feed.Testing your Feed with a Mollie Test Account is highly recommended before running transactions on your live account.If you initiate a refund for a transaction within the Mollie dashboard, the Form Entry will update with a webhook to show the payment status as Refunded.While the email is passed into the Mollie Account during feed processing (if you have matched the Email field in your feed), it will not be displayed in the Mollie Account transaction record. You can still search by email address in the Mollie Account transaction list and it will display matching records.When connecting and testing transactions in Test Mode, the customer data is always shown as 「Test Consumer/[email protected]」 in the Mollie Dashboard, under Payment Details, regardless of the billing information mapped.

Gravity Forms Custom Development

CodeableJob Board

If you need to customize Gravity Forms to fit your needs or add a functionality that is not solved by an add-on or a help document, you might need to hire a developer to work on your particular challenge. There are many, many freelance developers and agencies available that offer WordPress development and customization assistance, but we would like to mention two particular areas.
Codeable
Need to customize Gravity Forms to suit some particular need? Gravity Forms has partnered with Codeable, the #1 outsourcing service for WordPress, to provide Gravity Forms customization services. They can provide quality development from hand-picked Gravity Forms specialists for any project size and budget, and can quickly provide a no obligation estimate of what it may cost. You can reach them via: Get Started Now!
Job Board
If you are looking for someone to work on your project, or if you are offering your services to help, check out our new Community Forum Job Board as a possible starting place.
We do not vet or provide recommendations for any individual developer there, it is an open forum, but our community is certainly full of talented folks that may be able to help get you where your project needs to be!

Creating a Feed for the Stripe Add-On (version 2.9 and earlier)

Pre-RequisitesIntroductionCreate Your FeedProducts & Services SettingsSubscription SettingsPayment Collection Settings (Stripe v2.6+)Stripe Checkout SettingsStripe Credit Card Field SettingsUse a Different Stripe Account (Stripe v2.8+)Other SettingsSummaryNotes

Pre-Requisites

Setup the Stripe Add-On
Create a Stripe Compatible Form

Introduction
The last step of integrating Stripe with Gravity Forms is creating a feed. A feed communicates information to Stripe each time a visitor successfully submits your form. This is a critical step. If it is not completed, nothing is sent to Stripe for processing.
Create Your Feed

Open the form you created during the Setting up a Stripe Compatible Form article. If you have not created this form, visit Setting Up A Stripe Compatible Form. Select Forms to view your forms. Hover over your Stripe compatible form, then hover over Settings, and select Stripe from the dropdown.

You will be directed to a Stripe Feeds page. Select Add New or Create One to begin creating your Stripe Feed.
Give your Feed a unique Name. This prevents any trouble with distinguishing the feed later on. It is not displayed to the user.
Select the Transaction Type. Products and Services are single one time payments while the Subscription is a recurring payment. Refer to the sections below for instructions on how to setup each transaction type.

Products & Services Settings

Select which data determines the Payment Amount. You may choose a specific Product Field or the overall Form Total. This is dependent on the fields on your form.

Subscription Settings

Select which data determines the Recurring Amount. You may choose a specific Product Field or the overall Form Total. This is dependent on the fields on your form.
Set the Billing Cycle. This determines how often the recurring payment should occur. By default, the Billing Cycle charges the customer once a day. You can change this option by modifying the number that precedes the time interval, or by changing the time interval itself.
Check the box to enable a Setup Fee. This can be mapped to a pricing field to charge an initial fee to start your subscription. This is dependent on the fields on your form. If you select this option, the Trial field will be unavailable.
If you did not enable the Setup Fee, you have the option to enable a Trial. When enabling the trial period, select the amount of days you would like the trial to last. The customer』s recurring payment will not begin until the end of the Trial Period.

Payment Collection Settings (Stripe v2.6+)
The Payment Collection Method lets you choose how payment information will be obtained.
Note: The Payment Collection Method settings is only available for Stripe version 2.6 and above.
Stripe Checkout Settings
The Stripe Checkout Settings section will only appear if you have Stripe』s Payment Collection Method set to Stripe Payment Form (Checkout) in the Stripe settings.
Note that from Stripe Add-On version 3 and later, these settings have been removed, and Stripe form configuration options are handled from within your Stripe account settings.

The Logo URL is a relative or absolute URL pointing to a square image of your brand or product. The recommended minimum size is 128px x 128px. The supported image types are .gif, .jpeg, and .png.
Add the Name of your company or website.
Add a Description for the product or service being purchased.
Enable/Disable the Billing Address. When this is enabled, Stripe』s checkout form will collect the billing address before the payment information is entered. The first image below shows what the Stripe Checkout form looks like with the billing address enabled. The second image is what is displayed after the billing information is filled out or if billing information is disabled. These images show where the Logo URL, Name, and Description display on the checkout form.

Stripe Credit Card Field Settings
This collection method was deprecated in Stripe Add-On version 3.4 and is not recommended. Refer to this document for more information.
The Stripe Credit Card Field Settings section will only appear if you have Stripe』s Payment Collection Method set to Stripe Credit Card Field (Elements) in the Stripe settings.

Under Billing Information, map the Gravity Form form fields to the Stripe Address fields to send the information to Stripe.

Use a Different Stripe Account (Stripe v2.8+)
The Switch Accounts button under Stripe Account settings allows you to specify that the feed use a different Stripe account than the one set on the Stripe Settings page.
Note: The Switch Accounts setting is only available for Stripe version 2.8 and above.

Under Stripe Account, click the Switch Accounts button.
Select the Mode to use for Stripe integration: Live or Test. Live is for real transactions, and Test is for testing the integration and submitting test forms.
Click the 「Connect with Stripe」 button.
If you have multiple accounts under this Stripe user, you can use the Switch Account drop down menu to select the Stripe account you wish to connect to.

Fill out the form and click the 「Authorize access to this account」 button. Alternatively, if you are using Stripe in development mode, you can click the 「Skip this account form」 link at the top of the page.
You will be returned to the Feed Settings page. You should see 「Connected to Stripe as」 with your account name.
Follow the same instructions to enable the webhook as you did when setting up your Stripe account. Refer to this article for details.

Other Settings

The Customer Information section is only available when the Transaction Type is set to Subscription. Map the Email Field to Email. You can map whichever field you would like for the Description. This will be used to uniquely identify your customer. You may also map a Coupon to a field on the form that contains a coupon code setup in your Stripe dashboard. This discount will apply to the recurring charges.
If you want to send custom Metadata to Stripe, enter text to identify the data and map it to a form field. This data displays under the payment information in Stripe. Click the + to add more than one key. A maximum of 20 keys may be sent. See Note E. Example:

The Stripe Receipt setting is only available when the Transaction Type is set to Products and Services and you have added an Email field to your form. If you would like to send a receipt, select an email field from the drop down. See Note F.
If you would like the Stripe integration to occur conditionally, enable Conditional Logic. This functions the same as Conditional Logic on fields by only triggering the execution of this Stripe Feed if the condition is met. Conditional Logic also allows you to configure multiple Stripe Feeds for a single form and trigger the correct one based on Conditional Logic. Refer to the Conditional Logic feed article for more information.
Click Update Settings to save the feed.

Summary
Now that you have finished setting up your Stripe Feed Settings, you can verify that your Stripe is indeed integrated with Gravity Forms by visiting Verifying Your Stripe Integration.
Notes
A. If you delete the Credit Card field from your form, the Stripe feeds will automatically deactivate to prevent them running during form submission, which as the field is missing, would cause a validation error due to Stripe being unable to capture the card details.
B. If a form has the Credit Card or Stripe Card field on it, these take precedence over the payment collection method of Stripe Payment Form (Stripe Checkout) and Stripe Payment Form (Stripe Checkout) is not used.
C. If a form has both the Credit Card and Stripe Card fields on it, and Conditional Logic is not used to show/hide one of them, the Stripe Card field takes precedence. Please note that a form should not be created where multiple credit card fields are visible on form display.
D. You can create multiple Stripe feeds for your form; however, you must configure conditional logic on them. The Stripe Add-On will only process one feed during submission. If conditional logic is not configured, it will use the first feed it finds.
E. Metadata displays on the Stripe payment page for Product and Services transaction type but not for the Subscription type. For Subscription type, metadata displays on the Stripe customer』s page.
F. If you want Stripe to send a receipt on payment from your Stripe Account (in addition to or instead of your Notifications), you will need to configure that in your Stripe account as it』s not enabled by default at Stripe. You can enable it in your Stripe Dashboard under Emails: https://dashboard.stripe.com/account/emails.

Deprecated Gravity Forms Database Tables

The following database tables have been deprecated as of Gravity Forms 2.3, and should not be utilized by any custom code or third-party plug-ins etc.

wp_rg_form
wp_rg_form_meta
wp_rg_form_view
wp_rg_incomplete_submissions
wp_rg_lead
wp_rg_lead_detail
wp_rg_lead_detail_long
wp_rg_lead_meta
wp_rg_lead_notes

For more detail on the Gravity Forms 2.3 upgrade process, refer to this article.

Creating a Square Sandbox Account for Testing

IntroductionSign-up for a Square Developer Account

Introduction
Testing your configuration and your forms without processing live transactions is an essential and recommended tool in your arsenal when working with payment processing forms. Configuring this in Square is very easy.
Sign-up for a Square Developer Account

Go to the Square Developer Account Sign-in: https://squareup.com/signup?v=developers

Once you』ve configured your account, go to the Developer Dashboard and create a new Application: https://developer.squareup.com/apps

From the New Application Screen, Give your application a name and click Save.

You will be returned to the Developer Dashboard and presented with a list of Sandbox Test Accounts. Select the one you just created and click Launch to open the Seller Sandbox Dashboard.

This will launch this portal (Developer Dashboard): https://squareupsandbox.com/dashboard/

Configure your Sandbox Account in the Square Add-on.