Checkout Page Use Cases
General Usage Scenario
- The customer selects a product existing on your end (e.g., in your online catalog or application) and clicks the Buy button.
- You redirect the customer to the checkout page via a checkout link. This link allows the customer to purchase the product selected. Each product uses an individual link. You can add additional parameters to the link to transfer the quantity/currency of the product or to activate a discount, etc.
- On the checkout page, the customer must complete the steps required for the purchase. The customer:
- Manages the contents of their order (changes the quantity of the product selected, returns to your end and adds one more product, applies special offers, etc.)
- Fills in their personal data.
- Selects one of the payment methods.
- Confirms their consent to the sales terms and conditions and to the processing of their personal data.
- Clicks the Continue button.
- We process the actions that the customer makes (order creation):
- We create an order. The status of this order is not paid. The order also has an additional status: not delivered.
- We send you a webhook. It notifies you about the order.created event (example).
- We redirect the customer to the order payment page.
- The customer pays for the order (if the online payment method has been selected) or receives the instructions on how to pay for the order offline. If necessary, the customer can change the payment method.
- We process the actions that the customer makes (successful payment):
- We send you a webhook. It notifies you about the payment.succeeded event (example).
- We send a successful order payment email, an email with receipt / with closing documents (if required for the payment method selected) to the customer.
- We initiate the fulfillment of the customer's order (electronic product delivery):
- We get the license information for the product. E.g., we request it from your web service or take it from the license pool, etc. It all depends on the method that was set for the product.
Additional Usage Scenarios
Error or Payment Issues
If the customer does not pay for their order within a specified time, we send them a reminder email (optional). If the order remains unpaid for 90 days, we automatically delete the order and its status changes to deleted.
If the customer makes a payment, but an error occurs (e.g., the customer entered their payment data incorrectly):
- We send you a webhook. It notifies about the payment.failed event.
- The customer can try to pay for the order again or choose a different payment method.