Custom Triggers

Introduction

The functionality to create custom buttons and hyperlinks empowers Distributors and Sellers to provide users with additional information, such as their balance, credit limit, payment terms, or other relevant details. This enables customers to seamlessly manage and pay their invoices with greater ease.

By including a hyperlink in the Overview tab, users can be redirected to external resources for further insights into their payment status or to facilitate making a payment directly.

In this article:

• What do you need to use this feature?
• Custom Triggers options
• Enable Custom Navigation
• Configure Custom Navigation
• Button placement – Overview tab or Payment methods
• Inheritance through the chain
• Conditional display of Custom Triggers
• Possible scenarios of displaying Custom Triggers
• Role visibility

What do you need to use this feature?

To use Custom Triggers, the following is required:

• The Custom Navigation toggle enabled in Settings → Currency & Payments → Display & Navigation.
• Permissions to change the settings on the Display & Navigation tab.
• Visibility Settings selected (Direct Customers, Indirect Sellers, or both).
• Display Conditions configured (either Always show or Show when conditions are met).

Custom Triggers options

Custom Triggers supports two types of elements that can be configured independently or at the same time:

• Button – a clickable control with a custom label and target URL. A button can also be placed under the Customer’s Payment methods section (see Button placement).
• Hyperlink – a text link with a custom caption and target URL. A hyperlink is always displayed on the Invoices – Overview tab, below the button.
• Location of payments method Button - the button for payments method is by default visible in the Invoices - Overview tab, but Distributors and Sellers can set them up to be visible in Organization's details.

Both the label/caption and the URL are fully customizable so that the navigation elements match business needs. Typical use cases include linking to a third-party payment portal, a balance-inquiry page, a credit-limit page, or any other external resource relevant to the user.

Enable Custom Navigation

Open Settings and select Currency & Payments.

Open the Display & Navigation tab and turn on the Custom Navigation toggle.

Configure Custom Navigation

After Custom Navigation is enabled, fill in the configuration sections:

1. Under Visibility Settings, select who should see the trigger: On the Distributor level: Direct Customers, Indirect Sellers, or both. On Seller level: Direct Customers.
   
2. Under Display Conditions, select one of the following:
   
   • Always show – the trigger is shown to every matching user.
   • Show when conditions are met – the trigger is shown only when the selected conditions apply. 
3. Under Button Configuration, enter the button label and the target URL.
   
4. (Optional) Under Hyperlink Configuration, enter the hyperlink caption and the target URL.
   
5. Select Save to apply the configuration.
   

Button placement – Overview tab or Payment methods

By default, a payments method button is displayed in the Custom Triggers area of the Invoices – Overview tab. The Button placement setting lets the Distributors and Sellers to move the button to the Customer’s Payment methods section in Organization details, so that it sits next to the other payment-related settings.

This is useful when the button links to a Payment method such as an external payment portal, a card-payment gateway, or a balance portal — the button then appears in the same place where users already review or edit payment methods.

To move the button to the Payment methods section:

1. In the Button placement section, select the checkbox Display custom navigation under Payment Methods instead of Overview Tab.
2. Select the correct Visibility Settings for your level (see the note below).
3. Select Save to apply the configuration.

The correct Visibility Settings depend on the level at which the button is configured:

• Distributor level – select Indirect Sellers. The button is only opened from the Customer’s organization profile when a user acts on behalf of that Customer, so the configuration is inherited down the chain to the Sellers and reaches the Customers through them. Selecting Direct Customers at Distributor level for the Payment methods placement does not make sense, because that visibility only applies when a user acts directly on behalf of a Customer on the Distributor’s own platform.
• Seller level – select Direct Customers. The Seller is configuring the button for its own Customers, who will see it in their Payment methods section.

With the Payment methods placement enabled, a user acting on behalf of a Customer sees the button in Organization details → Payments → Payment method:

Inheritance through the chain

A configuration set by a Distributor is automatically inherited down the business chain to its Sellers and through them to the Customers. The inheritance follows the structure of the chain:

• Distributor → Seller → Customers (indirect chain)
• Distributor → Direct Customers (when the Distributor serves Customers directly)

This means a Distributor only needs to configure the button once at its own level — the same button will appear for the Customers of its Sellers as well, without any extra setup on the Seller side.

The inheritance is broken only when a Seller creates its own button configuration for its Customers. In that case the Seller’s configuration overrides the Distributor’s configuration on the Seller’s platform — the Seller’s own button (and its placement) is shown to the Seller’s Customers instead of the inherited one.

Conditional display of Custom Triggers

Conditional Display Controls determine when a configured trigger is actually shown in the UI. A Distributor or Seller can either show the trigger to every matching user (Always show) or limit visibility to specific conditions (Show when conditions are met).

When Show when conditions are met is selected, the trigger is displayed only if the configured flags on the Seller profile are set correctly. For example, the button can be configured to appear only for Sellers that have Enable Invoicing or Card Payment turned on in the reseller onboarding form.

Possible scenarios of displaying Custom Triggers

The following table summarizes the behavior based on the configuration chosen:

Role visibility

When a button is placed under Payment methods, it is visible to all user roles that can sign in on behalf of a Customer, with one exception: the Seller agent admin role cannot see the button and cannot open the Payment methods configuration page.

When a Seller agent admin tries to open the Payment methods configuration page — either by selecting the edit icon under Organization details or by opening the URL directly — the page does not open and a standard error message is displayed:

“Payment method settings are managed by your account administrator.”

Limitations and important information

• The Button placement option is configurable only at Distributor level. Sellers cannot move the button themselves; they can only add their own button, which overrides the inherited configuration on the Seller’s platform.
• Users with the Seller agent admin role cannot see the button under Payment methods and cannot open the Payment methods configuration page. This restriction cannot be overridden from the Platform UI.
• Specific display conditions (for example, Enable Invoicing or Card Payment) can only be applied at Seller level.

Summary

The Custom Triggers feature lets Distributor administrators add custom buttons and hyperlinks to the Platform so that Sellers and Customers can reach external payment portals, balance pages, or other relevant resources. The configuration is done under Settings → Currency & Payments → Display & Navigation → Custom Navigation. Buttons can be displayed on the Invoices – Overview tab or, for selected Payment methods, directly in the Customer’s Payment methods section in Organization details. Visibility Settings, Display Conditions, and inheritance from Distributor to Seller together control which users actually see the trigger and where.