About Payment Method Views

This article provides an overview of Knack's payment method view type for E-commerce.

This article covers the following topics:

• Managing Payment Method Views

  • Adding Payment Method Views

  • Editing Payment Method Views

  • Deleting Payment Method Views

• Payment Method View Settings

  • Settings

  • Emails

  • Rules

  • Submit Rules

  • Record Rules

• Using Payment Method Views in Your Apps

  • Storing Payment Methods

  • Updating Payment Information

  • Removing Payment Information

• How to Guides

 

What are payment method views?

Knack's payment method view is a type of E-commerce view. While payment views allow you to accept a payment from someone, payment method views allow you to store, update, or remove a specific user’s payment method.

The payment method can then be used to facilitate future payments, whether it’s the user paying themselves or an account administrator charging the user on their behalf.

 

Managing Payment Method Views

Adding Payment Method Views

Payment method views can be added in two different places:

• In a login-protected starting page. A starting page is a top-level page within your app.

• In a child page that has access to a specific user record

To add your first payment method view, locate the "E-Commerce" option in the view menu and select the “Payment Method” view type:

 

After selecting the view type, then you will be guided through a series of options to customize the payment method view. First, you can select your payment processor and fill out your credentials:

Afterward, you can choose the account/user record to which the payment method should be associated with. This could be the currently logged-in user or someone else for whom you need to update their payment information:

 

The final step is to review the view’s summary to confirm everything was selected properly, and to select the "Add Payment Method View" button: 

 

Editing Payment Method Views

To access the payment method view settings, click the pen icon when hovering over the payment view. This will open the view settings in the toolbox to the left:

 

Deleting Payment Method Views

You can delete your payment method view at any time by clicking the trashcan icon when hovering over the payment view:

 

 

Payment Method View Settings

Payment method views have settings similar to payment views and allow you to change the behavior and looks of your view. Now, let's delve into each of these settings and understand their implications.

Settings

The "Settings" section contains basic settings about how the view will behave, for example, the payment action, processors, and the fields and currency being used:

The Change Action button will lead you to a modal pop-up where you can choose the payment processor to be used. It also gives you the option to enable test mode for the payment method view while building your application:

After selecting the "Next" button, you will then have the option to select the where the payment method will be saved for which user:

Lastly, you can view the Summary of the changed action selection after selecting the "Next" button again. This will allow you to select "Stage Changes" and save your updated settings:

• Payment Processors: This section is where you will select the payment processor that your payment method form will use. 

• Test Mode: You have the option to use payment processors in Test Mode. Stripe will store test customers in a specific section, so please remember to disable test mode if you plan to store real customer information.

 

Emails

In the Emails settings section, you can customize the emails that are sent after the payment information has been successfully submitted:

 

Rules

Payment rules work exactly like record rules in a form view. An excellent use case for a payment method rule is to update a field in the user's record, allowing you to easily identify who has not yet updated their payment information.

To add a payment rule, simply click on the "Add Rule" button located in either the "Submit Rules" or "Record Rules" tab. From there, you can set your desired criteria for the rule:

Submit Rules

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

 

 

Record Rules

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

 

 

Using Payment Method Views in Your App

Now that you have successfully configured your payment method view, let's explore how it functions:

Storing Payment Methods

If the user has not previously stored their payment method, the payment method view will present the credit card form:

When this form is submitted, a Stripe customer will be created in Stripe, and a payment method record will be added to the "Payment Methods" data table found in the Data section of the Builder. 

You can then use the "Payment Method ID" field value to locate the payment method in your Stripe Dashboard.

 

Updating Payment Information

If the user has stored their payment method already, they’ll see a link where they can choose to update or remove their existing payment method:

 

If the user chooses to update the payment method, they’ll have access to a credit card form:

 

Removing Payment Information

Using the same link as shared above, if a user selects the "Remove Payment Information" button, they’ll be redirected to the original payment method view with the credit card form:

 

How To Guides:

• Save a User's Payment Method

• How to View a Customer's Payment History

 

---