# Build an ecommerce site on answer.cloud with Stripe: the hatjob example

> Canonical source: [Build an ecommerce site on answer.cloud with Stripe: the hatjob example](https://www.answer.cloud/blog/ecommerce-answer-cloud-stripe-hatjob/)

Build an ecommerce site with answer.cloud and Stripe, using hatjob’s product pages, Payment Links, and fulfillment workflow as an example.

An ecommerce website needs a place to showcase products, a reliable checkout, and a way to turn successful payments into fulfilled orders. You can build those pieces with an Astro storefront on answer.cloud and Stripe for payments.

hatjob, a store selling town-inspired hats, provides a practical example. Its implementation uses product pages for individual towns, Stripe Payment Links for purchases, and an order worker that connects paid purchases to Printful fulfillment.

The same approach works for a small apparel brand, an artist selling prints, or a business launching a focused product collection.

**Start with the storefront**

Build the website on answer.cloud. Create a homepage, collection pages, individual product pages, and clear shipping, returns, privacy, and contact information.

hatjob organizes its catalog around states and towns, with product paths such as `/utah/midway`. Each page brings together the hat’s photographs, description, price, and purchase link.

Keep that information in the generated HTML so customers and answer engines can read it without waiting for browser scripts. answer.cloud hosts the static website and supplies its answer-engine layer, including search, chat, and analytics. Server-side payment and order processing run separately. [answer.cloud hosting guide](https://ai.answer.cloud/docs/mcp-hosted-sites/)

**Give each product a clear identity**

Maintain a structured catalog with a stable SKU for every purchasable product or variant. Include its name, description, images, displayed price, availability, and checkout reference.

For hatjob, the town identifies the design. A store selling several sizes or colors should identify each purchasable combination explicitly.

Only enable purchasing when the product, price, and fulfillment mapping are ready. hatjob’s source keeps products without configured checkout links visibly unavailable. That makes it possible to preview a growing collection while keeping purchasing tied to verified products.

**Choose the checkout your store needs**

For a focused catalog with one-product purchases, Stripe Payment Links provide a straightforward starting point. Create a Stripe Product and one-time Price, configure a Payment Link, and connect the product page’s purchase button to it. The public storefront needs no Stripe API secret. [Stripe Payment Links](https://docs.stripe.com/payment-links/share)

hatjob uses this approach for its available Utah hats, with a separate link for each town design. Its example price is $30 USD for one hat, including U.S. shipping.

A multi-item cart needs an additional service. The storefront sends selected SKUs and quantities to a secure backend, which validates them and creates a Stripe Checkout Session using approved prices. The backend should calculate the charge from trusted catalog data rather than accepting a total supplied by the browser. [Stripe Checkout](https://docs.stripe.com/payments/checkout/how-checkout-works?payment-ui=stripe-hosted)

Whichever approach you choose, configure allowed shipping countries, shipping charges, receipts, support details, and return policies before opening checkout.

Configure appropriate product tax classifications too. Confirm applicable registrations before enabling automatic tax collection; turning on Stripe Tax does not register the business with tax authorities. [Stripe Tax setup](https://docs.stripe.com/tax/set-up)

**Connect payment to fulfillment**

A customer reaching the success page is not sufficient proof of payment. Order processing should begin with a verified Stripe webhook.

The backend checks the webhook signature, records or queues the event, and verifies the current payment status. It must also handle delayed payment methods and repeated event deliveries. A retried webhook should never produce a second shipment. [Stripe fulfillment guide](https://docs.stripe.com/checkout/fulfillment)

hatjob’s backend uses a queue and durable order records to manage that work. It maps the purchased hat to its approved Printful product, checks fulfillment costs, and uses a stable supplier order identifier to recover safely from interrupted requests.

Keep credentials and customer information in the backend. Store payment and fulfillment status separately from notification status so a failed email can be retried without submitting the order again.

**Test the complete purchase journey**

Develop with a Stripe sandbox and keep its credentials separate from live payments. Test successful purchases, declined payments, abandoned checkout, delayed payments, duplicate webhooks, refunds, and invalid product selections.

Also test a successful payment where the customer closes the browser immediately afterward. The order should still reach the fulfillment queue exactly once.

When the storefront is ready, build Astro and deploy only the generated `dist/` contents through Answer Cloud. Review mobile layouts, purchase links, product metadata, deployment warnings, and the answers returned by site search and chat. Deploy and monitor the order backend separately.

hatjob’s architecture gives each part a clear responsibility: answer.cloud presents the products, Stripe collects payment, and the order backend manages fulfillment. That provides a practical foundation for launching a focused store and adding a cart or more advanced operations as the business grows.