# Payment Received Trigger FAQ

#### **Will this trigger include subsequent subscription payments as well?**  <a href="#will-this-trigger-include-subsequent-subscription-payments-as-well" id="will-this-trigger-include-subsequent-subscription-payments-as-well"></a>

Yes, the trigger will fire whenever a payment is received from the end customer directly on an order form submission and when the subscription is charged in the background.

#### **How can I achieve the trigger for successful subsequent subscription transactions?** <a href="#how-can-i-achieve-the-trigger-for-successful-subsequent-subscription-transactions" id="how-can-i-achieve-the-trigger-for-successful-subsequent-subscription-transactions"></a>

Since the subscriptions can be created in a funnel or website, we can create a trigger for Payment Received and apply the following filters for achieving the use case. The source type is Funnel/Website. The transaction type is "Customer not present/subscription transaction."

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48294599591/original/OrCqP9hHx0Hn9hTZVHZu36bkcArxNdWgPg.png?1682520656" alt=""><figcaption></figcaption></figure>

The payment status filter can filter successful or failed payments per the use case.

#### **What does the Customer present/first transaction mean and the Customer not present/subscription transaction?** <a href="#what-does-the-customer-present-first-transaction-mean-and-the-customer-not-present-subscription-tran" id="what-does-the-customer-present-first-transaction-mean-and-the-customer-not-present-subscription-tran"></a>

We are categorizing the transaction type into two categories

* Customer present /first transaction - This includes the transactions where the end customer is on-session and making the Payment. This consists of all one-time purchases and the first order placement for a subscription product.
* Customer not present / subscription transaction - This includes the transaction types which run in the background after a subscription has already been created. For example, if a customer purchases a recurring product with a 14-day trial period. The transaction is done while purchasing the recurring product ($0 transaction in this case) would fall into the Customer present/first transaction. After 14 days, when the trial period is over, and you charge $100 for the recurring product, the $100 transaction would fall into the Customer not present/subscription transaction category.

#### **Will failed payments also be captured in this trigger?**  <a href="#will-failed-payments-also-be-captured-in-this-trigger" id="will-failed-payments-also-be-captured-in-this-trigger"></a>

Yes, by default, without any filters, the trigger runs upon successful and failed payment attempts. For specific use cases around success/failed payments only, we can apply the "Transaction status" filter and set it to either success/failed as per the use case.

<figure><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48294601007/original/F5rh94OpAzMdtC93c23wQ4pYrasZGL7irw.png?1682520974" alt=""><figcaption></figcaption></figure>

#### **I have configured the trigger and selected a specific product in the filters. Does this mean that the trigger will fire off when that product is sold anywhere?** <a href="#i-have-configured-the-trigger-and-selected-a-specific-product-in-the-filters.-does-this-mean-that-th" id="i-have-configured-the-trigger-and-selected-a-specific-product-in-the-filters.-does-this-mean-that-th"></a>

If you have configured the trigger and set the filter for a specific product, it will fire off only when that product is sold in funnels/website/invoices. Using the transaction status filter, we can define whether the trigger should work when the purchase is successful or the purchase is a failure.

#### **What is the sub-source filter?** <a href="#what-is-the-sub-source-filter" id="what-is-the-sub-source-filter"></a>

When you select a source like funnels/websites/invoices, they can have sub-sources, like a payment from the funnel can be coming either via a one-step order form, a two-step order form, or an upsell. You can use these sub-source filters to define the Payment's origin.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.getgymini.com/gymini/features/features-overview/workflows/workflow-triggers/e-commerce-triggers/payment-received-workflow-trigger/payment-received-trigger-faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.