Hard-coded payment logic
Payment rules embedded in checkout, portals or business applications become expensive to change and difficult to keep consistent.
Payments / Payment Flow
Turn business rules into the right payment experience.
Define how payment should work before routing or execution begins — from available payment options and installments to split and partial payment behavior.
Business Rules · Payment Options · Installments · Split & Partial Payments
Business contextPayment experience
ChannelCustomer portal
AccountOpen balance
PolicyBusiness rules
Payment FlowApply rulesOptions · installments · split · partial
CardInstallments available
Bank transferAvailable
Partial paymentAvailable
Why it matters
Payment experience is business logic.
When payment behavior lives inside channel code, every commercial change becomes an implementation project. Payment Flow makes that behavior explicit and reusable.
Without a payment flow layer
Too many choices
Showing every available payment option can create complexity instead of a better payment experience.
Rigid installment behavior
Installment availability often depends on business policy, card context and commercial rules that change over time.
Fragmented collection journeys
Split and partial payments are difficult to operate consistently when each channel implements its own logic.
With Zopio
Centralize payment rules
Define payment behavior once instead of distributing business logic across customer-facing systems.
Present the right options
Shape which payment choices are available for the transaction and customer context.
Control installment experiences
Apply installment policies consistently without rebuilding the surrounding payment journey.
Support flexible collections
Use split and partial payment behavior where the commercial journey requires more than a single full payment.
How it works
How a payment experience is shaped.
Payment Flow separates the business decision about what should be offered from the provider decision about where the payment should execute.
- 01Context
- 02Rules
- 03Options
- 04Experience
- 05Handoff
Understand the context
Use the transaction and business context that matters for the payment journey.
Apply business rules
Evaluate the policies that determine allowed payment behavior.
Assemble payment options
Build the set of eligible options, installments and payment structures.
Shape the experience
Present a payment journey aligned with the business decision rather than a generic checkout.
Hand off for execution
Pass the selected payment intent into orchestration and execution without coupling channel logic to providers.
Core capabilities
Shape payment behavior without rebuilding the channel.
The scope stays deliberately focused on the business-facing payment experience: rules, choices, installment behavior and flexible collection structures.
Business Rules
Express payment behavior as business policy rather than application-specific checkout code.
Payment Options
Control which payment choices are available within a given payment journey.
Installments
Shape installment availability and behavior as part of the payment experience.
Split & Partial Payments
Support payment journeys where the total amount is collected across more than one payment action.
Separation of concerns
Keep payment policy separate from provider logic.
Payment Flow owns how the business wants payment to happen. Payment Orchestration and Payment Execution handle where and how that intent is processed.
Business Systems · Commerce Surfaces · Customer Portals · Payment Orchestration · Payment Execution
Centralized policyKeep payment rules in one decision layer instead of duplicating them across channels.
Channel consistencyApply the same payment behavior across multiple customer-facing experiences.
Provider independenceShape the payment experience without exposing provider-specific logic to business applications.
Controlled changeChange payment behavior without rebuilding the full payment stack.
Common use cases
Use Payment Flow wherever commercial rules shape how customers pay.
Payment Flow can stand alone as a business-rules layer or sit at the start of the broader Zopio payment lifecycle.
B2B collection journeys
Shape account-based payment experiences around business rules, balances, installments and partial collection needs.
Installment-led commerce
Make installment behavior part of the commercial experience rather than a provider-specific implementation detail.
Split payment scenarios
Support journeys where one obligation is satisfied through multiple payment actions or payment options.
Cross-channel consistency
Keep payment behavior aligned across portals, commerce surfaces and other customer-facing systems.
Part of Zopio PaymentsShape → Decide → Execute → Verify
- 01Payment Flow
- 02Payment Orchestration
- 03Payment Execution
- 04Financial Operations
Secured by Payment Vault · Connected by Payment Connectivity
Modular by design
Start with what you need. Expand when you need more.
Use Payment Flow to centralize payment behavior today, then connect orchestration, execution and financial operations as your payment environment grows.
Talk to an expert