> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/billing-and-payments/stripe-payments.md). # Stripe PeakCommerce integrates natively with **Stripe** as a payment processor and billing provider, so you can capture cards, store payment methods, and run subscription charges directly inside your commerce journeys. Stripe is one of PeakCommerce's first-class billing adapters: it plugs into the same catalog, order, and self-service surfaces that power the rest of the platform, which means a Stripe-backed tenant gets the same journey builder, customer portal, and reporting as any other. ## Why it matters Stripe handles the parts of taking money that you don't want to build or carry compliance for — secure card capture, tokenization, and recurring charges. PeakCommerce orchestrates the buying experience around it and keeps your order and transaction records in sync. ## What you can do with it * **Secure card capture** — Stripe Elements collects card details on your checkout and payment pages, so sensitive data goes straight to Stripe and never touches your servers. * **Saved payment methods** — cards are tokenized and stored against the customer for reuse on renewals and future purchases. * **One-time and recurring charges** — Stripe processes initial payments and recurring subscription charges; results flow back onto the order and transaction records. * **Catalog sync** — your Stripe products and prices sync into PeakCommerce so plans and charges can be sold through journeys. * **Subscriptions, invoices, and refunds** — view active subscriptions and open invoices in the customer portal and admin; refunds are issued from the Stripe Dashboard. ## How it fits / connect Connect your Stripe account to PeakCommerce by providing your API (secret) key and publishable key; a journey's billing step then renders Stripe Elements to collect payment. On submission, PeakCommerce tokenizes the payment method, attaches it to the customer, and charges the order. For asynchronous confirmations, PeakCommerce verifies Stripe webhooks against a configured signing secret before applying the result. ## Who and when Choose Stripe when you want card processing and stored payment methods with minimal PCI scope, especially for self-serve checkout and SMB subscriptions. ## Gotchas * A publishable key is required for client-side Elements; the secret key stays server-side. * Configure a webhook signing secret so async payment confirmations are verified — without it, verification is rejected outside development. * Refunds are handled in the Stripe Dashboard rather than in-app. ## See also * [Billing & Payments integrations](/integrations/billing-and-payments/billing-and-payments.md) * [Integrating billing systems with PeakCommerce](/integrations/billing-and-payments/integrating-billing-systems-with-peakcommerce.md) * [Zuora billing integration](/integrations/billing-and-payments/zuora-integration/zuora-billing-integration.md) --- # 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://docs.peakcommerce.com/integrations/billing-and-payments/stripe-payments.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.