A shopper who scans a Bidco trigger generates a call to the Bidco System Server, which is routed by the Bidco Integration Server using a combination of settings called a “Strategy”.

There are three order-processing strategies:

  1. Integrated Payment
  2. Hosted Payment
  3. Hosted Payment with Order ID

The Integrated Payment strategy is when the merchant’s ecommerce platform handles securing payment from the PSP. In this strategy, Bidco only talks to the merchant’s website, and never talks to the payment gateway.

The two Hosted Payment strategies are so named because checkout capability is provided by an external webpage hosted by the PSP. This requires Bidco's Integration Server to contact the payment gateway directly to handle payment.

Full details about each strategy are outlined below.

Integrated Payment Strategy

Bidco Integrated Payment Strategy

In the diagram above, note that the Bidco Integration Server never speaks directly to the Payment Gateway. Bidco passes all order and payment information directly to the Ecommerce Platform which handles the payment transaction. The Integrated Payment strategy is the most straight-forward, and is the easiest to configure, of the three payment strategies. However, the Integrated Payment Strategy is sometimes not an option, due to enhanced security requirements, or due to inability of a platform to support this method due to API constraints or corporate policy. It is not uncommon for a merchant to want to avoid handling credit card information in their website.

While the full order pathway is shown here for illustrative purposes, note that the API covers only the interactions between Bidco and external resources. These are the only interactions a merchant developer needs to implement.

Hosted Payment Strategy

Bidco Hosted Payment Strategy

In the diagram above, we can see that the Ecommerce Platform never directly handles credit card information. In this scenario, Bidco replaces the hosted payment page with a direct API call to the payment provider, at (17). The Payment Gateway accepts payment information, and returns success/failure info, with transaction id. At (19), the transaction id and results are passed into the Ecommerce Platform, along with the order information, and the notification is pushed back to the customer, at (22).

A Hosted Payment Strategy is used when integrated payments are not possible due to policy restrictions at the payment gateway, when the payment gateway platform plugin uses a “hosted payment” page, or when regulatory or security concerns make passing credit card info directly to the platform verboten.

While the full order pathway is shown here for illustrative purposes, note that the API covers only the interactions between Bidco and external resources. These are the only interactions a merchant developer needs to implement.

Hosted Payment with Order Id Strategy

Bidco Hosted Payment with Order Id Strategy

The Hosted Payment With Order Id Strategy differs from the preceding Hosted Payment Strategy because an Order ID must exist prior to processing payment at the Payment Gateway. This is usually due to a requirement at the payment gateway that an order identifier, or other order metadata, be associated with a payment for security reasons.

The order process starts almost the same as an Integrated Payment, passing item and shipping information to the Ecommerce Platform at (17), but differs in that payment information is omitted. The obtained order identifier is then passed to the Payment Gateway (19), along with payment information. Once a transaction id and result are obtained from the Gateway, this information is then transmitted back to the Ecommerce Platform (21), and the order is updated with the results.

While the full order pathway is shown here for illustrative purposes, note that the API covers only the interactions between Bidco and external resources. These are the only interactions a merchant developer needs to implement.