Callback Functions
Last updated
Last updated
Glopal Checkout offers callback support (synchronous webhooks) that enables your system to respond at crucial points during the checkout process. The platform will pause for your backend to supply a response, modifying the related action's behavior accordingly.
On receiving network error, 5xx HTTP response or timeout (no response in 5 seconds), Glopal will retry the callback request up to 3 times. Most callbacks have optional response. In case of a bad or no response, Glopal will resume delivering checkout experience. Because of their synchronous nature, it is critical for a good buyer experience to ensure fast and reliable response.
To activate Checkout Callbacks, please provide the URL(s) of your backend that should receive callbacks to your Glopal account manager. For details on the expected request body and potential responses, consult the related documentation provided below.
To authenticate requests from Glopal, you can choose to setup Basic HTTP Authentication for the Endpoint URL or include a shared secret in query parameters.
Callback is triggered at the last stage of the checkout, before starting the payment action. Use this callback to confirm items are available for purchase.
When integrating this callback, keep in mind that buyers may still opt not to complete the payment, effectively canceling the purchase. If you decide to reserve inventory at this stage, rendering it unavailable to other buyers, make sure to establish an appropriate time limit before the reservation is released.
Use this callback to specify custom confirmation page message (eg. your order number) or custom . Other common uses is draft order creation (inventory reservation), clearing cart on the localized store or server-side marketing analytics.