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

# Payments

> Take payments in the portal with Stripe, refund payments, manage security deposits, send receipts and post orders to Track.

Portals take payment for offers, damage waivers, required fees and security deposits. Stripe is the payment provider.

## Stripe

Payments go to your own Stripe account, minus Conduit's fee and Stripe's processing fees.

### Connect Stripe

Needs **Manage Portal Payments**.

1. Go to **Portals > Settings > Stripe**
2. Click **Log in to Stripe** for an existing account, or **Create a Stripe account**
3. Finish Stripe's steps within 15 minutes, signed in to Conduit as the same user. The link works once
4. Back on the Stripe page, check that **Charges enabled** says **Yes**. If the account shows **Action needed**, finish the requirements in Stripe and click **Refresh status**

* The status only updates when you click **Refresh status**
* **Settlement currency** is the Stripe account's default currency. It can't be changed in Conduit
* Connecting the first account moves every offer to that currency and keeps the amounts

> [!WARNING]
>
> Connect Stripe before you add a priced damage waiver, security deposit or required fee. Check-in steps keep the currency they were saved in, and a step in a different currency from your Stripe account fails when the guest pays.

### Bank verification

**Bank verification** (off by default) asks the card's bank to verify payments with 3D Secure. Some banks add a confirmation step at checkout.

### More than one Stripe account

1. Click **Connect another account**. The first account is the **Default**
2. Under **Payment routing**, click **Add routing rule** and pick **Listings** or **Listing groups** and a **Stripe account**
3. Click **Save payment routing**

* Rules run in **Priority** order and the first match wins. Stays that match no rule use the default account
* Every account has to use the same currency
* An offer's **Payment account**, shown once you have 2 or more accounts, sends that offer to one account. **Follow payment routing** is the default. An offer on a different account than the rest of the cart has to be paid on its own
* Disconnecting the default account doesn't pick a new one. Pick it under **Payment routing**

## Transactions

Needs **View Portal Transactions**. Go to **Portals > Transactions**.

The **Payments** tab shows revenue, conversion, a checkout funnel and **Transaction history** for the last 7, 30 or 90 days. **Export range** downloads a CSV.

* Filter by **Items**, **Status**, **Listings** or **Check-in** date, or search by guest, booking or listing
* Statuses: **Paid**, **Pending**, **Failed** (with the reason) and **Refunded**. The **Status** filter calls Paid **Succeeded**
* Test link payments aren't listed

### Refund a payment

Needs **Manage Portal Payments**.

1. Open the row's **⋮** menu and click **Refund payment**
2. Enter the **Amount**, up to what's left to refund
3. Click the **Refund** button, which shows the amount

* Offers, damage waivers and required fees can be refunded, in full or in part, one refund at a time
* The refund includes Conduit's fee and goes back to the original payment method
* \$0 payments and test link payments can't be refunded, and collected deposits can't be refunded from **Transactions**

## Security deposits

The **Security deposits** tab opens on **Outstanding** deposits. Pick **All statuses** or one status to see the rest: **Held**, **Needs attention**, **Status not checked**, **Scheduled**, **Collected**, **Released**, **Canceled** and **Expired**. Open a deposit to see what happens next and its history.

| Action | What it does |
| - | - |
| **Collect from deposit** | Collects up to the held amount, with a reason the guest doesn't see. Stripe allows one collection per hold, and the rest is released |
| **Release hold** | Ends the hold without moving money. Can't be undone |
| **Renew hold now** | Places a new hold, then cancels the old one. The guest can see two pending charges |
| **Change card** | **Enter card details**, or **Allow guest to update in portal** |

Deposit actions need **Manage Portal Payments**.

* The hold is placed 1 to 3 days before check-in, as set on the [deposit step](https://docs.conduit.ai/portals/step-settings.md#security-deposit), or right away when check-in is sooner
* Conduit renews a hold automatically when it would expire before the release date
* The hold is released automatically at checkout plus the step's **Release the hold** delay
* Collected deposits aren't counted in net revenue

## Receipts

* **⋮ > View receipt** on a transaction opens the receipt PDF. It needs **Manage Portal Payments**. A stay with 2 or more payments gets **Whole stay** and **This payment**
* **Download** saves the PDF. **Send** opens the guest's conversation with the PDF attached to the reply
* Guests find their receipts on the Stay page under **Payments > Receipts**, with **Download PDF**

**Email a receipt after each payment**, in [Defaults](https://docs.conduit.ai/portals/defaults.md#payments), emails guests a receipt shortly after each paid offer, damage waiver or required fee.

* Deposits, test links and Airbnb, Booking.com and Expedia relay addresses don't get one
* The email comes from your business name and links to the guest's receipts. No PDF is attached
* Receipts and the reply-to address use the template's current logo and contact details, or the brand kit's when the template has none

## Track folio

Track accounts get a **Track folio** group under **Defaults > Payments**:

1. Turn on **Post paid orders**
2. Pick a **Payment type** and a **Default fee**
3. Click **Save**

* Each paid offer order, including approved paid requests, posts to the booking's folio as one fee line per item plus one payment
* An offer can use its own fee from the **Track folio** card on the offer. Otherwise it uses the default fee
* Damage waivers and required fees don't post

**Portals > Transactions** shows each order's folio status:

| Status | Meaning |
| - | - |
| **Posting to Track** | Posting now |
| **Track failed** | The post failed, for example because the reservation isn't linked to a Track account or has no folio yet. Hover for the reason, or click **Retry Track post** |
| **Reverse in Track** | The order was refunded after it posted. Reverse it in Track |
| **Not in Track** | The order was refunded before it reached Track, or folio posting is off for that Track account |

Refunds aren't reversed in Track automatically.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.