Use cases
Although many payment orchestration platforms don’t differentiate between use-cases, we do. We built the system around a couple of use-cases. These use-cases bundle specific behavior and make it available on specific endpoints. This not only makes it easier to understand and implement, but also reduces the complexity (of payloads for instance) and reduces fricition and potential sources of error.One-off Payments
Process one-off payments with Commerce.
Initial Recurring
Set up recurring payments with Commerce.
Initial Unscheduled
Prepare for unscheduled payments with Commerce.
Processing
The overall process of accepting online payments with Commerce is always the same.- Request a payment on our API.
- Handle an action requirement on the front-end with our SDKs.
- Commerce will choose the processing setup based on the request and start the processing.
- You will receive a webhook notifications throughout the lifecycle of the payment.