You add a Pay with Stripe button to the checkout you already have. One server-side call returns a checkout URL, the customer is sent straight to a Stripe Checkout page, and the charge runs on your own Stripe account, de-risked by BrokkrPay on the way. Here’s the whole path, end to end, for the operator running the store.
Pay with Stripe in your checkout calls BrokkrPay for a checkout URL.
Every order is de-risked before it is cleared to charge.
The charge runs on your own Stripe account, the funds are yours from capture.
Nine steps from your customer clicking a button to money in your own bank account. Every one of them runs on rails you already control.
Everything up to this point is your store: your cart, your prices, your branding. The only thing BrokkrPay adds is one button.
Your server makes one call to the BrokkrPay API with the order total and your own order reference. It comes back with a checkout URL. There is no script to embed and no gateway to install. WooCommerce merchants add that button with the plugin instead, and write none of it.
You redirect the browser to that URL and it forwards straight to a Stripe-hosted checkout page — clearly separate from your store, and the payment experience your customers already recognise.
Visa, Mastercard, Apple Pay, or Google Pay, entered on Stripe’s page. No card data ever touches your site or BrokkrPay.
This is the step the whole model rests on. Between your storefront and the charge, BrokkrPay does the work that makes the transaction a low-risk one by the time it arrives at your Stripe account.
This is the core of the model: you are the merchant, on your own Stripe account. The funds are yours from the moment they’re captured, and BrokkrPay never holds or touches your money.
BrokkrPay posts an HMAC-signed order.state_changed event to your endpoint and retries until you acknowledge it. That webhook — never the browser redirect — is what you fulfil on. The customer is returned to your own return URL in the meantime.
The de-risking runs on every transaction, not just the first one, so the account stays in good standing as volume grows. Uptime is engineered, not hoped for.
Standard Stripe payouts, on the schedule you choose. Your total cost: a flat 2.5% to BrokkrPay plus Stripe’s standard rate.
The same flow, on every store we underwrite. Each is screened and approved individually before it goes live.
The same payment link can be emailed to the customer instead of redirecting their browser — useful when you are invoicing, or when the customer is not sitting in your checkout. It is one field on the same API call, and everything after it is identical. The redirect is the default and the primary path; the full parameter reference is in the developer docs.
Step two is a plugin rather than an API call: upload the zip, paste one API key, and the Pay with Stripe method appears on your checkout. Every step after it is identical. The WooCommerce plugin page has the abridged install.
Tell us your vertical and your monthly volume. Approved operators are live on their own Stripe account within a day.