Created
Payment initiated
In progress
Completion confirmed
Payout initiated
Completed
Buyer initiates a transaction
A buyer starts the journey in your marketplace. Your application defines the order, participants, and expected completion conditions.
Marketplace creates a transaction
The intended TradeVelio API creates a shared record for the workflow, using a stable reference that your marketplace can recognize.
Payment workflow begins
Relevant payment events would be coordinated with an appropriately authorized provider. TradeVelio itself is not presented as the custodian of funds.
Transaction state is monitored
Events and milestone changes would update the transaction’s state. Exceptions should be visible rather than silently treated as completed.
Marketplace confirms completion
Your platform checks the agreed criteria and records a confirmation. Who may confirm, and under what conditions, must be explicitly defined.
Payout workflow begins
Confirmation may make the transaction eligible for the next payout step. An instruction to pay is distinct from a provider-confirmed payout outcome.
Webhooks notify the marketplace
Planned notifications would communicate relevant changes throughout the lifecycle. Your application can use those events to update its own experience.
Idempotency: make retries predictable.
A request may be retried when a connection fails or a response is delayed. An idempotent operation is designed so a repeated request for the same action does not create another business effect. Keys, scope, and retention rules would be specified in the future API contract.
Events: connect systems without guessing.
An event describes a meaningful change. A marketplace can react to it without assuming that every step finishes immediately. Consumers need to handle duplicates, delays, and ordering deliberately; “event-driven” alone does not guarantee delivery or exactly-once processing.