Table of Contents

Payment Views

Sarto Jama Updated by Sarto Jama

What are Payment Views?

With E-Commerce enabled in your app and payment processors added, the final step is to add a payment view, which is a type of payment view. The payment view includes options for calculating the total payment, displaying the payment summary, sending email receipts, and rules for updating other database records.

Manage Payment Views

Add Payment Views

In order to be able to insert a payment view in your app, you must include a numeric field in your object. A numeric field is required to determine the amount that will be charged. Numeric fields include any field that can be selected from the ‘Number’ menu:

When editing a page that deals with a specific record, such as an edit form or details view, you will have the option to add a "Payment" view under the “E-Commerce” view dropdown:

Adding, editing and deleting payment views behaves very similarly to other views. To learn more on how to add, edit, and delete views from your app, see About Views

Payment View Settings

The payment view has a unique set of features that are not available in other views, this includes additional settings, separate Payment Summary / Details sections, Email Receipts, and Payment Rules.

Settings

  • Payment Action: The Payment Action section will display the data source of your payment view. It also allows you to update the numeric field that will be used as the form’s payment total.
  • Payment Processors: This section is where you will select the payment processor that your form will use. 
  • Test Mode: Every Payment Processor can be used in Test Mode. Stripe will store TEST customers in a separate section, so if you want to store real customer information be sure to toggle test mode OFF.
Since E-Commerce is only available on Pro plans and above, Starter plans will always have Test Mode enabled.
  • Payment Total Field: This is the field that will be used to determine the grand total for the transaction.
  • Description Field: Payment description that will be passed along into Stripe. 
  • Currency: This is where you can choose a currency for your form. 
  • Submit Payment Button Text: Here you can set the display text of the button that submits payment information to your selected Stripe payment processor.

Payment Summary

This section displays what your current payment method view is doing and allows you to go through the setup wizard again if you need to change any settings.

Payment Details

Each payment method view can use its own payment processor. You can only select Stripe payment processors in this view type.

Emails

Control any emails sent after the payment information is successfully completed.

The submitted payment method details are not available to be displayed in an email. Click here to learn more about Emailing your Users.

Payment Rules

Payment rules work exactly like record rules in a form view. A great example of when to use a payment method rule is to update a field in the user’s record so you can tell who has yet to update their payment information.

To add a payment rule, click on the "Add Rule" button in either “Submit Rules” or “Record Rules” tab, then set your criteria:

Payment Rules will only trigger for successful changes to the connected payment method.
Submit Rules

Submit rules allow you to determine where to direct the user after the form is submitted:

You can learn more about using submit rules here.

Record Rules

Record rules allow you to update or insert records after the payment is successfully processed:

You can learn more about using record rules here.

Using the Payment View in your App

Payment Processing

Once the user submits the payment form, a new Payment record will be created and automatically connected to the record from the original parent form.

Click here for more on managing payment records in your database

Successful Payments

If a payment is successful, your user will be redirected to the completion page. At this time any emails and payment rules you defined in the checkout view will trigger immediately.

Errors

When a payment error occurs, a new payment record connected to the form record will be created with a Failed status. A failed payment will not trigger any email / payment rules in the payment view.

The user will be alerted that an error occurred, and will be able to fill out the form again and try submitting a successful payment:

image alt text

More specific details about the error will be added to the Notes field of the payment record:

How did we do?

Payments Object & Records

Payment Method Views

Contact