> ## Documentation Index > Fetch the complete documentation index at: https://docs.gr4vy.com/llms.txt > Use this file to discover all available pages before exploring further. # Flow > Control payment options presented at checkout, and the flow of card and non-card payments all the way through to the payment service. Flow enables customization of customer experiences throughout the transaction lifecycle. By creating rules with conditions, specific customers can be targeted and/or transactions to dynamically change the outcome. This feature can be interacted with via the API or the dashboard. Flow dashboard ## Concepts ### Flows A flow represents one stage of the customer journey, for example, the checkout experience. Flow gives control to dynamically change each of these flows via actions. ### Actions Each flow may have one or more associated actions, for example, when processing a transaction, a transaction can be declined or routed to a specific connection. For each action, what happens under specific circumstances can be controlled by creating rules. ### Rules A rule represents a set of conditions and an outcome. If, at evaluation time, all the conditions for the rule are met, the outcome is used to alter the customer experience. An example of a rule would be **If the transaction amount is between $10 & $50, then only show the card payment option at checkout**. Each rule is evaluated from top to bottom; the first matched rule is used to change the outcome.