Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.hellgate.io/llms.txt

Use this file to discover all available pages before exploring further.

Commerce allows you to accept online payments directly from your website or application. There is no lock-in to any payment processor and the many flavors payments are integrated. You just have to implement your payment setup once. A payment setup with Commerce consists of a back-end connection to our API and a front-end setup to interact with your customers. The back-end API is described on our API reference. The front-end can vary depending on the channel and the payment method you want to use. For the sake of explanation, we will use the example of a web application. The same principles apply to mobile applications, but the implementation details may vary.

​
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.
  1. Request a payment on our API.
  2. Handle an action requirement on the front-end with our SDKs.
  3. Commerce will choose the processing setup based on the request and start the processing.
  4. You will receive a webhook notifications throughout the lifecycle of the payment.

​
Authentication / 3-D Secure

In case 3-D Secure is configured for your account, Commerce will automatically handle the process. The above steps will not change. Learn more about Authentication.