New in Endora Commerce: a built-in CRM with sales opportunities See it →
Endora Commerce

Stripe integration

Stripe runs as a full gateway integration in Endora Commerce: cards, BLIK, Przelewy24, Apple Pay and Google Pay, with payment embedded in your own checkout or handled through a Stripe Checkout redirect. Below: what exactly it covers, what you need on the Stripe side, and when another gateway is the better fit.

When Stripe makes sense in B2B sales

Stripe is a payment provider with international reach, offering one account and one API for cards, wallets and local payment methods. In wholesale and distribution it is rarely the main way of settling orders: regular customers pay by bank transfer on terms or against a credit limit, and the platform has both in its open core. A card gateway handles the rest: new customers without an approved limit, prepaid orders, customers abroad, and a B2C channel if you run one from the same admin panel.

Stripe is a good choice for that role when a significant share of payments are cards held by buyers outside Poland, or when the company already has a Stripe account for another product. The Stripe module is a paid module, like the other online payment gateways. It was added to the platform in one of the platform updates.

What the integration supports

  • Cards with 3-D Secure. Strong customer authentication runs automatically where the card issuer requires it.
  • BLIK through the same Stripe account.
  • Przelewy24 as a fast bank transfer method, through the Przelewy24 payment type available in Stripe.
  • Apple Pay and Google Pay.
  • Saved cards: a returning buyer pays without re-entering card details.
  • Refunds issued from the Endora admin panel or directly from the Stripe dashboard. Both stay in sync, so the finance team can work wherever suits them.

Embedded checkout or Stripe Checkout

The integration comes in two variants, and choosing between them has practical consequences.

AspectForm embedded in your checkoutRedirect to Stripe Checkout
Where the buyer paysOn your site, without leaving the checkoutOn a payment page hosted by Stripe
Apple PayRequires registering the store domain in the Stripe dashboardWorks with no additional configuration

Domain registration applies to every domain and subdomain where you show an Apple Pay button, including test ones. If you run several sales channels under different addresses, register each of them. Stripe handles validation with Apple for you, as described in the Stripe Apple Pay documentation.

BLIK through Stripe: limits worth knowing

BLIK on Stripe works only for payments in PLN and for buyers in Poland. For orders in euros or any other currency, the method is not available. The buyer enters a six-digit code from their banking app and has 60 seconds to approve the payment on their phone. After that the attempt times out and a new code is needed.

BLIK refunds can be full or partial. BLIK also has its own claims process: a buyer can dispute a transaction, and Stripe holds back the disputed amount from your balance until the dispute is resolved. Details are in the Stripe BLIK documentation.

What the buyer sees and what the admin sees

Stripe appears in the checkout as a payment method that you configure the same way as bank transfer or credit limit:

  • visibility is set separately for each sales channel, and for selected organizations you can narrow the list of available methods,
  • for each method you choose the order statuses for a pending, a successful and a failed payment,
  • you can add a flat surcharge to the order for choosing a given method.

The order is created in the pending-payment status and changes once the payment is resolved. If an attempt fails, the buyer can retry the payment from their account, and an admin can do so from the order. Every attempt stays in the order’s payment history. The platform also emits settlement, failure and refund events, which you can pass on, for example as a webhook to your ERP.

What to prepare on the Stripe side

  1. An activated Stripe account. Accepting real payments requires completing the provider’s business verification.
  2. API keys. Stripe distinguishes a publishable key from server-side keys, with separate sets for the sandbox and for live mode. You can tell them apart by the _test_ and _live_ parts of the prefix. In the Endora admin panel, provider configurations are stored encrypted.
  3. A webhook endpoint. Stripe reports payment outcomes, and refunds issued in its dashboard, through webhooks signed with the Stripe-Signature header. Each endpoint has its own signing secret, different in the sandbox and in live mode.
  4. Enabled payment methods. BLIK, Przelewy24 and wallets are switched on in the payment method settings of the Stripe dashboard.
  5. Registered domains, if you choose the embedded checkout with Apple Pay.

In live mode Stripe retries undelivered notifications for up to three days and does not guarantee their order, so a short store outage does not mean losing information about a payment.

Stripe and the other gateways

You pay Stripe’s own processing rate and nothing on top. Endora does not add an intermediary surcharge, unlike some SaaS platforms that charge extra unless you use their preferred gateway.

If you sell almost exclusively in Poland and in złoty, compare Stripe with PayU and tpay: both offer fast bank transfers directly, whereas in Stripe they are available through Przelewy24. The gateways are not mutually exclusive, because each is a separate payment method with its own visibility per channel. The full list is in the integrations catalog.

Let’s find out what we can connect at your end

Book a free consultation. We will walk through your ERP, warehouse and sales processes, and show you what the integration path looks like step by step.

Michał Zabielski, founder and CEO of Endora

Michał Zabielski

Founder and CEO, Endora

We reply within one business day.