Composer (Workflow Engine)

SME review required: SME / Product review required before publication, confirm product descriptions and capabilities are current.

Composer is Spreedly's low-code/no-code (LC/NC) workflow builder that enables merchants and payment operations teams to configure, implement, and optimize complex payment routing logic without writing custom API code for each routing scenario. Through a visual interface, teams can design transaction workflows that define which gateway receives which transactions, how failures are handled, and how routing rules adapt to different transaction conditions.

Composer workflows support several routing models. Single gateway routing directs all transactions to one configured provider, useful for merchants establishing their first gateway relationship while building in the flexibility to expand later. Split volume routing distributes transaction volume between two gateways by configurable percentage, useful for A/B testing new providers or maintaining a secondary gateway relationship. Conditional routing rules apply logic-based conditions to routing decisions: routing all Euro transactions to a designated European gateway, sending all Amex transactions to the gateway with the lowest Amex rate, or directing transactions from a specific issuing country to a local provider with higher authorization rates in that market.

Composer also supports Recover strategies, automated workflows for handling declined transactions, including Decline Salvage sequences that retry failed transactions on alternative gateways, and retry logic for Soft Declines. When Advanced Vault is enabled, Composer workflows can incorporate Network Tokenization, automatically attempting transactions with a network token when one is available for the stored payment method.

The practical significance of Composer is the separation of routing strategy from code deployment. Payment operations teams can adjust routing logic, shifting volume between gateways, adding conditional rules, activating recovery strategies, through the Composer interface, without requiring engineering changes to the API integration. This makes payment optimization an operational capability rather than an engineering project.