Stripe for e-commerce: setup, fees, and why we use it

Why payment processing is a strategic decision

Most store owners treat payment processing like choosing an electricity provider. They pick whatever is default, never think about it again, and assume the fees are all the same.

They are not.

Your payment processor determines: what you pay on every transaction, which payment methods your customers can use, how your checkout looks and behaves, whether you can do subscriptions and recurring billing, and how much control you have over the post-purchase experience.

We use Stripe for Build444 and recommend it for most custom e-commerce projects. Not because it is trendy. Because the economics, developer experience, and feature set make it the rational choice for stores that want to grow.

The full picture.

Stripe in 60 seconds

Stripe is a payment infrastructure company. They process payments for businesses of all sizes, from a one-person store selling digital products to enterprise companies processing billions. They operate in 46+ countries and support 135+ currencies.

What makes Stripe different from traditional payment gateways:

• No monthly fees. You pay per transaction. No minimum volumes. No annual contracts.
• Transparent pricing. 2.9% + $0.30 per card transaction in the US. 1.5% + 0.25 EUR in the EEA. Published on their website. No negotiation needed at low volumes.
• Stripe is developer-first. The API documentation is considered the gold standard. Every feature is accessible via API, which means total control over the payment experience.
• There is a hosted checkout option. If you do not want to build a custom payment form, Stripe Checkout is a pre-built, optimized payment page that converts well out of the box.

The three ways to integrate Stripe

Option 1: Stripe Checkout (hosted)

Stripe Checkout is a pre-built payment page hosted by Stripe. You redirect the customer to Stripe's domain, they pay, and Stripe redirects them back to your confirmation page.

Pros:

• Fastest to implement (hours, not days)
• Stripe optimizes it across millions of transactions
• PCI compliance handled entirely by Stripe
• Built-in address autocomplete, error handling, and mobile optimization
• Supports 40+ payment methods including Apple Pay and Google Pay
• Dynamic tax calculation available

Cons:

• Customer leaves your site briefly (branded Stripe page)
• Limited design customization
• Cannot embed additional content on the payment page

Best for: Most stores. Especially early-stage stores that want a high-converting checkout without custom development. We use Stripe Checkout for the Build444 SEO report product, and it handles everything from payment to receipt emails.

Option 2: Stripe Elements (embedded)

Stripe Elements are customizable payment UI components that you embed directly in your website. The customer never leaves your site. You control the design and layout completely.

Pros:

• Full design control, matches your site exactly
• Customer stays on your domain throughout
• Can combine payment with other form fields (shipping, custom options)
• Still PCI-compliant (card data goes directly to Stripe, never touches your server)

Cons:

• More development work (days instead of hours)
• You manage the form layout, validation, and error states
• Requires more testing across devices and browsers

Best for: Stores where the checkout experience is part of the brand, or where you need to collect additional information during payment. Custom product builders, subscription sign-ups with configuration, or any flow where leaving the site would break the experience.

Option 3: Custom integration (full API)

For complex use cases, you can interact with Stripe's API directly. Create PaymentIntents, manage customers, handle webhooks, and build entirely custom payment flows.

Pros:

• Unlimited flexibility
• Can handle any payment scenario: marketplace splits, usage-based billing, metered subscriptions, complex tax requirements
• Full control over the timing and sequence of charges

Cons:

• Significant development effort
• PCI compliance requirements increase
• More surface area for bugs

Best for: Marketplaces, platforms with complex billing, and businesses with payment flows that do not fit standard models.

The fee comparison you actually need

Everyone compares headline rates. What matters in practice:

The numbers that catch most people: PayPal is meaningfully more expensive per transaction. Shopify Payments is competitive on the headline rate but charges a 0.5-2% surcharge if you use any other payment gateway alongside it. That surcharge applies even if you use Stripe as an additional option.

At $20,000/month in revenue:

• Stripe: $880/month in fees
• PayPal: $1,096/month in fees
• Shopify Payments + Shopify Basic: $880 + $39 = $919/month
• Shopify with external Stripe: $880 + $200-400 surcharge + $39 = $1,119-$1,319/month

Over three years, the difference between Stripe on a custom build and Shopify with Stripe is $8,600-$15,800. That is real money.

Webhook handling: the part most tutorials skip

Webhooks are how Stripe tells your application that something happened. A payment succeeded. A subscription was renewed. A dispute was filed. Your application needs to listen for these events and act on them.

This is where most ecommerce integrations get sloppy. If your webhook handler fails, orders do not get fulfilled. Customers do not get confirmation emails. Inventory does not update.

What a production webhook handler needs:

1. Signature verification. Every webhook from Stripe includes a signature. Verify it. Without this, anyone can send fake events to your endpoint.
2. Idempotency. Stripe may send the same event multiple times. Your handler must process it safely regardless of how many times it arrives.
3. Async processing. Return a 200 response immediately, then process the event asynchronously. Stripe times out after 20 seconds and marks the webhook as failed.
4. Error handling and logging. Log every event. Alert on failures. A missed webhook is a missed order.

We built our own webhook handler for Build444 that forwards Stripe events to our n8n automation workflows. Payment comes in, n8n processes the order, generates the deliverable, sends the email. Zero manual steps. The webhook handler is at /api/webhooks/stripe and it has processed every order without a single miss.

Multi-currency: selling internationally

If you sell to customers in multiple countries, Stripe makes multi-currency straightforward. You can:

• Present prices in local currency. Show EUR to European customers, GBP to UK customers, USD to US customers. Stripe converts at the current exchange rate.
• Accept local payment methods. iDEAL in the Netherlands, Bancontact in Belgium, MobilePay in Denmark. Each market has preferred payment methods, and Stripe supports most of them.
• Settle in your preferred currency. Regardless of what the customer pays in, Stripe deposits to your bank in your home currency.

The fee for currency conversion is 1% on top of the standard processing fee. For most businesses, the increased conversion from local pricing and payment methods more than offsets this.

Subscriptions and recurring billing

If your business has a recurring component (memberships, SaaS, monthly boxes, retainer services), Stripe Billing handles it without additional tools.

What Stripe Billing includes:

• Subscription creation with multiple price tiers
• Free trials with automatic conversion
• Proration when customers change plans
• Automated dunning (retry logic for failed payments)
• Customer portal for self-service management
• Usage-based and metered billing
• Invoice generation and PDF receipts

Most subscription businesses layer Chargebee or Recurly on top of Stripe. For straightforward subscription models, Stripe Billing alone is sufficient and eliminates an additional vendor and fee.

Tax calculation

Stripe Tax automatically calculates and collects the correct sales tax, VAT, or GST based on the customer's location. This is especially relevant for EU businesses dealing with VAT MOSS, where the tax rate depends on the buyer's country.

Stripe Tax costs 0.5% per transaction on top of processing fees. For businesses selling across multiple tax jurisdictions, this eliminates the need for a separate tax calculation service and the compliance risk of getting it wrong.

What we built with Stripe at Build444

We practice what we recommend. Build444's own product, the SEO audit report, runs entirely on Stripe.

The flow: customer selects their market and enters their URL on the product page. Stripe Checkout handles the payment. A webhook fires to our n8n workflow. The workflow runs a full SEO audit across 7 parallel analysis branches, generates a PDF report using Claude, and emails it to the customer. The entire pipeline from payment to delivery is automated.

We chose Stripe Checkout (hosted) because the payment step is straightforward and did not need custom design. The complexity is in the post-purchase automation, not the payment form. Stripe Checkout handles responsive design, error validation, and receipt emails without us writing a single line of payment UI code.

Total Stripe fees for this product: 2.9% + $0.30 per sale. No monthly platform fee. No revenue share. No vendor lock-in. If we ever wanted to switch payment processors, the checkout integration is the only part that changes.

The decision framework

Use Stripe Checkout if:

• You want a high-converting checkout with minimal development
• Your payment flow is standard (pay once, get product)
• You do not need heavy design customization on the payment page
• You want Stripe to handle PCI compliance entirely

Use Stripe Elements if:

• Checkout design is part of your brand experience
• You need to collect non-payment information during checkout
• Customers should stay on your domain throughout
• You have development resources for custom implementation

Use the full Stripe API if:

• You have complex billing (marketplaces, usage-based, splits)
• Your payment flow does not fit standard models
• You need granular control over charge timing and sequencing

For most e-commerce stores, Stripe Checkout is the right starting point. You can always upgrade to Elements or the full API as needs evolve. Starting with the simplest integration that meets your requirements gets you to revenue faster.

The bottom line

Look, Stripe is not the cheapest option for every scenario. Square is slightly cheaper for in-person payments. PayPal has broader consumer recognition. Shopify Payments avoids the external gateway surcharge if you are already on Shopify.

But for custom-built e-commerce stores, Stripe is the clear winner. Transparent fees, no platform lock-in, developer-friendly APIs, and a checkout that converts. It is the payment layer we build on, and the one we recommend to clients.

For more on choosing between platforms, read our Shopify vs custom comparison. For the full guide to building a store that sells, start with our online store launch guide.

Ready to build your store with Stripe? We handle the integration so you can focus on your product.