> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/payments/how-vendor-checkout-works.md). # How vendor checkout works This page explains what your vendors experience after they receive a payment link. Understanding the checkout flow helps you answer vendor questions and troubleshoot any issues. *** ## The checkout experience, step by step ### 1. Vendor clicks the payment link The vendor opens the link from their email and lands on a **secure checkout page** hosted by Vendor Space. The page displays: * Your **event name** * The vendor's **company name** * The **booth type** and its price * Any **add-on products** included with the link * The **total amount** due ### 2. Vendor reviews and customizes their order If you included optional add-ons, the vendor can select or deselect them on this page. The total updates in real time as they make changes. ### 3. Vendor clicks "Pay" After reviewing their order, the vendor clicks the **Pay** button and is redirected to **Stripe Checkout**, a secure payment page powered by Stripe. Here they enter their card details and complete the transaction. ### 4. Payment confirmation Once the payment goes through: * The vendor sees a **confirmation page** thanking them for their purchase. * A **confirmation email** is sent to the vendor with a summary of what they paid for. * Back in Vendor Space, the vendor's pipeline stage automatically updates to **Paid**. *** ## Key things to know * **No account required.** Vendors do not need to create a Vendor Space account to pay. The payment link is all they need. * **Secure and unique.** Each payment link is generated with a secure token tied to that specific vendor and event. Links cannot be reused or shared between vendors. * **Stripe handles card processing.** Vendor Space never sees or stores vendor credit card numbers. All payment data is handled securely by Stripe. > **Tip:** If a vendor reports that their link is not working, check their pipeline stage. If it already shows "Paid," the link has already been used. If the link has expired or been replaced, you can generate a new one from the Vendors tab. *** ## After payment Once a vendor pays: * Their **pipeline stage** moves to **Paid** automatically. * The transaction appears in your **Transactions** page with full details. * Funds are deposited into your connected **Stripe account** (minus the transaction fee). > **Tip:** You can view all completed payments from the Transactions page in your sidebar. See [Viewing Transactions](/docs/payments/viewing-transactions.md) for more details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://vendorspace.gitbook.io/docs/payments/how-vendor-checkout-works.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.