Payment Confirmation Emails

Step-by-step Basic Payment Confirmations

Use Emails to send confirmation messages to customers, including a detailed breakdown of their Basic Payment Submission

Prerequisites

• You have installed eCommerce Module v1.1.4 or later. Check out Install or Manage Modules to find out how you can install the latest version.
• You have set up a Basic Payment Form using the Stripe Payment Gateway

Introduction

You can now add details of a customer's Basic Payment Form to Workflow and Autoresponder transactional emails. Give your Client and the customer peace of mind, as well as valuable records for their safekeeping. Within the email, you can also access any fields that were submitted along with the original Form. Learn more here: Dynamic Content in Workflow and Autoresponder Emails

Step 1) Include the Payment Summary Feature

To include the details of the customer's most recent Order, include the following Liquid tag:

Example
liquid
Copy
{% include 'ecommerce/payment_details', layout: 'default' %}

This can be outputted in one of two places:

• Inside the body of an automation email e.g. autoresponder or workflow
• Inside a Form Confirmation Layout

Placing in either of these locations will allow the system to identify the last submitted Form case and, if there is one, the associated payment.

Step 2) Create or Find a Layout

File Structure

You can use an existing Layout, or create a new one in this File Structure: layouts/modules/module_14/payment/my_layout.liquid

Basic Payment Forms Folder Structure

Step 3) Develop the Layout

Inside your automation email body, you'll have access to the Form object: {{form.properties}} This contains the fields submitted with the Form. Learn more here: Dynamic Content in Workflow and Autoresponder Emails You'll still have access to these fields throughout the Payment Details Layouts as they will be inherited.

***Accessing Payment Details ***The layout file will have access to the this object, which will contain details about the Payment: {{this}} Within this object, you'll have access to the following fields: