# Actions Actions are tasks that execute when an event with a configured rule or bind occurs. This topic describes all action types and how to configure them. To configure event based email notifications, see [Email notifications](/docs/automations/email-notifications). ## Terms - **Event:** An event is a preconfigured occurrence. For example, when a customer new customer is created, the 'customer created' event is triggered. - Rules and binds: There are two methods of creating automations in Rebilly: - **Rules**: Can be configured to stop subsequent rules in the event list from being executed. - **Binds:** Can be configured to always execute, regardless of rule-based events. Use this automation type when you want to ensure an automation always executes when an event occurs. - **Ruleset:** Each event maintains a list of automations that are to be executed under specified conditions when the event occurs. These lists of automations are called rulesets. Rulesets are executed in the order they are listed on the event. - **Draft rulesets:** Provide a means of testing, and comparing changes with the active ruleset before publishing. - **Actions:** Tasks that execute when an event with a configured rule or bind occurs. ## Abandon scheduled payments Abandons scheduled payments for an order that exceeds the configured delinquency period. For information on delinquency periods and how to configure them, see [Manage delinquency periods](/docs/data-tables/manage-delinquency-periods). ### Associated events This action is available for the [Order delinquency reached](/docs/automations/event-types#order-delinquency-reached) event. ### Create an 'Abandon scheduled payments' action details summary Create a rule or bind that includes an 'Abandon scheduled payments' action This process creates a rule or bind that is added to the ruleset of the [Order delinquency reached](/docs/automations/event-types#order-delinquency-reached) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Billing events**, then select **Order delinquency reached**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select **Abandon scheduled payments**. / This action will abandon scheduled payments for an order that exceeds the configured delinquency period. To configure the delinquency period, see [Manage delinquency periods](/docs/data-tables/manage-delinquency-periods). 8. At the bottom of the page, press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes an 'Abandon scheduled payments' action This process creates a draft ruleset for the [Order delinquency reached](/docs/automations/event-types#order-delinquency-reached) event. The draft ruleset includes a rule or bind for an 'Abandon scheduled payments' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Billing events**, then select **Order delinquency reached**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select **Abandon scheduled payments**. / This action will abandon scheduled payments for an order that exceeds the configured delinquency period. To configure the delinquency period, see [Manage delinquency periods](/docs/data-tables/manage-delinquency-periods). 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Adjust ready to pay Controls which payment methods are displayed when a customer is ready to make a payment. Use the filters to control which payment methods are displayed or the order in which they are displayed, for customer segments based on tags, geography, and custom fields. ### Associated events This action is available for the [Ready to pay requested](/docs/automations/event-types#ready-to-pay-requested) event. ### Create an 'Adjust ready to pay' action details summary Create a rule or bind that includes an 'Adjust ready to pay' action This process creates a rule or bind that is added to the ruleset of the [Ready to pay requested](/docs/automations/event-types#ready-to-pay-requested) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events**, then select **Ready to pay requested**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select **Adjust ready to pay**. 8. Based on your active payment gateways, add payment methods and drag items to set the display order. 9. Optionally, to prioritize payment methods that are associated with a customer's active payment instruments, select the **Prioritize active payment instruments** checkbox. 10. At the point of sale, these methods are displayed on top of the list of available payment methods. 11. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes an 'Adjust ready to pay' action This process creates a draft ruleset for the [Ready to pay requested](/docs/automations/event-types#ready-to-pay-requested) event. The ruleset includes a rule or bind for an 'Adjust ready to pay' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events**, then select **Ready to pay requested**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select **Adjust ready to pay**. 11. Based on your active payment gateways, add payment methods and drag items to set the display order. 12. Optionally, to prioritize payment methods that are associated with a customer's active payment instruments, select the **Prioritize active payment instruments** checkbox. At the point of sale, these methods are displayed on top of the list of available payment methods. 13. Press **Save rule** or **Save bind**. 14. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Adjust ready to payout Controls which payment methods are displayed when a customer requests a payout. Use the filters to control which payment methods are displayed or the order in which they are displayed, for customer segments based on tags, geography, and custom fields. To configure how a gateway manages payout requests, set the ready to payout instruction in gateway account settings. For more information, see the [configure how the gateway manages payout requests](/docs/settings/set-up-a-gateway#optionally,-to-configure-how-the-gateway-manages-payout-requests) step when setting up a gateway account. ### Associated events This action is available for the [Ready to payout requested](/docs/automations/event-types#ready-to-pay-out-requested) event. ### Create an 'Adjust ready to payout' action details summary Create a rule or bind that includes an 'Adjust ready to payout' action This process creates a rule or bind that is added to the ruleset of the [Ready to payout requested](/docs/automations/event-types#ready-to-pay-out-requested) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events**, then press **Ready to payout requested** 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select **Adjust ready to payout**. 8. Based on your active payment gateways, add payment methods and drag items to set the display order. 9. Optionally, to prioritize payment methods that are associated with a customer's active payment instruments, select the **Prioritize active payment instruments** checkbox. At the point of pay out, these methods are displayed on top of the list of available payment methods. 10. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes an 'Adjust ready to payout' action This process creates a draft ruleset for the [Ready to payout requested](/docs/automations/event-types#ready-to-pay-out-requested) event. The ruleset includes a rule or bind for an 'Adjust ready to payout' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events**, then press **Ready to payout requested**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select **Adjust ready to payout**. 11. Based on your active payment gateways, add payment methods and drag items to set the display order. 12. Optionally, to prioritize payment methods that are associated with a customer's active payment instruments, select the **Prioritize active payment instruments** checkbox. At the point of pay out, these methods are displayed on top of the list of available payment methods. 13. Press **Save rule** or **Save bind**. 14. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Cancel scheduled payments Cancels all scheduled payments and void outstanding invoices related to a canceled subscription. ### Associated events This action is available for the [Subscription canceled](/docs/automations/event-types#subscription-canceled) event. ### Create a 'Cancel scheduled payments' action details summary Create a rule or bind that includes a 'Cancel scheduled payments' action This process creates a rule or bind that is added to the ruleset of the [Subscription canceled](/docs/automations/event-types#subscription-canceled) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Billing events**, then select **Subscription canceled**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select the **Cancel scheduled payments** action. 8. Optionally, to exclude invoices with services periods that have already started, select the checkbox. 9. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Cancel scheduled payments' action This process creates a draft ruleset for the [Subscription canceled](/docs/automations/event-types#subscription-canceled) event. The ruleset includes a rule or bind for a 'Cancel scheduled payments' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Billing events**, then select **Subscription canceled**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select the **Cancel scheduled payments** action. 11. Optionally, to exclude invoices with services periods that have already started, select the checkbox. 12. Press **Save rule** or **Save bind**. 13. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Churn subscription Ends a subscription when a renewal invoice payment is canceled. ### Associated events This action is available for the [Renewal invoice payment canceled](/docs/automations/event-types#renewal-invoice-payment-canceled) event. ### Create a 'Churn subscription' action details summary Create a rule or bind that includes a 'Churn subscription' action This process creates a rule or bind that is added to the ruleset of the [Renewal invoice payment canceled](/docs/automations/event-types#renewal-invoice-payment-canceled) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Billing events**, then select **Renewal invoice payment canceled**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select the **Churn subscription** action. 8. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Churn subscription' action This process creates a draft ruleset for the [Renewal invoice payment canceled](/docs/automations/event-types#renewal-invoice-payment-canceled). The ruleset includes a rule or bind for a 'Churn subscription' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Billing events**, then select **Renewal invoice payment canceled**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select the **Churn subscription** action. 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Display other choices Displays various choices at the purchase screen, based on the customer's language. ### Associated events This action is available for the [Gateway account requested](/docs/automations/event-types#gateway-account-requested) event. ### Create a 'Display other choices' action details summary Create a rule or bind that includes a 'Display other choices' action This process creates a rule or bind that is added to the ruleset of the [Gateway account requested](/docs/automations/event-types#gateway-account-requested) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events**, then select **Gateway account requested**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select the **Display other choices** action. 8. In the **HTML content** field, enter a message. 9. Optionally, to display additional choices based on the user's detected language: 1. Press **Add language**, the select a language and press **Add language**. 2. In the **HTML content** field, press the language name, then enter a message. 10. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Display other choices' action This process creates a draft ruleset for the [Gateway account requested](/docs/automations/event-types#gateway-account-requested). The ruleset includes a rule or bind for a 'Display other choices' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events**, then select **Gateway account requested**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select the **Display other choices** action. 11. In the **HTML content** field, enter a message. 12. Optionally, to display additional choices based on the user's detected language: 1. Press **Add language**, the select a language and press **Add language**. 2. In the **HTML content** field, press the language name, then enter a message. 13. Press **Save rule** or **Save bind**. 14. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Decline a transaction Declines a transaction and stops it from being processed. A common use case for this action is to limit the maximum amount in a transaction, where it is not processed if the amount is greater than a set value. In this case, the action stops large transactions that may incur additional fees, or avoids transactions amounts that are too small to process. ### Associated events This action is available for the [Transaction process requested](/docs/automations/event-types#transaction-process-requested) event. ### Create a 'Decline a transaction' action details summary Create a rule or bind that includes a 'Decline a transaction' action This process creates a rule or bind that is added to the ruleset of the [Transaction process requested](/docs/automations/event-types#transaction-process-requested) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events**, then press **Transaction process requested**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Specify conditions on when to decline a transactionTo use the decline a transaction action, you must specify conditions that determine when the action is executed. Example: Decline a transaction if the amount is greater than $100 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select **Transaction > amount**. 3. In the next field, select a **greater or equal to**. 4. In the next field, enter `100.01`. 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select **Decline a transaction**. 8. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Decline a transaction' action This process creates a draft ruleset for the [Transaction process requested](/docs/automations/event-types#transaction-process-requested). The ruleset includes a rule or bind for a 'Decline a transaction' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events**, then select **Transaction process requested**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Specify conditions on when to decline a transactionTo use the decline a transaction action, you must specify conditions that determine when the action is executed. Example: Decline a transaction if the amount is greater than $100 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select **Transaction > amount**. 3. In the next field, select a **greater or equal to**. 4. In the next field, enter `100.01`. 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select **Decline a transaction**. 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Guess payment card expiration Instructs Rebilly to guess the new expiration date of an expired payment card. This action makes up to 3 attempts to guess the new expiration date. For each guess, the action attempts a $1 authorization. On a successful authorization, the customer's payment card is updated to use that expiration date and the $1 authorization is voided. ### Associated events This action is available for the [Payment card expired](/docs/automations/event-types#payment-card-expired) event. ### Create a 'Guess payment card expiration' action details summary Create a rule or bind that includes a 'Guess payment card expiration' action This process creates a rule or bind that is added to the ruleset of the [Payment card expired](/docs/automations/event-types#payment-card-expired) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Billing events**, then select **Payment card expired**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select **Payment card expired**. 8. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Guess payment card expiration' action This process creates a draft ruleset for the [Payment card expired](/docs/automations/event-types#payment-card-expired). The ruleset includes a rule or bind for a 'Guess payment card expiration' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Billing events**, then select **Payment card expired**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select **Payment card expired**. 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Perform Experian check Performs an identity check using the Rebilly [Experian integration](/docs/app-store/experian-integration). ### Associated events This action is available for the [Transaction process requested](/docs/automations/event-types#transaction-process-requested) event. ### Create a 'Perform Experian check' action details summary Create a rule or bind that includes a 'Perform Experian check' action This process creates a rule or bind that is added to the ruleset of the [Transaction process requested](/docs/automations/event-types#transaction-process-requested) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events**, then select **Transaction process requested**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select **Perform Experian check**. 8. In the **Experian credential hash** field, select an Experian credentials hash value. For more information, see [Experian integration](/docs/app-store/experian-integration). 9. In the **Identity matches**, **Identity mismatches**, and **Result unknown** dropdowns, select tags to apply based on the Experian check result. To create tags, see [Create a tag](/docs/settings/tags#create-a-tag). 10. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Perform Experian check' action This process creates a draft ruleset for the [Transaction process requested](/docs/automations/event-types#transaction-process-requested). The ruleset includes a rule or bind for a 'Perform Experian check' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events**, then select **Transaction process requested**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select **Perform Experian check**. 11. In the **Experian credential hash** field, select an Experian credentials hash value. For more information, see [Experian integration](/docs/app-store/experian-integration). 12. In the **Identity matches**, **Identity mismatches**, and **Result unknown** dropdowns, select tags to apply based on the Experian check result. To create tags, see [Create a tag](/docs/settings/tags#create-a-tag). 13. Press **Save rule** or **Save bind**. 14. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Pick gateway account Dynamically routes transactions between payment gateways, based on real-time data and selected parameters. When a customer first attempts a transaction, a gateway account is requested. Rebilly can assign a gateway account based on gateway account weight or gateway acquirer weight. The weight specifies priority. To configure payment routing you must have more than one gateway account connected to Rebilly. ### Associated events This action is available for the [Gateway account requested](/docs/automations/event-types#gateway-account-requested) event. ### Create a 'Pick gateway account' action To create a 'Pick gateway account' action, see [Set up gateway routing](/docs/settings/gateway-routing). ## Request KYC Displays a Know Your Customer (KYC) form to the customer. The KYC form requests documentation that is used to verify the customer's identity. ### Associated events This action is available for the [Gateway account requested](/docs/automations/event-types#gateway-account-requested) event. ### Create a 'Request KYC' action To create a request KYC action, see [Create an automated KYC document request](/docs/kyc-and-aml/kyc#create-an-automated-kyc-document-request) ## Schedule payment Schedules a payment for a renewed subscription. ### Associated events This action is available for the [Renewal invoice issued](/docs/automations/event-types#renewal-invoice-issued) event. ### Create a 'Schedule payment' action details summary Create a rule or bind that includes a 'Schedule payment' action This process creates a rule or bind that is added to the ruleset of the [Renewal invoice issued](/docs/automations/event-types#renewal-invoice-issued) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Billing events**, then press **Renewal invoice issued**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then press **Schedule payment**. 8. In the **Schedule payment** dropdown, select and define a payment schedule. 9. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Schedule payment' action This process creates a draft ruleset for the [Renewal invoice issued](/docs/automations/event-types#renewal-invoice-issued). The ruleset includes a rule or bind for a 'Schedule payment' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Billing events**, then press **Renewal invoice issued**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Schedule payment** dropdown, select and define a payment schedule. 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Schedule invoice retry Schedules multiple payment retries for when a payment for a subscription fails. Retries can be scheduled by: second, minute, hour, day, month, or year. The payment amount can be adjusted on each retry — making the payment partial, or applying a discount. When a final retry attempt fails, this action can be set to cancel the subscription and the abandon invoice. ### Associated events This action is available for the [Renewal invoice payment declined](/docs/automations/event-types#renewal-invoice-payment-declined) event. ### Create a 'Schedule invoice retry' action details summary Create a rule or bind that includes a 'Schedule invoice retry' action This process creates a rule or bind for the [Renewal invoice payment declined](/docs/automations/event-types#renewal-invoice-payment-declined) event that includes a 'Schedule invoice retry' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Billing events**, then select **Renewal invoice payment declined**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. Configure the 'Schedule invoice retry' action 1. In the **Actions** section, press **Add action**, then select the **Schedule invoice retry** action. 2. In the **Retry attempts** section, press **Add attempt**. Retries are relative to the previous attempt. For example, to retry the payment 1 hour after the previous attempt, enter '1' in the input field and select **Hours**. 3. Select from one of the following retry options: Retry after a certain amount of time Select this option to retry the payment after a certain amount of time. 1. In the **Schedule type** section, select **Retry after a certain amount of time**. 2. Specify the amount of time to wait before the retry attempt. Retry on a specific date Select this option to retry the payment on a specific date. 1. In the **Schedule type** section, select **Retry on a specific date**. 2. Specify the date, and optionally the time, of the retry attempt. Retry on a specific day Select this option to retry the payment on a specific day. 1. In the **Schedule type** section, select **Retry on a specific day**. 2. Specify the day, and optionally the time, of the retry attempt. Retry immediately Select this option to retry the payment immediately. 1. In the **Schedule type** section, select **Retry immediately**. Retry intelligently Select this option to retry the payment based on historical BIN approval rates during a specific period of time. 1. In the **Schedule type** section, select **Retry on a specific day**. 2. Specify the time period that the retry attempt must occur in. 4. In the **Payment adjustment** section, select one of the following options: - **Full amount**: Select this option to retry the full amount of the invoice. - **Partial amount**: Select this option to retry a partial amount of the invoice. 1. Select **Fixed** to specify a fixed amount, or select **Percentage** to specify a percentage of the invoice amount. 2. Enter the amount. 3. To specify actions to take when a partial payment is approved, select one of the following: - **Do nothing**: Select this option to not take any action. - **Discount the remaining amount due**: Select this option to discount the amount paid from the remaining amount due. 5. Optionally, to try to collect payment using the customer's backup payment instruments, select the **Try backup payment instruments** checkbox. 6. To ensure that the recurring payment does not occur within the retry schedule, in the **After each attempt** section, select the **Push renewal time forward** checkbox. 7. To accommodate the scenario where all retry attempts fail, in the **After the last failed attempt** section, select one or both the **Cancel subscription** and **Abandon invoice** checkboxes. 8. To override a retry that is in process, in the **Override existing retry** section, select the **Override existing retry** checkbox. 8. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Schedule invoice retry' action This process creates a draft ruleset that includes a rule or bind for a 'Schedule invoice retry' action and is associated with the [Renewal invoice payment declined](/docs/automations/event-types#renewal-invoice-payment-declined) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Billing events**, then select **Renewal invoice payment declined**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. Configure the 'Schedule invoice retry' action 1. In the **Actions** section, press **Add action**, then select the **Schedule invoice retry** action. 2. In the **Retry attempts** section, press **Add attempt**. Retries are relative to the previous attempt. For example, to retry the payment 1 hour after the previous attempt, enter '1' in the input field and select **Hours**. 3. Select from one of the following retry options: Retry after a certain amount of time Select this option to retry the payment after a certain amount of time. 1. In the **Schedule type** section, select **Retry after a certain amount of time**. 2. Specify the amount of time to wait before the retry attempt. Retry on a specific date Select this option to retry the payment on a specific date. 1. In the **Schedule type** section, select **Retry on a specific date**. 2. Specify the date, and optionally the time, of the retry attempt. Retry on a specific day Select this option to retry the payment on a specific day. 1. In the **Schedule type** section, select **Retry on a specific day**. 2. Specify the day, and optionally the time, of the retry attempt. Retry immediately Select this option to retry the payment immediately. 1. In the **Schedule type** section, select **Retry immediately**. Retry intelligently Select this option to retry the payment based on historical BIN approval rates during a specific period of time. 1. In the **Schedule type** section, select **Retry on a specific day**. 2. Specify the time period that the retry attempt must occur in. 4. In the **Payment adjustment** section, select one of the following options: - **Full amount**: Select this option to retry the full amount of the invoice. - **Partial amount**: Select this option to retry a partial amount of the invoice. 1. Select **Fixed** to specify a fixed amount, or select **Percentage** to specify a percentage of the invoice amount. 2. Enter the amount. 3. To specify actions to take when a partial payment is approved, select one of the following: - **Do nothing**: Select this option to not take any action. - **Discount the remaining amount due**: Select this option to discount the amount paid from the remaining amount due. 5. Optionally, to try to collect payment using the customer's backup payment instruments, select the **Try backup payment instruments** checkbox. 6. To ensure that the recurring payment does not occur within the retry schedule, in the **After each attempt** section, select the **Push renewal time forward** checkbox. 7. To accommodate the scenario where all retry attempts fail, in the **After the last failed attempt** section, select one or both the **Cancel subscription** and **Abandon invoice** checkboxes. 8. To override a retry that is in process, in the **Override existing retry** section, select the **Override existing retry** checkbox. 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Show descriptor disclaimer Displays a disclaimer message at the point of sale. Use this message to display important information to the customer before they complete a purchase. ### Associated events This action is available for the [Gateway account requested](/docs/automations/event-types#gateway-account-requested) event. ### Create a 'Show descriptor disclaimer' action details summary Create a rule or bind that includes a 'Show descriptor disclaimer' action This process creates a rule or bind that is added to the ruleset of the [Gateway account requested](/docs/automations/event-types#gateway-account-requested) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events** then press **Gateway account requested**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select the **Show descriptor disclaimer** action. 8. Specify the disclaimer text, button text, and return link text. 9. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes a 'Show descriptor disclaimer' action This process creates a draft ruleset for the [Gateway account requested](/docs/automations/event-types#gateway-account-requested). The ruleset includes a rule or bind for a 'Show descriptor disclaimer' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events** then press **Gateway account requested**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select the **Show descriptor disclaimer** action. 11. Specify the disclaimer text, button text, and return link text. 12. Press **Save rule** or **Save bind**. 13. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**. ## Stop subscriptions Cancels active subscriptions based on transaction outcome. This action cancels both active subscriptions and renewals immediately after the event is executed. ### Associated events This action is available for the [Transaction processed](/docs/automations/event-types#transaction-processed) event. ### Create a 'Stop subscriptions' action details summary Create a rule or bind that includes a 'Stop subscriptions' action This process creates a rule or bind that is added to the ruleset of the [Transaction processed](/docs/automations/event-types#transaction-processed) event. 1. In the left navigation bar, press . 2. In the **Rules engine** section, press **Rules engine**. 3. Press **Core events**, then press **Transaction processed**. 4. Press **Rule set**. 5. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 6. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 7. In the **Actions** section, press **Add action**, then select the **Stop subscriptions** action. 8. Press **Save rule** or **Save bind**. details summary Create a draft ruleset that includes 'Stop subscriptions' action This process creates a draft ruleset for the [Transaction processed](/docs/automations/event-types#transaction-processed). The ruleset includes a rule or bind for a 'Stop subscriptions' action. 1. In the left navigation bar, press . 2. In the **Rules engine** section, **Rules engine**. 3. Press **Core events**, then press **Transaction processed**. 4. Press **Draft rulesets**, then press **Create draft ruleset**. 5. Enter a name and description for the draft ruleset. 6. Optionally, if you have existing rules on the event, and want to replace or edit them, select the **Copy current ruleset** checkbox. 7. Press **Save ruleset**. 8. Select from the following: - Create an automation that can stop all subsequent rules in the event list from being processed 1. In the top left of the page, press **Rules**. 2. Press **Create rule**. 3. In the **Rule name** field, enter a name for your rule. 4. In the **Labels** field, enter a value and press enter. Use labels to categorize and filter your rules and binds. 5. Optionally, to specify that when this rule occurs, the rules engine stops subsequent rules in the event list from being processed, select the **Stop further processing** checkbox. - Create an automation that always executes regardless of rule based events 1. In the top left of the page, press **Binds**. 2. Press **Create bind**. 3. In the **Bind name** field, enter a name for your bind. 9. Optionally, specify conditions for when the action must trigger 1. In the **Conditions** section, clear the **No conditions** checkbox. 2. In the **Select filter** dropdown, select a filter. 3. In the next field, select a condition. - To use data that is shared by other rules, or to compare against a list of data: select **is in list** or any other list filter type, then in the next field select the related list. For more information, see [Create a value list](/docs/automations/create-a-value-list). - To ensure that a specific field is empty, or not empty: select **is empty** or any other empty filter type. For more information, see [Empty criteria](/docs/automations/create-a-value-list#empty-conditions). 4. In the next field, enter or select values. 5. Press **Add filter**. 10. In the **Actions** section, press **Add action**, then select the **Stop subscriptions** action. 11. Press **Save rule** or **Save bind**. 12. Optionally, to publish your ruleset from draft to live: 1. In the right of the page, press , and select **Publish**. If you have existing rules or binds on the event, the differences are displayed. 2. Press **Publish**. If you have existing rules or binds on the event, the differences are displayed. 3. Press **Publish**.