Stripe Development & Integration

— FAQ

Frequently asked questions

• Do I need my own Stripe account?+

  Yes, and you should want one. The account is registered to your business, the payouts go straight to your bank, and we only need restricted API access to build the integration.

• Can Stripe handle subscriptions and one-off payments together?+

  It can, and most of the shops we build do both. Stripe treats a subscription as a recurring price on the same customer record, so a client can hold a plan and still buy something once.

• What happens if a customer closes the tab mid-payment?+

  Nothing is lost. Fulfilment is triggered by the webhook Stripe sends, not by the customer arriving back on your thank-you page — which is precisely why the webhook handler is the part we spend the most time on.

• Can you add Stripe to an existing WooCommerce or WordPress site?+

  Yes. On WooCommerce we use the official Stripe extension where it fits and custom code where the flow needs more, such as subscriptions tied to your own accounts area. On Next.js or a custom build we integrate the API directly. The standard case is covered by the fixed-price Stripe Payments package.

• Can Stripe take Apple Pay, Google Pay or Klarna?+

  Yes, where Stripe supports them for your country and currency. Wallets and methods like these are switched on in the Stripe dashboard and appear on their own in Checkout or the Payment Element, so adding one rarely means new code. We check which methods your customers' countries can actually use before launch.

• Should we use Stripe or PayPal?+

  It is rarely either-or. Stripe gives you cards, wallets and subscriptions behind one API, with the checkout on your own site; PayPal matters where your buyers already have an account and prefer to pay with it. We build on Stripe first and tell you honestly whether your customers are likely to ask for PayPal as well.