Skip to main content

Card Transactions Flow

The Card Transactions Flow enables customization of the processing of card payments.

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.

Action: Skip 3-D Secure

This action allows you to continue a transaction without 3-D Secure.

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.

  • 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 Gr4vy 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