Payment Workflows
Payment Workflows in the XYB Console are prebuilt, configurable flows designed to automate and control the lifecycle of a payment from initiation through validation, creation, authorization, and final clearance.
These workflows allow you to:
Standardize payment logic across your platform
React dynamically to failures or alternate states
Integrate payment activity with other services like tasks, alerts, and ledger updates
What You Can Define
Within a payment workflow, you can visually orchestrate how the system handles different events and states. For example:
What happens when a payment is requested?
How should the system respond if validation fails?
When is a payment marked as authorized or cleared?
What happens when a payment is failed?
Each of these can be represented as a node in the workflow, giving you full control over execution logic.
Key Components
Start node: The entry point to the flow
Payment state nodes: Represent transitions like
REQUESTED,VALIDATED,CREATED,AUTHORIZED,FAILED, orCLEAREDConditional branches: Define what happens based on success or failure
End node: Marks the conclusion of a path
You can customize the logic between these nodes using platform events, variables, and service calls to enforce business rules.
Who Is It For?
Payment workflows are typically used by:
Ops teams, to define and adjust how payments behave
Product managers, to prototype and test payment logic
Compliance or risk teams, to introduce additional steps based on payment data
Last updated