Briqpay - The checkout flow
The checkout flow used for this plugin can result in Pending orders existing in WooCommerce, where the payment has not been finalized in Briqpay. This is part of the general WooCommerce checkout flow, and it does not implicate that something is wrong.
The Checkout Flow
- 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.
- 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.
- 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.
- 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.
- Provided that the Briqpay plugin respond with a true message, Briqpay then finalizes the purchase in their system.
- Briqpay redirects the customer to the confirmation URL.
- The Briqpay plugin runs the WooCommerce function payment_complete() that changes the WooCommerce order status to either Processing or Completed.
- The order received page is rendered and displayed for the customer.