Cart is a feature that lets you allow customers to purchase multiple products in a single order.

The following subjects are covered in this article:

• Overview
• Implementing Cart With JSON
• Implementing Cart With the Cbitems Parameter
• Customer View
• Compatibility With Other Features
• Common Issues

Overview

Cart allows vendors to provide customers with a cohesive customer shopping experience. In a single transaction, a customer has the ability to purchase multiple products, or multiple quantity of a single product, from the same vendor, with ease. The customer also receives a single confirmation email with the details for each product.

There are two payment link formats that you can use for cart purchases. One uses a parameter to specify the item SKUs and quantities, while the other uses JavaScript Object Notation (JSON).

Benefits of Cart

Implementing ClickBank’s Cart functionality provides vendors with a host of benefits. These include:

• Ability for a customer to purchase multiple quantities of a single product, or multiple products within a single transaction
• Increase in average customer transaction value
• Smoother overall shopping experience, including a seamless integration with existing vendor storefronts
• Supports additional ClickBank functionality including product add-ons and coupons

Important Aspects of Cart

• Supports all payment methods and currency types – Customers can select their preferred payment method and currency, selected to process a single transaction covering multiple products.
• Supported across all product types – All product types can be combined seamlessly into a single product bundle, including digital and physical products. A cart order can include any number of digital items, physical items, and recurring items.
• Modifiable Quantity – You can specify the starting quantity for each item in a cart order.
• Mobile Friendly – Cart is compatible with mobile devices and tablets, delivering an elegant and functional experience across the devices your customers use to complete their purchase.
• Order Form Customization – Both Basic and Advanced order form customization is supported through the customer shopping journey, keeping the familiar custom branding across the full order flow.
• Affiliate Commissions – A single affiliate can receive a commission for a cart transaction. Affiliate commission percentages are processed according to the individual rules for each product included in the transaction.
• Refund Process – Refunds will be processed at the individual product level. This allows a customer to request a refund for one of the items within the transaction, while retaining the remainder of the item.

Implementing Cart With the Cbitems Parameter

You can implement cart by passing a special paylink. This paylink contains the SKUs of the desired products and their quantities in the cbitems parameter.

Paylink Structure

To create a cart order, you use a payment link with the following format:

http://vendornickname.pay.clickbank.net/?cbitems=sku.quantity_sku.quantity

The cbitems parameter indicates the items purchased and their quantities using one or more SKU-quantity pairs.

When the customer arrives at the order form, it displays the items and quantities. If you have the Editable Quantity feature enabled, the customer can edit the quantity of the items. See the Editable Quantity on the Order Form article for more information.

Code Example

The following paylink example takes a customer to the order form with one item A and two of item B.

http://vendornickname.pay.clickbank.net/?cbitems=A.1_B.2

Implementing Cart With JSON

You can implement cart using JSON. If you don't feel comfortable using JSON, you can use the cbitems parameter, or find a developer who can help you.

Paylink Structure

To create a cart order, you pass the cbcart parameter as part of the order flow. The cbcart parameter contains all the details required to present the customer with the proper set of items to be purchased on the order form.

The parameter can either be passed on the paylink from the vendor pitch page to the ClickBank order form, or used as the action of a post form that has a cbcart input.

The contents of the cbcart parameter will be in URL-encoded JavaScript Object Notation (JSON) Data Interchange Format.

The payment link needs to point to:

http://vendornickname.pay.clickbank.net/?cbcart={Cart details}

Unlike standard payment links, there is no SKU provided as the initial portion of the URL, because multiple SKUs are expected as part of the paylink cbcart parameter.
Additional parameters can be specified before or after the cbcart parameter, as per standard URL parsing structure.

Items Array

• sku – The SKU (item number) for the product to be purchased.
• qty – The quantity of the product provided in the SKU parameter to be purchased.

Additional Parameters

• editURL – Optional Parameter that provides a destination URL of the vendor’s choosing. That way, a location is provided for the customer to return in case they want to change, review or would like more information on their selected items.
  NOTE – The "editURL" must be located on the pitch domain. If an editURL is not provided or the URL provided is on a domain not matching the pitch domain, the user will not be presented with the link on the Order Summary page (or in the case that the skipSummary parameter is used, the link will not be presented on the Order Form page.)
• skipSummary – Optional parameter; If this is provided as true then the order summary page will be skipped. When the parameter is passed, the customer will immediately see the full order form page upon accessing the paylink.
• editQuantity – If the Editable Quantity feature is enabled and the parameter is passed as True, the customer will be able to edit the quantity, as well as remove items on the order form. Additionally, if this is passed as true, the order summary page will always be skipped. See the Editable Quantity on the Order Form article for more information.

Code Examples

Example Unencoded CBCart parameter (in tabbed format for ease in reading)

{      "items":[         {            "sku":"1",          "qty":1       },       {            "sku":"2",          "qty":2       }    ],    "editUrl": "http://www.exampleURL.com",    "skipSummary":true,     "editQuantity":true  }

Example Unencoded CBCart parameter (compact view)

{"items":[{"sku":"1","qty":1},{"sku":"2","qty":2}],"editUrl":"http://www.exampleURL.com","skipSummary":true,"editQuantity":true}

Example Full Paylink, URL Encoded

http://vendor.pay.clickbank.net/?cbcart=%7B%22 items%22%3A%5B%7B%22 sku%22%3A%221%22%2C%22 qty%22@3A1%7D%2C%7B%22 sku%22%3A%222%22%2C%22 qty%22%3A2%7D%5D%2C%22 editUrl%22%3A%22http%3A%2F%2F www.exampleURL.com%22%2C%22 skipSummary%22%3Atrue%2C%22 editQuantity%22%3Atrue%7D

Customer View

Order Summary Page

The summary page includes product images, product titles and product descriptions. The subtotal is also displayed.

The customer is then able to review, proceed to the order form or return to the vendor’s site. Note, as mentioned above, in order for the return URL to be displayed, the editURL must be specified within the cbcart parameter.

If skip summary is used, the customer will bypass the order summary page and only see the Order Form.

NOTE – Single Item Purchases: The new cbcart structure can be used with single item purchases to allow for consistent paylink coding. If a single item is passed in, the customer will be presented with the standard, single item, order form.

Order Form with Summary Skipped

 

Compatibility With Other Features

Instant Notifications

Instant Notifications version 6 includes line item level details. Please see the Instant Notification Service article for general information about Instant Notifications and how to set up an account to send and consume these notifications.

APIs

The Orders and Ticket APIs have been updated to support accessing information from multi-line transaction orders. For the following endpoints, a sku (item number) is provided to request a specific line item. A sku is required when making a call against a multi-line transaction purchase. If a sku is not provided, the endpoint will return an error status with a detailed error messaging that a sku is required to return the results of the API call. See the ClickBank APIs article for updated service descriptions.

PitchPlus Upsell Flows

Cart purchases can be used with the cbfid parameter to initiate PitchPlus upsell flows. Cart orders cannot be the destination of an upsell flow. However, PitchPlus upsell flow steps can sell multiple products. See the PitchPlus Upsell Flows article for more information.

Physical Products

Cart supports physical products.

If a physical product has shipping and handling charges, the shipping and handling amount is applied linearly with the quantity of products purchased.

Recurring Products

Cart supports recurring products.

Coupons

Coupons work with Cart. If a coupon can apply to more than one item in a cart basket, then the coupon is applied to the highest priced item. In the case that multiple of the applicable item were being purchased, the coupon is applied linearly to each quantity of that item.

Order Bump

One or more Order Bump products can be displayed on a Cart order form. Any product configured as a bump product for the first product in the cart is also displayed as a bump product for the cart order. See the Order Bump article for more information.

Common Issues

Some common error handling scenarios are covered below.

Scenario	Response
Paylink received with both a standard item and the cbcart parameter. For example: {sku}.{vendor}.pay.clickbank.net/?cbcart={cbcart param}	User will be redirected to the invalid paylink page.
Invalid JSON or JSON completely missing within the cbcart parameter.	User redirected to the invalid paylink (network abuse) page.
Paylink received with cbcart details containing a mix of valid and invalid items.	Order summary will be populated with the valid products and will not include the invalid products.
Paylink received with cbcart details that include at least one item that is in a non-approved state.	Order flow will be in test mode and purchase will be treated as a test purchase.
Paylink received with cbcart JSON that has a return URL that does not match with the pitch domain setup for the vendor account.	User will see the order summary page without the link to return to the vendor page.
Paylink received with a single sku multiple times as separate items.	The item will be displayed with a quantity matching the total quantity between the duplicate line items.