Action management

  Unfortunately, the product documented here is currently only available in English.

  This feature is available to merchants using our TRU Connect gateway.

This page explains how to manage Actions that form part of a Rule configured in the Rule Manager.

portal-rca-action-en.png

Remember: Trust Payments will perform an Action when all criteria of a Condition have been met.


  Required user roles

Admin, Developer

  Conditions and Actions can only be managed by the users that created them.


  How to access

Select your site from the “Sites” page and click the “Rule Manager” icon.
Then select the relevant Action type from the drop-down box and click “Go”.

 

View Actions

Actions created on your Portal user account can be managed by clicking the “Manage actions” tab above the table.

myst-manageactions-3009-01-en.png

This tab will list any Actions configured by your Portal account (if you have no Actions configured, it will prompt you to create your first).

  You can only view and manage Actions that you have created. Actions created by other Portal users are not displayed.

 


 

Viewing further details

myst-manageactions-3009-02-en.png

Actions are listed in a table with   icons to the left of each one. Clicking the   icon will cause the Action to expand in order to display its properties. When finished, you can click the   icon to collapse the Action, hiding the properties from view.

Clicking the   icon in the header row expands all Actions at once. Subsequently clicking the   icon in the header row will collapse all Actions at once, returning the table to its original state.

 


 

Modifying Actions

To modify the properties of an Action, click the Action name in the table. You will be presented with a page that allows you to modify the Action.

myst-manageactions-3009-01-en.png

  You can only modify Actions your Portal user account has created.

 


 

Deleting Actions

Using the checkboxes to the right of each Action, you can select Actions for deletion.

myst-manageactions-3009-04-en.png

When you have selected the Actions you would like to delete, press the “Delete” button. You will be shown a confirmation prompt before deleting an Action(s). You can only delete Actions that are not part of an existing Rule.

 


 

"IN USE" Actions

Actions that are part of an existing Rule are highlighted with the words “IN USE” in the “Delete” column. In order to delete these Actions, you must first delete the Rules that are using the Actions in question.

myst-manageactions-3009-04-en.png

 

When modifying an Action that is being used by an active Rule, a yellow warning is shown at the top of the page. This lists the number of Rules that will be affected by the changes made, and their associated Trust Payments sitereference(s).

myst-manageactions-3009-03-en.png

 


 

Action types

URL notifications

URL notification Actions are requests sent from Trust Payments to a pre-defined URL.
These notifications contain information about requests processed on your Trust Payments account.

e.g. For successful transactions, send a URL notification that includes the delivery address to your server.

  Learn more

Payment pages customer email

This Action is used to send an email to the customer’s billing email address following a Payment Pages transaction, when the associated Condition(s) has been met.

e.g. For successful transactions, send an email confirmation to the customer's billing email address.

  Learn more

Payment pages merchant email

This Action is used to send an email to yourself and/or members of your organisation following a Payment Pages transaction, when the associated Condition(s) has been met.

e.g. For successful transactions over £600, send an email confirmation to orders@companyname.com.

  Learn more

Payment pages redirect

This Action is used to redirect the customer’s browser from the Payment Pages following a transaction, when the associated Condition(s) has been met. The customer’s browser bypasses Trust Payments’s default response page and is redirected to the URL specified in the Action.

e.g. For successful transactions, redirect the customer’s browser to your website.

  Learn more

Payment pages required fields

This Action is used to designate fields as required on the Payment Pages when the associated Condition(s) has been met.

e.g. For Mastercard transactions, you could specify the billing name as required.

  Learn more

Update response Action

This Action is used to automatically update the status of a request after it has been processed by the acquirer

  Learn more

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request