Standard Ecommerce Architecture

Standard ecommerce overview

In a standard ecommerce order:

  • The customer uses a computer (A) to visit the merchant website (B).
  • The customer adds an item or items to her shopping cart at (B)
  • The customer then checks out, either entering billing info at the merchant website (B) or at a hosted payment page at the Payment Service Provider (C)
  • The Payment Service Provider (C) transfers funds to the Merchant (B)

Bidco Adds a Second Order Channel

The standard ecommerce architecture, as above, is maintained.

The Bidco System adds a second order channel as follows:

Enhanced ecommerce with Bidco

System Components:

  1. Customer's carry smartphones (iPhone, Android, Windows Phone) with a Bidco-Powered app. Customers can use the app to scan Bidco QR Codes that initiate a purchase. Customers are prompted to sign up and supply billing info when they install the app.
  2. The Bidco server decodes QR and other trigger scans, and also houses customer accounts & the payment info they supplied when they signed up. It also maintains the server-based shopping cart for each customer, enabling users to complete scan products now, and complete checkout at a later date.
  3. The Bidco server acts as a transaction router, mapping requests from customer scans to the correct merchant website. The server also serves as a translation layer, normalizing requests across a wide variety of ecommerce platforms and PSPs.
  4. Merchant ecommerce platform may be any of several popular ecommerce systems, or may be a bespoke creation. The ecommerce platform is typically modified to work with Bidco via a bespoke integration with the Merchant Integration API.
  5. Payment Service Provider (PSP) typically offer their own API for programatic processing of payments. The Bidco Integration Server (C) can speak directly to the the APIs of a number of popular PSPs.

In a Bidco order:

  1. The customer (A) scans a Bidco trigger with their phone
  2. A request is sent to the merchant website (D) for product info, image, pricing, shipping/tax, and total and returned to customer (A) for purchase decision.
  3. If the customer agrees to purchase, the Bidco Server (B) looks up the customer billing information, and provides it to the Bidco Integration Server (C)
  4. The Bidco Integration Server (C) provides the sku and other order details to the Merchant Ecommerce Platform (D)
  5. The Bidco Integration Server (C) provides the customer billing information to either the Merchant Ecommerce Platform (D) or the Payment Service Provider (E) as appropriate for the checkout strategy.
  6. Upon receiving a transaction success from the PSP (E), a normal order is inserted into the Merchant Ecommerce Platform (D), and the Bidco Integration Server (C) sends notification back up the chain.
  7. The Bidco System Server (B) is notified of a new order, and the customer record is updated.
  8. The Customer app (A) is notified of the transaction success, and the UI and order history is updated accordingly.