> For the complete documentation index, see [llms.txt](https://limechatai.gitbook.io/limechat-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limechatai.gitbook.io/limechat-product-guide/whatsapp-marketing/flows/action-nodes/custom-checkout-on-chat.md).

# Custom Checkout On Chat

Action Node · Conversational Checkout

### What It Does

This node creates a checkout experience directly within the chat conversation by sending product details, pricing, shipping charges, discounts, and payment information to the customer.

It enables users to initiate and complete purchases without leaving WhatsApp or the chat interface, making it ideal for conversational commerce workflows.

After initiating the checkout flow, the node returns payment-related identifiers for downstream tracking and automation.

***

### Example

A customer selects products through a WhatsApp shopping flow.

The workflow sends a checkout message containing:

* Product details
* Pricing
* Shipping charges
* Discount information
* Payment CTA

The customer can immediately proceed with payment directly from the conversation.

***

## When to Use This Node

Use this node when:

1. You want customers to complete purchases directly within chat
2. You are building conversational commerce experiences
3. You want to recover abandoned carts with quick payment flows
4. You need instant checkout after product recommendations
5. You are running COD-to-prepaid conversion campaigns

***

## Requirements

 Before configuring this node:

* Ensure product information is mapped correctly
* Product IDs, names, and prices should remain aligned
* Pricing calculations should be validated before initiating checkout

***

## Supported Events

This node supports:

1. All Events

***

## Setting It Up

### Inputs

| Input               | Type          | Required | Description                                               |
| ------------------- | ------------- | -------- | --------------------------------------------------------- |
| Body Text           | Text          | Yes      | Message shown to the customer along with checkout details |
| Product IDs         | List (Text)   | Yes      | Unique identifiers for each product                       |
| Product Names       | List (Text)   | Yes      | Names of products being purchased                         |
| Product Prices      | List (Number) | Yes      | Prices of each product                                    |
| Shipping Price      | Number        | Yes      | Delivery charges applied to the order                     |
| Subtotal Price      | Number        | Yes      | Total product value before tax, discount, and shipping    |
| Tax Percentage      | Number        | Yes      | Tax rate applied to the order                             |
| Discount Percentage | Number        | Yes      | Discount applied to the order                             |

***

## Input Field Details

### Body Text

Checkout message displayed to the customer.

Supports dynamic variables.

#### Example

Your order is almost ready! Complete your payment now to confirm purchase and enjoy faster delivery.

***

### Product IDs

Unique identifiers for each product included in the checkout.

Supports multiple values.

#### Example

* PROD\_1023
* PROD\_4589

***

### Product Names

Names of the products being purchased.

Must remain aligned with Product IDs and Product Prices.

#### Example

* Running Shoes
* Wireless Earbuds

***

### Product Prices

Price for each product.

Must align with Product IDs and Product Names.

#### Example

* 2499
* 1999

***

### Shipping Price

Delivery charges added to the order.

#### Example

* 50
* 100

***

### Subtotal Price

Combined product value before:

* Tax
* Discounts
* Shipping

#### Example

* 4498

***

### Tax Percentage

Tax percentage applied to the order.

#### Example

* 5
* 18

***

### Discount Percentage

Discount percentage applied during checkout.

#### Example

* 10
* 15

***

## Special Behavior

* Product IDs, names, and prices must match in sequence and length
* Supports dynamic checkout creation directly inside the conversation
* Initiates the payment flow but does not confirm payment completion
* Payment status should be tracked separately through events or webhooks

***

## Outputs

| Output          | Type    | Description                                                            |
| --------------- | ------- | ---------------------------------------------------------------------- |
| successful      | Boolean | Indicates whether the checkout/payment flow was successfully initiated |
| payment\_id     | Text    | Unique identifier of the payment session                               |
| transaction\_id | Text    | Transaction reference ID associated with the payment                   |

***

## Output Behavior

| Output Value       | Meaning                              | Recommended Next Step                   |
| ------------------ | ------------------------------------ | --------------------------------------- |
| successful = true  | Checkout flow initiated successfully | Wait for payment confirmation           |
| successful = false | Failed to initiate checkout          | Retry checkout or trigger fallback flow |

***

## What Happens After It Runs

Once executed:

* The checkout experience is sent directly within the chat
* Customers can initiate payment immediately
* Payment-related identifiers are generated
* The workflow can continue toward:
  * Payment tracking
  * Order confirmation
  * CRM tagging
  * Fulfillment workflows
  * Reminder notifications

***

## Best Practices

 Ensure all product lists remain correctly aligned.

 Validate pricing calculations before triggering checkout.

 Use concise and action-oriented Body Text.

 Combine with:

* Payment reminder workflows
* Abandoned cart recovery
* COD-to-prepaid campaigns
* Order confirmation automation
* Payment success tracking

 Keep discounts and pricing transparent to improve conversion rates.

***

## Key Reminders

1. Product IDs, names, and prices must align correctly
2. This node initiates checkout but does not confirm successful payment
3. Payment completion should be tracked separately
4. Works across all workflow events
5. Supports conversational commerce and in-chat checkout experiences
6. Incorrect product mapping can result in inaccurate checkout details
7. Typically followed by payment status handling workflows or webhooks