Stripe sends the customer to a secure Stripe page: card, Apple Pay, Google Pay, Klarna, iDEAL, BLIK, SEPA and other local methods. The store gets the result from Stripe and sets the order status.
When you need this:
- Selling in the EU, UK or US — customers see their country's methods.
- SEPA payments — the order waits for the bank, then becomes paid by itself.
- The cart changed after going to pay — another amount won't become “Paid”.
- A chargeback at the customer's bank — the order gets the status you choose.
Where to start: “Store settings” → “Checkout & payment” → Stripe → keys, webhook address and “Enabled”.
What Stripe payments can do
- Take payments on the Stripe page — the methods you turned on in the Stripe Dashboard that suit the customer.
- Work in test mode — test cards, no money is charged.
- Keep test and live keys together — the mode switch picks which pair is used.
- Set the order status on its own — paid, waiting for the bank, failed, refunded, disputed.
- Refund the full amount or part of it — with a button in the Elbuz order card.
How to connect Stripe
You need a Stripe account for your company. Stripe gives you test mode right after sign-up, before any contract, so you can set up and check the module in advance.
- Open the module screen. “Store settings” → the “Checkout & payment” section → the Stripe card.
- In the “Connection” block, leave “Test mode” on and copy the “Webhook address”.
- Create a webhook in the Stripe Dashboard with this address and the events from the “Webhook events” field (below).
- In the “Test keys” card, enter the “Test secret key” and the “Test webhook signing secret”.
- Turn on the “Enabled” switch at the top of the screen and click “Save”.
- Check with a test payment, then switch to live mode.
1
Stripe card2
Status mark: keys needed- The Stripe payment module card; clicking it opens the module screen.
- What the module is missing: "keys needed" until the keys for the current mode are entered.
1
Enabled switch2
Test mode3
Webhook address4
Still to set up5
Mode- Shows Stripe to customers once saved.
- Test payments with no money charged; the pair of test keys is used.
- Paste this address into the webhook in your Stripe account.
- What is still missing for payments to work.
- The mode payments are running in now.
The key card of the current mode is expanded and marked “in use now”; the other one is collapsed. An enabled module won't save without both keys of the current mode: the field shows “Required — the module will not work without it”.
A key of the wrong mode, such as sk_live_… in the test field, won't save: the message next to the field says the test key must begin with sk_test_ or rk_test_. How the window works in general is covered in “Store settings”.
Where to get the keys and create the webhook
Each mode needs two values: the secret key and the webhook signing secret. Test and live values are different. You switch the mode at the top of the Stripe Dashboard (Test mode or Sandbox).
Secret key
Stripe Dashboard → Developers → API keys → Secret key → Reveal. The test key begins with sk_test_, the live one with sk_live_. Stripe shows the live key in full only once: keep a copy.
A restricted key works too: rk_test_… or rk_live_…. The “Help” button on the module screen explains which permissions to give it.
The webhook and its secret
A webhook is a store address where Stripe sends notifications about payments and refunds. Without it, the store won't know the customer has paid.
- In the Stripe Dashboard: Workbench → Webhooks → Create an event destination.
- Choose Your account and the Snapshot event payload.
- Select all 9 events from the “Webhook events” field. The “Copy all” button copies them together.
- The type is Webhook endpoint. Paste the “Webhook address” from the module screen into Endpoint URL and save.
- On the webhook page, click Reveal next to Signing secret and copy the
whsec_…value into the signing secret field.
1
Webhook address2
Webhook events3
Test secret key4
Test webhook signing secret5
In use now- Paste into the webhook Endpoint URL in your Stripe account.
- The events to tick in the webhook; Copy all copies them together.
- The Secret key from Developers → API keys in test mode (sk_test_…).
- The Signing secret of the test webhook (whsec_…).
- The key pair used in the current mode.
For live mode, repeat the same steps in the live mode of the Dashboard: it has its own webhook and its own secret. Site protection must not block the webhook address, or statuses won't change.
Keys aren't shown after saving — the field only tells you they are set. To change one, click “Replace” and enter a new one.
How to check with a test payment
- Place an order for yourself and choose Stripe. Above the redirect you'll see “Test mode (Stripe): no money is charged”.
- On the Stripe page, pay with a test card from the table. Expiry date — any future date, CVC — any three digits.
- Check the order in Elbuz: it has the status from the “Paid” field. The payment itself is visible in the Stripe Dashboard in test mode.
| What to enter | What happens |
|---|---|
Card 4242 4242 4242 4242 | Successful payment |
Card 4000 0000 0000 3220 | Payment with 3-D Secure confirmation: click Complete in the window |
Card 4000 0000 0000 0002 | The bank declined: the customer stays on the Stripe page and can try another card |
SEPA, IBAN DE89370400440532013000 | First “Waiting for the bank”, then “Paid” |
SEPA, IBAN DE62370400440532013001 | First “Waiting for the bank”, then “Payment failed” |
SEPA is shown only if it's turned on in the Stripe Dashboard and the order is in euros.
Switching to live mode
While test mode is on, the right side shows “Test mode is on — no money is charged. Turn it off before you start selling”. To accept real money:
- In the Stripe Dashboard, finish activation: Activate payments, your company details and the payout account.
- Create a webhook in the live mode of the Dashboard.
- In the “Live keys” card, enter the “Live secret key” and the “Live webhook signing secret”.
- Turn off “Test mode” and click “Save”. The “Mode” line on the right will show “Live mode”.
After the switch, the store closes the unfinished payment pages of the old mode in Stripe. The test keys stay saved: turn test mode back on and they're still there.
What the customer sees and for which orders
At checkout the method is called “Card, Apple Pay, Google Pay and other methods (Stripe)”. After confirming, the customer sees “Taking you to the secure Stripe payment page…” and lands on the Stripe page.
| What happened | Where the customer returns |
|---|---|
| Paid, or started a delayed payment (SEPA) | The order success page |
| Clicked “Back” on the Stripe page | Checkout, with no message: the cart and details are in place, the order is unconfirmed. They can pay again or choose another method |
| Came back without paying | Checkout with “The payment was not completed. Please try again or choose another payment method…” |
| The payment page couldn't be opened | Stays in the store with “Could not open the payment page…” and a “Pay” button |
You choose which methods appear on the Stripe page in the Stripe Dashboard: Settings → Payments → Payment methods. The module doesn't limit them: Stripe shows the enabled methods that suit the customer's country and currency.
The amount is charged in the order currency, without conversion. Whether your account accepts that currency is shown in the Stripe Dashboard.
The page language is the store's main language if Stripe supports it: English, German, Polish, French and other EU languages. Stripe has no Ukrainian, so for it the page opens in the customer's browser language.
For which orders to show it
The “Where to show” block limits who sees Stripe:
- “Geo zone” — the payment is shown only to customers with an address in this zone; “All zones” — to everyone.
- “Minimum order total” — Stripe appears from this total in the store's main currency. Empty or
0— always. Stripe itself rejects amounts below about EUR 0.50 or USD 0.50. - “Sort order” — the position in the payment list; a smaller number goes higher.
Order statuses
The store sets the status itself when Stripe reports an event. You choose which ones in the “Order statuses” block.
1
Paid2
Waiting for the bank3
Payment failed4
Refunded5
Disputed by the customer- Stripe confirmed payment of the full amount.
- SEPA and other delayed methods while the bank confirms.
- The bank did not confirm a delayed payment.
- After a refund of the full amount.
- The customer disputed the payment at the bank; by default the status does not change.
| Field | When it is set | Default |
|---|---|---|
| Paid | Stripe confirmed payment of the full order total. The customer gets the usual order email | “Processing” |
| Waiting for the bank | SEPA and other delayed methods: the customer has paid, the bank confirms within up to a few business days | “Pending” |
| Payment failed | The bank didn't confirm a delayed payment | “Failed” |
| Refunded | The full amount was refunded to the customer | “Refunded” |
| Disputed by the buyer | The customer disputed the payment with their bank (chargeback) | “— keep the current status —” |
Until the customer pays, the order stays unconfirmed. A new payment attempt closes the previous Stripe page, so the customer can't pay twice from an old tab.
A delayed payment is visible by the “Waiting for the bank” status. Don't ship until the module sets “Paid”.
The dispute, with its amount and reason, is visible in the Stripe Dashboard, and you respond there too. If “Disputed by the buyer” is left at “— keep the current status —”, the order status won't change.
When the status doesn't change
- Wrong amount. The customer changed the cart after going to payment and paid the old amount. The money arrived, but the order stays unconfirmed — check the amount in the Stripe Dashboard.
- Second payment. The customer paid for an order that is already paid. Both payments of the order are visible in the Stripe Dashboard: refund the extra one.
- Wrong mode. A test payment while the store is in live mode doesn't mark the order paid: no money arrived. A live payment while the store is in test mode doesn't either, though the money is real: find it in the Stripe Dashboard.
- Forged notification. The module checks the signature with the webhook secret and asks Stripe again for the amount, currency and mode. Someone else's notification won't change the order.
- The order is already paid. A delayed payment or its failure doesn't override the “Paid” status.
Refunds in the order card
A site order arrives in Elbuz as a “Customer order” document with the payment type “Bank card”. Its card has a “Payment in Stripe” block: payment status, amount, how much was captured and refunded. It also shows how much is still refundable and every payment attempt with its Stripe reference.
Only the buttons available to the order right now are shown:
| Button | What it does |
|---|---|
| Refund | Returns the full amount or part of it to the customer. The amount field is prefilled with the balance: to refund everything, keep the suggested amount |
| Refresh status | Gets the payment status from Stripe if a notification didn't arrive |
You can refund several times, but no more than what's left. Stripe takes a few minutes to process a refund: an amount in progress no longer counts toward “Refundable”.
| Refund | What happens to the order |
|---|---|
| Full amount | The status from the “Refunded” field |
| Part | The status stays the same; the refunded amount is visible in the “Payment in Stripe” block |
| Stripe declined | The status stays the same; a message in the order card shows the reason |
Before a refund, the program asks for confirmation with the warning “This operation cannot be undone.”. The order status changes the same way as after a Stripe notification, and the order history gets an entry with the result.
If the store didn't respond, the program shows “It is unknown whether the operation went through…” and a “Retry” button. It repeats the same operation: the money won't move a second time. Clicking the button again starts a new operation.
Only a user with the “Payment operations: refund, hold, credit” permission can make refunds — by default, the owner. “Refresh status” is available to everyone who can see the order.
A card refund goes out right away and reaches the customer in 5–10 days. SEPA and bank refunds take a few days: the “Refunded” status appears once Stripe completes the refund. The store doesn't email the customer about the refund.
The module doesn't track refunds you make yourself in the Stripe Dashboard: change the order status yourself.
Once there are orders through Stripe, the module screen header shows the last 30 days: count, total, average order value and the share of canceled or refunded ones.
Scenarios
Home appliances: customers from the Netherlands pay through their bank
Turn on iDEAL and Bancontact in the Stripe Dashboard, with storefront prices in euros. A customer from Amsterdam sees iDEAL on the Stripe page and pays in their banking app. The washing machine becomes “Paid” without you doing anything.
Monitors for a company in Austria: payment from a bank account
Turn on SEPA Direct Debit in the Stripe Dashboard. In “Waiting for the bank”, choose a status that tells the warehouse not to ship. The company enters its IBAN, and a few days later the order becomes “Paid” or “Payment failed” on its own.
Clothing: paying from a phone without entering a card
Check that Apple Pay and Google Pay are on in the Stripe Dashboard. Set “Sort order” lower than for other payment methods, for example 0: Stripe will be first. A customer on an iPhone pays with Apple Pay without entering a card.
A storefront in dollars for the US alongside euros
Add the USD currency to the store and turn on the US payment methods you need in the Stripe Dashboard. A US customer pays in dollars, a European one in euros. One module covers both markets.
What to do when payments don't work
| What you see | Why | What to do |
|---|---|---|
| The customer doesn't see Stripe at checkout | The module is off, there's no secret key for the current mode, the total is below the minimum, or the address isn't in the geo zone | Check “Enabled”, the keys of the current mode, “Minimum order total” and “Geo zone”, then “Save” |
| The customer sees “Could not open the payment page” | Stripe rejected the key, the order currency or a too-small amount | Paste the key again from the Stripe Dashboard. Still not working — Elbuz support will check the Stripe response in the module log |
| The payment went through, but the status didn't change | Wrong webhook secret, the webhook was created in the other mode or with a different address, or site protection blocks the address | For this order, click “Refresh status” in its card in Elbuz. Copy the Signing secret again. Check the webhook address and events in the Stripe Dashboard: Workbench → Webhooks → your webhook → Event deliveries |
| Next to the key: “A test key starts with sk_test_…”, “A live key starts with sk_live_…” or “A signing secret starts with whsec_.” | A key of the other mode, or pasted with a space or not in full | The test key is sk_test_…, the live key is sk_live_…, the webhook secret is whsec_…. Copy with the button in the Stripe Dashboard |
| You refunded the full amount, but the status didn't become “Refunded” | A refund to a bank account rather than a card is still in progress at Stripe | Wait: the status changes once Stripe completes the refund. The refund progress is visible in the Stripe Dashboard |
| “The store did not accept the settings” or “The store did not accept some values: see the highlighted fields” | The store didn't respond or rejected some fields | Fix the highlighted fields and save. If no fields are highlighted, the changes will go with the next export |
FAQ
Can a company from Ukraine connect Stripe?
The module works with any Stripe account. Whether Stripe opens an account for your company is Stripe's decision, based on the country where the company is registered.
Do I need the publishable key pk_…?
No. Stripe shows the payment page itself, so the store only needs the secret key and the webhook secret.
What happens if I turn the module off?
Stripe disappears from checkout. The keys and settings are kept: turn it back on and everything is in place.
Can I send the customer a Stripe payment link from Elbuz?
Yes, but that's a separate Stripe connection in Elbuz, with its own key and its own notification address: Payment links.
The zone I need isn't in the “Geo zone” list — what do I do?
Elbuz support creates the zone, for example “Netherlands”. Then choose it in the “Where to show” block.
How do I refund the customer?
Open the order in Elbuz and click “Refund” in the “Payment in Stripe” block. The amount is already filled in with the balance: for a partial refund, enter less. The customer gets no refund email from the store.
Where to find it and who has access
- Menu
- Directories → Operations → Store settings → “Checkout & payment” → Stripe
- Access rights
- the “Store settings” window in group permissions; refunds — the “Payment operations: refund, hold, credit” permission
- Prepare
- a Stripe account, a secret key and a webhook for each mode
Related topics
- If you need to understand how the store settings window works — Store settings.
- If your customers from the Baltics are used to Paysera — How to accept Paysera payments in your store.
- If you need to send an invoice and get paid via a link — Payment links.
- If you need to process a paid order in Elbuz — Customer order.
