How Checkout works
iCliGo Checkout allow you to accepts payments using an iCliGo-hosted payment page and a low-code integration.
Checkout lifecycle
The basic lifecycle for a customer’s Checkout experience looks like this:
- When customers are ready to complete their purchase, your application creates a new Checkout Session.
- The Checkout Session provides a URL that redirects customers to a iCliGo-hosted payment page.
- Customers enter their payment details on the payment page and complete the transaction authorization process.
- After the customer finish the transaction authorization process, the events webhook URL supplied on the Checkout Session creation is called with an event payload of type checkout.session.authorized, checkout.session.rejected, checkout.session.paid, or checkout.session.unpaid.
- After the order is fulfilled, your application must finalize the Checkout Session in order to capture the transaction value. After the system capture the transaction value an checkout.session.completed event is sent to the events webhook URL supplied on the Checkout Session creation.
Implementation steps
1. Create the Checkout Session
The Checkout Session is a programmatic representation of what your customers see on the iCliGo-hosted payment page. After creating a Checkout Session, redirect your customers to the Session’s URL to complete the purchase. When customers complete their purchase, you can fulfill their orders by configuring webhooks on Checkout Session events. This code snippet from the quickstart guide is an example of how to create a Checkout Session in your application.
2. Redirect customers to iCliGo-hosted payment page
....
3. Handle order fulfillment
.... checkout.session.authorized or checkout.session.rejected event
4. Finalize the Checkout Session
....
3. Handle order complete (optional)
.... checkout.session.completed event