The Process Cart endpoint processes an order automatically. Cleverbridge uses the customer's most recent payment details to process the order.
If the order cannot be processed automatically, the API returns a unique URL that can be sent to the customer to complete the transaction on the Cleverbridge-hosted website.

Implement the Process Cart API endpoint

Before you start

Make sure that:

• You can authenticate requests to the Cleverbridge REST API.
• You know the ProductId and quantity of each cart item.
• You have a supported customer identifier: LogonPurchaseId, CustomerReferenceId, or SubscriptionId.
• Your application can handle the response status and any returned completion URL.
• You have configured notifications if your system must synchronize purchase or subscription events.

Payment information and PCI compliance

Do not send payment information in the request. Cleverbridge uses stored information when available. Otherwise, the response provides a Cleverbridge-hosted URL where the customer can enter it securely.

Step 1: Identify the customer

Provide one identifier so that Cleverbridge can locate the customer and their stored payment information:

Step 2: Build the cart

See the API reference for the complete request schema and product-dependent fields.

Step 3: Choose the processing behavior

ProcessCartMode

If valid information is available but payment is declined, Cleverbridge creates the purchase and returns a URL where the customer can update their payment details or method.

FraudProtectionMode

Step 4: Submit the request

curl --request POST \
  --url 'https://rest.cleverbridge.com/cart/processcart' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --data '{
    "Cart": {
      "CartItems": [
        {
          "ProductId": 97771,
          "Quantity": 1
        }
      ],
      "DefaultLanguageId": "en",
      "LogonPurchaseId": 115000000
    },
    "ProcessCartMode": 0,
    "FraudProtectionMode": 1
  }'

For a client-managed subscription, include the subscription separately:

{
  "Cart": {
    "CartItems": [
      {
        "ProductId": 97771,
        "Quantity": 1
      }
    ],
    "DefaultLanguageId": "en"
  },
  "ProcessCartMode": 0,
  "FraudProtectionMode": 1,
  "Subscription": {
    "SubscriptionId": "S9073119"
  }
}

Step 5: Handle the response

Do not treat every HTTP 200 response as a completed payment. Evaluate the response status before fulfillment.

Optionally: Add custom x-parameters

Use x-parameters to pass custom customer, campaign, partner, tracking, or licensing data. Keys must begin with x-; the submitted values are included in notifications.

{
  "ExtraParameters": {
    "ExtraParameter": [
      {
        "Key": "x-vendor-subscription-id",
        "Value": "544920"
      }
    ]
  }
}

Use ExtraParameterMode for subscription products:

This setting affects subsequent billing events only for new subscriptions. For an existing subscription, use POST /subscription/updatesubscriptionparameters.