Payment received trigger

The Payment Received trigger in Stack is a powerful tool designed to automate and streamline your business processes by capturing all incoming payments. This trigger can be customized with filters to target specific scenarios, helping you respond promptly to real-time customer transactions.

What is the Payment Received Workflow Trigger?

The Payment Received trigger automates actions based on incoming payments within your CRM. It activates workflows whenever a payment event occurs, such as successful or failed transactions, or specific product purchases. This allows you to automate actions like sending confirmation emails, generating invoices, or updating customer records. You can apply filters to target specific scenarios, such as subscription renewals or failed payments, enabling precise workflow automation.

Key Benefits of the Payment Received Workflow Trigger

• Automated Payment Confirmation: Automatically send confirmation emails or messages to customers when a payment is processed, enhancing customer satisfaction.
• Subscription Management: Update subscription statuses automatically when payments succeed or fail, streamlining subscription management.
• Payment Failure Resolution: Notify customer support or sales teams to address payment failures promptly, improving issue resolution.

How to Use the Payment Received Trigger

1. Add the Trigger: In your workflow, add the “Payment Received” trigger.
2. Apply Filters: Click “add filter” to choose and customize filters for your workflow.

Filters

Customize your trigger with various filters to refine when your workflow activates. Here are some options:

• Payment Source: Invoice, Funnel/Website, Text2Pay link
• Transaction Type: Customer present/first transaction, Customer not present/subscription transaction
• Payment Status: Success, Failed

For instance, to trigger a workflow when a two-step order form is submitted, select:

1. Payment Source > is > Funnel
2. Add filter > Sub-Source > is > two-step order form

If/Else Conditions

Enhance your workflows with If/Else conditions to branch actions based on payment characteristics, such as amount or status.

Custom Values

After setting up your Payment Received trigger, access a range of custom values for use in SMS, emails, and notifications. Here are some examples:

• Payment Source: {{payment.source}}
• Customer Name: {{payment.customer.name}}
• Invoice Number: {{payment.invoice.number}}
• Total Amount: {{payment.total_amount}}

Frequently Asked Questions

What is the sub-source filter?
Sub-source filters specify the origin of a payment, such as a one-step order form or upsell, within a source like funnels or websites.

Will this trigger include initial and subsequent subscription payments?
Yes, the trigger activates for both initial and subsequent payments, including those processed in the background.

What does Customer present/first transaction mean?
This refers to transactions where the customer is actively making a payment, including one-time purchases and initial subscription orders.

How can I configure the trigger for successful subsequent subscription transactions?
Set the source type to Funnel/Website and transaction type to “Customer not present/subscription transaction” with a successful payment status filter.

Will failed payments also be captured in this trigger?
Yes, the trigger captures both successful and failed payments by default. Use the “Transaction status” filter to specify your needs.

Additional Benefits

• Dunning Management: Trigger email sequences for failed payments to recover revenue and reduce churn.
• Customer Segmentation: Use payment data to create segments for targeted marketing and personalized experiences.
• Sales Performance Tracking: Monitor payment data to identify trends and optimize sales strategies.
• Integration with Accounting Systems: Update accounting records automatically with payment information.
• Handling Trial Period Transactions: Manage trial period transactions effectively, enhancing customer experience and retention.
• Integrating Text2Pay Links: Automate workflows for payments received through Text2Pay links, improving payment processing and customer communication.

Overview

The Payment Received trigger in Stack automates actions based on payments received through the CRM. This includes one-time purchases, subscription charges, and invoice payments. By using this trigger, businesses can streamline their processes, such as sending confirmation emails, updating records, or managing failed payments in real time. Customize it with filters like payment type, source, and transaction status to suit specific business needs.

Trigger Name

Payment Received

Trigger Description

The Payment Received trigger captures and acts on payment-related events within Stack workflows. Whether it’s a successful transaction, a failed payment, or a subscription renewal, this trigger initiates automated actions such as sending notifications, updating subscription statuses, or managing dunning processes. Customize this trigger by filtering based on payment source, product, transaction type, and payment status.

Key Features

• Captures all types of payments: one-time, subscription, and invoices.
• Supports real-time automation for both successful and failed payments.
• Customizable with filters: source, product, and transaction status.
• Automates responses like sending receipts, notifications, or triggering follow-ups.

How to Configure

Step-by-Step Guide

1. Add the Payment Received Trigger:

   • In your workflow builder, select the Payment Received trigger from the list of available triggers.

2. Name Your Trigger:

   • Provide a descriptive name for the trigger, such as “New Subscription Payment” or “Invoice Payment Received.”

3. Apply Filters (Optional):

   • Make your trigger more specific by applying filters. Available filters include:
     • Payment Source: Funnel, website, invoice, Text2Pay links.
     • Sub-Sources: Choose from options like a one-step order form, two-step order form, or upsell.
     • Transaction Type: Select between “Customer Present” (first transaction) or “Customer Not Present” (subscription/recurring).
     • Payment Status: Filter by successful or failed payments.

4. Use If/Else Conditions (Optional):

   • Customize the workflow further by adding If/Else conditions based on payment details. For example, send different emails depending on whether the payment was successful or failed.

5. Customize Actions Based on Payment Data:

   • Use Custom Values from the payment data (e.g., amount, product name, payment method) to personalize follow-up actions, such as sending confirmation emails, updating customer records, or notifying team members.

6. Save and Activate:

   • Once configured, save and activate the workflow to start automating your payment-based processes.

Example

Scenario

A business wants to automatically send a confirmation email when a customer successfully makes a payment for an online course.

Workflow Setup

• Trigger: Payment Received
• Name: “Online Course Payment”
• Payment Source: Funnel
• Payment Status: Success

Actions

• Send a confirmation email to the customer with course access details.
• Update the customer record in the CRM with the payment status.
• Notify the sales team about the successful payment.

Outcome

When a customer successfully makes a payment via the two-step order form in the funnel, the workflow automatically sends them a confirmation email, updates their CRM record, and notifies the sales team.