Merchant decline rule

  Last updated: 


  This document is regarding a rule that can be activated on your Payment Pages.
Click here to learn more about rules.

  This rule is only supported by acquirers and payment methods that support security code checks.

When active, the STR-1 rule will automatically cancel transactions (update the settle status to 3) when the security code entered by the customer does not match the value held on the bank’s records.

A “Merchant Declined” message will be displayed to your customers on the Payment Pages when they enter an incorrect security code.

If activated in the MyST Rule Manager, the rule will also be enabled for payments processed using the Virtual Terminal, where a message of “Transaction Failed” will be displayed.

  If you intend to implement the merchant decline rule on a site reference where redirect and/or notification rules are already active, you should review the additional information provided below and update your rules as required.

Contact our Support Team if you require further assistance.


For merchants with existing rules

When a transaction is cancelled by an update transaction response rule (e.g. Merchant Decline), the error code may remain in status “0” (Ok). This would indicate that the payment was authorised by the acquiring bank, but later cancelled by Trust Payments. Therefore, you may need to update any active rules to take this possible outcome into account. To prevent a rule from being triggered on a merchant decline, remove the settle status “3” (Cancelled) from existing conditions on the affected site reference(s).

Note: When creating new conditions using the MyST Rule Manager, we will automatically deselect settle status “3” when you select error code of “0”, by default.

Was this article helpful?
0 out of 0 found this helpful