Workflow Trigger: Payment Received
Automatically trigger workflows when payments occur—covering successful charges, failed transactions, subscriptions, invoice payments, funnels, and calendar payments.
Turning Payment Events Into Automated Business Processes Instead Of Managing Revenue Activities Manually
Every payment event represents an important moment in the customer lifecycle. Successful payments can trigger onboarding, product delivery, account updates, and customer communication, while failed payments often require recovery actions, notifications, and follow-up processes.
BizStackPro's Payment Received workflow trigger allows businesses to automatically respond whenever payment activity occurs, helping teams deliver products, update CRM records, manage subscriptions, send receipts, recover failed payments, and maintain consistent customer experiences.
Without payment-based automation, businesses may delay onboarding, overlook failed transactions, create inconsistent customer communication, or rely on manual processes that become increasingly difficult to manage as transaction volume grows.
This guide explains how the Payment Received trigger works, how payment filters control workflow entry, and how businesses can create more efficient revenue, subscription, and customer management systems inside BizStackPro.
Before automating payment events, it helps to understand how products, subscriptions, invoices, checkout systems, payment gateways, CRM records, workflow automation, and customer lifecycle management work together inside BizStackPro.
What the Payment Received Trigger Does
The Payment Received workflow trigger lets you automate actions whenever a payment event occurs in BizStackPro. This includes one-time payments, subscription renewals, invoice payments, funnel purchases, calendar payments, and failed transactions. It’s ideal for sending receipts, updating CRM records, managing subscriptions, and responding to payment issues in real time.
Quick Tip: Build two workflows—one for successful payments (confirmations + onboarding) and one for failed payments (alerts + recovery follow-up). It keeps your logic clean and easier to troubleshoot.
Key Capabilities
- Automation: Trigger confirmations, CRM updates, and internal notifications automatically.
- Filtering: Target by source, transaction type, product, price, and payment status.
- Real-time response: React instantly to incoming or failed payments.
- Branching: Use If/Else conditions to route contacts based on payment data.
- Tracking: Apply tags and store details for reporting and segmentation.
How to Add the Payment Received Trigger
- Open Workflows: Go to Automation and open Workflows.
- Create or edit a workflow: Start a new workflow or open an existing one.
- Add the trigger: Click Add New Workflow Trigger and select Payment Received.
- Apply filters: Choose filters to control which payment events should enter the workflow.
- Add actions: Send confirmations, apply tags, notify your team, or start onboarding.
- Save + publish: Save the workflow, toggle to Publish, and test with a controlled payment.
Note: When you select a filter, additional sub-filters may appear to help you target payments more precisely.
Available Trigger Filters
- Payment source: Invoice, Funnel/Website, Calendar, or Text2Pay
- Sub-source: One-step order form, two-step order form, upsell, recurring invoice, or e-commerce store
- Transaction type: Customer present (first transaction) vs customer not present (subscription/renewal)
- Global product: Target a specific global product
- Price: Target a specific product price
- Payment status: Success or Failed
Using If/Else Conditions with Payments
After filters are applied, use If/Else branches to route contacts based on payment attributes such as:
- Product purchased
- Funnel or website used
- Calendar used (if applicable)
- Payment source (invoice, funnel, calendar, etc.)
- Payment status (success or failed)
- Payment amount thresholds
Custom Values Available with Payment Received
This trigger exposes custom values you can use in messages and notifications—helpful for receipts, troubleshooting, and personalization.
Payment details
Source, currency, amount, status, transaction ID.
Customer info
Name, email, phone, address, country.
Invoice data
Invoice name/number, invoice URL, due date, recorded by.
Gateway details
Payment gateway, card brand, last four digits (when available).
Common Payment Scenarios
- Subscription renewals: Trigger workflows for background subscription charges.
- Failed payments: Notify customers and launch recovery follow-up automatically.
- High-value transactions: Alert your team when large payments are received.
- Invoice payments: Track invoices and update records instantly.
Automate payment follow-ups without manual work
Trigger receipts, onboarding, tagging, and recovery actions the moment a payment succeeds—or fails.
Opens in a new tab.
Frequently Asked Questions
Will this trigger include subscription payments?
Yes. The trigger can fire for first-time purchases and recurring subscription charges.
Can I trigger only successful or failed payments?
Yes. Use the payment status filter to target successful or failed transactions.
What does customer present vs customer not present mean?
Customer present refers to payments made during an active checkout. Customer not present refers to background subscription renewals.
Will this trigger fire for payment links?
Yes. It can capture payments from order forms, invoices, calendars, and payment links.
Can I use this trigger for failed payment recovery?
Yes. It is commonly used to automate retries and notifications for failed payments.
Build clean payment automations that scale
Use Payment Received to confirm purchases, manage subscriptions, and respond fast when payments fail—so your revenue operations stay consistent across funnels, invoices, and calendars.
Faster follow-up. Cleaner records.
Disclaimer: This site is NOT endorsed by Google, Facebook or YouTube in ANY WAY. All trademarks & Logo / branding are the property of their respective owners. Please Note: This site was created in BizStackPro by Ken George II (An Affiliate of BizStackPro) and may contain affiliate links.
Copyrights 2024 | AllAboutBizStackPro.Com | Pricing | About | Features | All Rights Reserved.