Briqpay - The checkout flow

The Checkout Flow

1. Customer navigates to the checkout page in WooCommerce. If Briqpay is the selected (or default) payment method, an initialize session request is sent to Briqpay.
2. Briqpay responds with a session id that is used for further communication with Briqpay and a html snippet that is rendered on the checkout page. The html snippet includes the embedded Briqpay checkout.
3. When the customer clicks the Complete payment button in Briqpay, a JavaScript event is triggered by Briqpay.
4. When the customer identify herself in the Briqpay checkout, a JS event is triggered. The Briqpay for WooCommerce plugin is listening for this event, updates the customer in WooCommerce and recalculates the cart. If anything changes (like the selected shipping method), an update checkout request is sent to Briqpay.
5. When the customer clicks the Complete payment button in Briqpay checkout, a JavaScript event is triggered by Briqpay.
6. The standard WooCommerce checkout form is submitted by the Briqpay plugin with customer data that we have in this step and a pending order is created in WooCommerce. This order has not yet been paid for and you should not change the status to Processing/Completed manually.
7. If the order creation went well, the Briqpay plugin responds with a true message in the JavaScript event (if something went wrong during the order creation process the Briqpay plugin will respond with a false message in the JavaScript event and Briqpay will not finalize the purchase. Instead an error notice will be displayed for the customer). 
8. Provided that the Briqpay plugin respond with a true message, Briqpay then finalizes the purchase in their system.
9. Briqpay redirects the customer to the confirmation URL.
10. The Briqpay plugin runs the WooCommerce function payment_complete() that changes the WooCommerce order status to either Processing or Completed.
11. The order received page is rendered and displayed for the customer.