Glossary
Flow builder
A flow builder is the editor in which a payment business composes its routing: conditions on amount, currency, country of the payer, the IP and the card, scheme, BIN range, method and time window branch into route groups of terminals with priorities, weights and limits, with fallbacks when a branch has no terminal available. A flow is saved as a version, tested against sample payments and activated for a network or a merchant; the previous version stays for rollback.
What a flow contains
An entry per operation, deposit or payout; condition blocks that read the payment’s attributes; route groups at the ends of branches; limits that drop a terminal out when reached; a default branch for payments nothing else matched; and a decline outcome for payments the business does not want at all. Good flows are shallow: a few conditions that matter, not a tree nobody can read.
Versions and activation
Every change creates a version with its author and time; a version is activated at a moment and the journal records which version routed each payment, so a change in approval rate can be tied to a change in the flow. Rollback is activating the previous version.
On the platform
Tranzify’s flow builder offers conditions on amount, country of the payer, the IP and the card, scheme, BIN ranges and time windows, route groups with priority and weight, limits and restrictions, versions and activation per network; the journal names the flow version and the branch behind every routing decision.
Updated: 2026-11-08