Create flow rule

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

The flow name. This can be one of the following.

• checkout - Applies during checkout to determine what payment options are shown.
• card-transaction - Applies when processing a card transaction.
• non-card-transaction - Applies when processing a gift card only transaction, or a redirect transaction using the decline-early action.
• redirect-transaction - Applies when processing any other transaction.

The flow action.

Description of the flow rule.

One or more conditions that apply for this rule. Each condition needs to match for this rule to go into effect.

Defines the outcome of a rule in a flow where the result is a boolean.

The type of this resource. Is always rule.

The unique Gr4vy ID for this rule.

The unique ID for a merchant account.

Description of the flow rule.

The name of the Flow.

Action for the given rule. Actions can only be used in flows that support them.

• The checkout flow only supports the select-payment-options action.
• The card-transaction supports the route-transaction, skip-3ds, and decline-early actions.
• The non-card-transaction flow only supports the decline-early action.
• The redirect-transaction flow only supports the route-transaction action.

One or more conditions that apply for this rule. Each condition needs to match for this rule to go into effect.

Defines the outcome of a rule in a flow where the result is a list of dictionaries that define the payment service, instrument and transformation to be used to process a transaction.

The position of the rule in the flow.

The date and time when this buyer was created in our system.

The date and time when this buyer was last updated in our system.