I used ChatGPT and the Floot connector to build a one-product storefront, then tested checkout, payment confirmation, and PDF delivery without moving real money.
Disclosure: Floot sponsored this article and provided testing access. The walkthrough describes my experience, including the limits of what I verified.
You’ve built an app with AI. The page looks good, the buttons work, and you have a link you can share. Then someone wants to buy what you’re offering. What happens next?
For a digital product, the customer needs more than a checkout button. They need a confirmation, the file they paid for, and an order record that connects those steps. I wanted to see whether I could build and check that flow through a conversation.
Floot’s connector works with ChatGPT and Claude. In my previous Floot article, I used ChatGPT to build and publish a content planner. For this walkthrough, I again used ChatGPT with the Floot connector to create a separate Online Biz Offers storefront for one product. I tested its checkout in Floot’s preview, where Stripe uses test mode and no real money moves.
Start With One Product and a Clear Purchase Flow
My product was the Online Business Launch Checklist, a nine-page PDF workbook for entrepreneurs, freelancers, creators, and online business owners. It includes a focus checklist, an offer worksheet, launch preparation, pricing and content planning, customer journey checks, and a first-week review.
I already had the finished workbook. The storefront needed to show visitors what was inside, display the €5 one-time price, and provide a clear route from preview checkout to payment confirmation and the PDF download. I also wanted an order record so I could match the confirmation to the payment.
That gave me a practical way to judge the result. A successful preview payment was only one checkpoint. I also needed to download and open the workbook from the confirmation screen.
What the Floot Connector Did in This Build
I started by asking ChatGPT to check my Floot access and the payment documentation, then create a separate storefront project. In the same prompt, I described the product, price, order confirmation, and PDF delivery I wanted. I also specified that checkout should be tested in Floot’s preview using Stripe test mode.
I continued in the same conversation to request design changes, troubleshoot the download, and verify the successful test payment.
If you’re writing your own build prompt, describe what should happen after someone clicks Buy. Say what they should see when payment succeeds, what order information to save, and how they’ll receive the product. “Add payments” leaves those decisions open.
Step 1: Build the Storefront and Prepare the Download
The storefront used Online Biz Offers’ purple, black, and white branding. The product area paired a purple workbook-cover visual with the Online Business Launch Checklist headline, a description of the nine-page PDF, the €5 EUR one-time price, and a Buy the checklist button.
A banner appeared in the preview reading “Stripe test mode · No real money moves.” Below the product area, What’s Inside explained the workbook’s six sections.
You can view the workbook cover, product details, and What’s Inside on the published storefront demo.
The finished workbook went into private storage. The app checked payment on the backend before issuing a download link valid for five minutes. I also checked that pending and canceled orders, and a request without a matching order token, could not retrieve the file.
Step 2: Find the Stripe Connection Settings
I already had a Stripe account registered in Germany. To find the connection controls, I opened my Floot project, selected Services in the top navigation, and then chose Payments in the sidebar.
From the Payments tab, I chose the option to connect an existing Stripe account. I had first looked for these controls on Floot’s homepage before finding them inside the project.
I completed the Stripe authorisation privately. Floot’s built-in integration handles the Stripe keys and webhooks, so I didn’t paste payment credentials into ChatGPT. Floot payment setup documentation.
The project’s Payments settings showed Live mode: Ready. This confirmed the Stripe setup status. It did not confirm that the storefront had completed a live purchase, and I did not make one.
Step 3: Confirm You’re in the Preview
Before entering payment details, I checked that I was in Floot’s preview. Floot documents that preview checkout uses Stripe test mode, while published apps use live mode. Floot’s guide to payment modes.
I completed the €5 checkout in preview using Stripe’s test card. That was the only purchase I made; no live payment was initiated.
I also checked the published storefront’s setup. Its Stripe configuration was in live mode, but the checkout code ChatGPT had generated for this store contained a check that refused live-mode requests. As a result, the published Buy button could not create a Checkout session, and I couldn’t inspect what label Stripe Checkout would show. This was behavior of the code in this storefront. Floot documents live payments for published apps after Stripe setup and the required plan.
I disabled the public Buy button and added a notice explaining that checkout is unavailable on the demo. The preview remains available for the test checkout.
Step 4: Complete the €5 Test Checkout
In the preview, I clicked Buy the checklist. Stripe Checkout opened for the Online Business Launch Checklist at €5.00.
Following Floot’s preview instructions, I entered Stripe’s test card number, 4242 4242 4242 4242, a future expiry date, and a three-digit CVC.
After checkout, the storefront displayed Test Payment Confirmed, the product name, amount, order reference, and Paid · test mode status. It also displayed the Download the PDF button.
Step 5: Match the Payment Record and Open the PDF
I asked ChatGPT to look up the payment through Floot. The connector returned a successful €5.00 EUR Stripe test payment that matched the order reference saved by the storefront.
I clicked Download the PDF on the paid confirmation, saved the file, and opened the nine-page Online Business Launch Checklist. I wanted to see what happened after the payment went through. The confirmation showed that the order was paid, and opening the workbook showed that the storefront had delivered the file.
That completed the end-to-end purchase and download flow in Floot’s preview, from a simulated checkout to opening the workbook. It confirmed how the app handled a successful test payment, but it did not verify a live customer purchase. No real money moved.
The first exercise asks readers to choose one audience, identify a problem that audience already tries to solve, and define the smallest useful outcome their offer can deliver.
The final page helps readers review their first week. It gives them space to record common questions, checkout or delivery problems, and what customers found useful, then choose one change to make.
What Worked in the Preview?
- Checkout. I completed a €5 card test payment in Floot’s preview.
- Order confirmation. The storefront showed the product, amount, order reference, and paid test status.
- Payment verification. ChatGPT checked the Stripe test payment through Floot and matched it to the saved order.
- PDF delivery. I downloaded and opened the workbook from the confirmed test order.
- Download restrictions. Separate preview checks blocked downloads for pending and canceled orders.
I built the storefront in ChatGPT only; I haven’t tested the equivalent Claude workflow. Apple Pay and Link were also untested. Payouts, refunds, disputes, cross-device download recovery, emailed delivery, declined-card handling, and download-link expiry were outside the test. I didn’t conduct a full security or accessibility review or test simultaneous customers.
What Else Could You Build With Floot?
Floot Payments documentation covers shopping carts, subscriptions, coupons, and refunds. Those features could support a larger catalogue or a recurring offer, though my test covered one product and a single payment. Floot Payments features.
For physical products, Floot documents a Shippo integration for address checks, carrier rates, shipping labels, and tracking. Preview shipping uses sample rates and labels. Real shipping requires connecting your own Shippo account, and Shippo bills for real labels. My workbook was delivered digitally, so shipping was outside my test. Floot shipping documentation
What Does It Cost to Accept Payments?
At the time of writing, Floot Payments supports preview testing on the Free plan without connecting your own Stripe account. Accepting real payments through a published app requires Pro or Power. Floot lists a 1% platform fee on Pro and 0% on Power; Stripe processing fees apply separately. My sponsored testing access was on Power. Floot Payments plans and fees.
The €5 in my walkthrough was a simulated preview payment. No real revenue or card-processing fee resulted from that test.
My Takeaway From the Build
The most useful check came after checkout. I matched the payment record to the storefront’s saved order, downloaded the workbook, and opened the PDF. That let me verify the order-to-download flow.
If you’re building a digital storefront with Floot, start with one finished product and follow the customer journey from checkout through delivery. Check that the order is recorded and that the customer can retrieve the product after payment is confirmed.
If you found this walkthrough useful, I’d appreciate a clap, comment, or share. It helps more readers find practical ways to build, test, and launch useful online business tools.
