​
Action: Decline

This action allows you to decline transactions before they are routed to one of your connections.

​
Action: Route to connection

This action allows you to route transactions to a subset of your connections. A transaction will be processed sequentially with the defined outcome connections until it is successful. If a rule is matched and there are no active connections or all connections fail to process the request the transaction will be declined.

​
Retries

Transactions may be retried with the next connections in the sequence under certain conditions.

​
Failures

Attempts that fail due to technical reasons will be automatically retried with the next connection in the sequence.

​
Retriable declines

If the option “Yes, retry 3 times” is set, transactions that are declined with retriable decline codes will be automatically retried with the next connections in the sequence. Retries will stop after a success or after 3 more declines. Note that if an attempt fails due to technical reasons, that connection will not be counted towards the retries.

Currently, this feature is only available with the following connections, any decline response from any other connection will be assumed to be a hard decline and will not be retried:

  • Adyen
  • Braintree
  • Chase Orbital

​
Action: 3-D Secure

This action allows you to control when 3-D Secure is required for transactions.

​
Conditions

You can add the following conditions:

  • Amount: This enables filtering based on the amount for the transaction. Each rule defines a single currency for which it applies. You can specify a minimum amount, maximum amount, or a range for the amount.

  • Anti-fraud Decision: This enables filtering based on a risk decision received from an anti-fraud provider as an inclusive or exclusive list of decisions. Note that Error (unable to get decision) represents a state where a decision is unobtainable. For example, due to a network timeout or server error.

  • Browser language: This enables filtering based on a buyer’s browser language.

  • Country: This enables filtering based on the customer’s country as an inclusive or exclusive list of countries.

  • Currency: This enables filtering based on the transaction currency as an inclusive or exclusive list of currencies.

  • Metadata: This enables filtering based on key/value strings from an object passed to the API. This currently only supports matching/not matching string values. For example you could pass {"foo": "bar"} and create a condition based on the value of the foo key.

  • Card Source: This enables filtering based on the input used for the card, for example; Apple Pay, Google Pay, tokenized, or one off card details.

  • Card Scheme: This enables filtering based on the scheme of the card.

  • BIN Range: This enables filtering on up to the first eight digits of the card, for example; 4242-4545 or 12345678-12345678.

Rule Validation

  • You may only have one amount or currency condition per rule
  • You may only have one country condition per rule
  • You may only have one card source condition per rule
  • You may only have one card scheme condition per rule
  • You may only have one BIN range condition per rule