> ## 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.

# Create a billing session

## Sample Request for create Billing Session

```json theme={null}

{
    "returnUrl": "https://www.transactbridge.com",
    "quoteCurrCode": "INR",
    
    "items": [
        {
            "name": "Product Name 1 with very long name",
            "description": "Product Descriptoin with a very long desc <br> here is new line for this desc <br/> this is another line for testing puspose hope this works",
            "amount": 2000,
            "quantity": 1
        }
    ],
    "billTo": {
        "name": "XYZ",
        "postalCode": "110001",
        "state": "Delhi",
        "city": "CENTRAL DELHI",
        "country": "INDIA"
    },
    
    "email": "test@gmail.com"
}
```

### Parameter's Description

* **returnUrl**: The URL to which the customer will be redirected after completing the payment. This is mandatory for all different variants of checkout integration.
* **quoteCurrCode**: Fiat price of the product or service in the currency for which request needs to be initiated. **Quote currency and pay currency for the customer can be different for different jurisdictions.**
* **items**: An array of items being purchased, each with a name, description, amount, and quantity.
* **billTo** : An object containing billing Details of the customer for the invoice. Including name, postal code, state, city, and country(mandatory). **Depending on the billTo country local payment currency and other taxations are calculated.**
* **email**: The customer's email address for sending the invoice and payment confirmation.
* **meta**: An optional object for storing additional metadata related to the billing session. This can include any custom information that the merchant wants to associate with the session, such as order ID, customer ID, or any other relevant data. They will be passed in the webhook and query API as well.
* **discount**: An optional object for applying a discount to the one-time payment. This can include details such as the discount name and the discount amount. The discount will be applied to the total amount of the billing session, reducing the final payable amount for the customer.
* **dropIn**: An optional object for configuring the drop-in checkout experience. This can include settings such as the theme, layout, and other customization options for the checkout page. The drop-in configuration allows merchants to provide a seamless payment experience for their customers. **If this is set to be true then the response will contain token that can be used in the drop-in module. This can only be sent in the request if DropIn module has been enabled for the Partner Account**.