> ## Documentation Index
> Fetch the complete documentation index at: https://developer.transactbridge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

# Product-Based Payment Link

A **product-based payment link** allows merchants to collect payments for a specific product without building or maintaining their own website or payment integration.

This solution is particularly useful for **small businesses, freelancers, and merchants with limited technical knowledge**. Merchants can create a product in the TransactBridge Admin Panel, generate a payment link for that product, and share the link directly with customers.

Customers can use the payment link to view the product details and complete the payment.

## About Product-Based Payment Links

With a product-based payment link, the merchant does not need to:

* Build a website or mobile application.
* Integrate the TransactBridge payment APIs.
* Develop a custom checkout page.
* Implement payment collection logic.

Instead, the merchant can manage the product and generate its payment link directly from the **Admin Panel**.

The payment link is associated with a specific product and can be shared with customers through channels such as **WhatsApp, SMS, email, or other communication platforms**.

> **Note:** Currently, product-specific payment links can only be generated through the TransactBridge Admin Panel.

## How to Generate a Product-Based Payment Link

Follow the steps below to create a product and generate its payment link from the Admin Panel.

### Step 1: Navigate to Products

Log in to the **TransactBridge [Admin Panel](https://reseller.transactbridge.com)** and navigate to the **Products** tab.

### Step 2: Create a Product

1. Navigate to the **Items** tab.
2. Click the **Create** icon.
3. The **Create Product** form will open.
4. Enter the required product details, such as:

   * Product name
   * Product description
   * Product price
   * Discount, either as an **amount** or **percentage**
   * Other applicable product details
5. Click **Create**.

The product will be created and listed in the Admin Panel.

### Step 3: Generate the Payment Link

1. Click the **Product ID** of the product you created.
2. Navigate to the **Actions** tab.
3. Select **Product Pay URL**.
4. Copy the generated payment URL.

You can now share this payment link with your customers to collect payment for the product.

## Product Availability and Quantity

The quantity of a product that a customer can purchase depends on the **available inventory** configured for that product.

For example, if the product has an available inventory of 10 units, customers cannot purchase more than the available quantity.

> **Note:** Product availability and purchase quantity are controlled based on the inventory configured for the product.

## Business Use Cases

Product-based payment links are useful for merchants who want to start accepting online payments without investing in a custom website or technical integration.

### Small Businesses

A small business selling products through social media can create products in the TransactBridge Admin Panel and share the corresponding payment links with customers.

**Example:**
A home-based bakery receives an order through WhatsApp. The merchant creates or selects the product in the Admin Panel, generates the product payment link, and sends it to the customer. The customer opens the link and completes the payment.

### Freelancers and Independent Professionals

Freelancers can use product-based payment links to collect payments for predefined services.

**Example:**
A freelance designer offers a logo-design package for ₹5,000. Instead of creating a website or integrating a payment gateway, the freelancer can create the service as a product and share its payment link with the customer.

### Social Media Sellers

Merchants who sell products through platforms such as Instagram or WhatsApp can use payment links to convert customer inquiries into payments.

**Example:**
A customer sees a product on Instagram and contacts the merchant through direct message. The merchant can share the product payment link directly with the customer instead of asking the customer to visit a separate website.

### Offline Businesses

Businesses that interact with customers offline can also use product payment links to collect digital payments.

**Example:**
A merchant can generate a product payment link and share it with a customer through SMS or WhatsApp after taking an order over the phone.

### Merchants Without Technical Resources

This solution is suitable for merchants who do not have developers or technical resources to integrate payment APIs.

The merchant can manage products and payment links entirely from the Admin Panel.

## Session Status

The payment link creates a payment session for the customer. The session status changes based on the outcome of the payment attempts.

| Payment Scenario       | Session Status | Description                                                                                                                                                                                                                                                                 |
| ---------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payment is successful  | `CLOSED`       | The session is closed after a successful transaction.                                                                                                                                                                                                                       |
| Transaction fails      | `STARTED`      | The session remains active because multiple transaction attempts can be made against a single session.                                                                                                                                                                      |
| Transaction is pending | `STARTED`      | The session remains in a pending state while the transaction is being processed.                                                                                                                                                                                            |
| No payment is made     | `STARTED`      | The session remains in the `STARTED` state for 24 hours.                                                                                                                                                                                                                    |
| Session expires        | `EXPIRED`      | If no payment is made against a session, the session remains in the **`STARTED`** state for **24 hours**. After 24 hours, the session is automatically marked as **`EXPIRED`**. Once the session has expired, no further payment attempts can be made against that session. |

<Note>
  To understand the difference between a **session** and a **transaction**, refer to [Session vs. Transaction](/one-time-payments/get-started-with-one-time-payments/overview#session-vs-transaction).
</Note>

## Webhook

TransactBridge sends a webhook event to the configured **partner URL** whenever the session status changes.

The session can have any of the following statuses:

* `CREATED`
* `STARTED`
* `CLOSED`
* `EXPIRED`
* `FAILED`

The webhook allows the merchant to receive real-time updates about the payment session and take appropriate action on their side.

For more information, refer to the [Webhook](/one-time-payments/manage-your-payments/webhook) documentation.
