Who This Is For / When to Use
Use this trigger if you want to automate confirmations, follow-ups, internal notifications, tagging, or branching logic whenever a customer payment is processed through Kyrios.
What the Payment Received Trigger Does
The Payment Received trigger enrolls a contact into a workflow whenever Kyrios records a payment event. This includes:
One-time purchases
Subscription signups
Subsequent subscription charges
Successful payments
Failed payment attempts
The trigger fires in real time and can be refined using filters and If/Else conditions.
How to Add the Payment Received Trigger
Go to Automation > Workflows.
Create a new workflow or edit an existing one.
Click Add New Trigger.
Select Payment Received from the trigger list.
(Optional) Rename the trigger using Workflow Trigger Name.
Available Filters for Payment Received
Filters allow you to control which payment events trigger the workflow. Multiple filters can be combined.
Payment Source
Defines where the payment originated.
Invoice
Funnel / Website
Calendar
Text2Pay link
Sub-sources (when applicable):
One-step order form
Two-step order form
Upsell
E-commerce store
Transaction Type
Defines how the payment was processed.
Customer present / first transaction (one-time purchases or first subscription charge)
Customer not present / subscription transaction (recurring charges processed in the background)
Payment Status
Success
Failed
Global Product
Filter by a specific global product and price.
Example Filter Setups
Trigger Only on Successful Subscription Renewals
Payment Source is Funnel / Website
Transaction Type is Customer not present / subscription transaction
Payment Status is Success
Trigger Only on Failed Payments
Payment Status is Failed
Using If/Else Conditions With Payments
After the trigger, you can branch the workflow using an If/Else action to route contacts based on payment details.
Supported If/Else Payment Conditions
You can branch based on:
Product
Funnel / Website
Calendar
Payment Source
Payment Status
Amount Paid
Supported operators include:
is / is not
equal to / not equal to
greater than / less than
is empty / is not empty
Payment Custom Values
You can use payment-related custom values in emails, SMS, internal notifications, and other actions.
Payment Values
{{payment.source}}
{{payment.currency_symbol}}
{{payment.currency_code}}
{{payment.total_amount}}
{{payment.sub_total_amount}}
{{payment.tax_amount}}
{{payment.discount_amount}}
{{payment.transaction_id}}
{{payment.payment_status}}
{{payment.gateway}}
{{payment.method}}
{{payment.card.last4}}
{{payment.card.brand}}
Customer Values
{{payment.customer.first_name}}
{{payment.customer.last_name}}
{{payment.customer.email}}
{{payment.customer.phone}}
{{payment.customer.address}}
{{payment.customer.city}}
{{payment.customer.state}}
{{payment.customer.country}}
{{payment.customer.postal_code}}
Invoice Values
{{payment.invoice.name}}
{{payment.invoice.number}}
{{payment.invoice.issue_date}}
{{payment.invoice.due_date}}
{{payment.invoice.url}}
Common Issues and Fixes
The workflow runs on failed payments
By default, the trigger includes both successful and failed transactions. Add a Payment Status is Success filter if you only want successful payments.
The workflow runs for every subscription charge
Subscription renewals count as payment events. Use the Transaction Type filter to control whether the workflow runs on first payments or recurring charges.
The workflow runs for the wrong product
Add a Global Product filter to limit the trigger to a specific product or price.
FAQs
Does this trigger include subscription renewals?
Yes. The trigger fires for both first-time payments and recurring subscription charges.
Can I trigger workflows only for failed payments?
Yes. Use the Payment Status is Failed filter.
What does Customer present vs Customer not present mean?
Customer present refers to payments made while the customer is actively checking out. Customer not present refers to background subscription charges.
Will this trigger fire for payment links?
Yes. Payments made through funnels, websites, invoices, calendars, and payment links are supported.
Can I test this trigger before publishing?
Yes. Use Test Workflow to validate filters, branches, and payment values before publishing.