Stripe in Justflows Shop: checkout, wallets, subscriptions and disputes

Until now, a Justflows shop that wanted to take payments online used Mollie. Stripe was listed as a payment provider, but it could not actually take a payment. With Shop 0.3.2 that changes: Stripe is a full payment gateway, from the first card payment to subscriptions, refunds and disputes.

It was built in nine steps, one GitHub issue each, and they all shipped together in this release. Here is what a merchant gets.

Each shop picks one of three checkout experiences in its Stripe settings:

Whichever you choose, the order carries the exact line totals from Shop, and an order is only marked paid when Stripe confirms it with a signed webhook. A redirect back to your site is never enough on its own. Manual capture and your own statement descriptor are supported, and a declined card shows an accessible error message.

Payment links work with Stripe too. A one-off payment link for a named customer can be issued as a Stripe Payment Link, and unpaid orders, such as accepted quotes, can be paid with Stripe or Mollie.

Payment Element checkout can show Stripe's Express Checkout buttons for Apple Pay, Google Pay and Link. They use the same payment, order details and webhooks as a card payment. You turn Express Checkout and Link on or off per test or live mode, and register your site's domain with your Stripe test and live accounts from the settings page.

Shop does not keep its own list of Stripe payment methods. The settings page reads the methods that are available on your Stripe account, for the current test or live mode, and you can switch the ones Stripe lets you change on or off right there. Shop writes that choice back to Stripe.

Active methods appear at checkout as separate choices with their own logos: cards, iDEAL, Bancontact, EPS, Przelewy24, SEPA Direct Debit, Klarna, Afterpay/Clearpay, Affirm and others you enable in Stripe. Shop only offers a method when it fits the order's currency and the billing country, and Stripe makes the final check for the device and account.

Some methods take a few days to confirm. While a payment is processing, the order and its stock stay reserved. If it fails, the order fails in the usual way and the stock is released. For SEPA Direct Debit, checkout shows the mandate text and the order records the mandate reference.

When a signed-in customer pays with Stripe for the first time, Shop creates their Stripe customer with their name, email and billing address. At checkout they can choose to save their card for later, and in their account they can add or remove saved payment methods. They see the card brand, last four digits and expiry date, and so do staff in Customers. Card numbers never reach Justflows.

Saved methods are what subscription renewals are charged to. If a bank asks the customer to confirm a renewal, Shop sends the recovery email it already uses for failed renewals. A personal data export lists that the customer has a Stripe mapping without showing provider ids, and deleting the user removes their saved methods and the mapping.

Each site chooses who runs its subscriptions:

In Billing mode, Stripe's invoices still become ordinary Shop renewal orders, so your reports, invoices and emails stay in one place. The choice applies to new subscriptions. Existing ones keep the mode they started with, so two schedulers never charge the same period.

When you save the Stripe settings, Shop creates or updates its webhook endpoint in your Stripe account, pinned to one API version and subscribed to only the events Shop uses. There is no signing secret to copy: Shop keeps it in the encrypted plugin secret store, and during a rotation it accepts both the old and the new secret.

Each Stripe event is applied once, even if Stripe sends it twice. Failed deliveries appear under Commerce → Payments with a replay button, and Diagnostics flags them. A replay reads the event from Stripe again first, so a late or out-of-order event cannot undo a newer state.

Under all of this sits a Stripe client pinned to one API version. Every request that creates something carries an idempotency key, short network failures are retried a limited number of times, and if Stripe's answer is unclear Shop reconciles it later instead of guessing. Restricted API keys work.

A customer whose card is declined, or who abandons a payment and tries again, keeps the same order. Shop updates that order with the new attempt instead of creating a duplicate, and the stock reserved for it stays available to that cart. When a payment succeeds the cart is emptied, so the next purchase starts clean.

Stripe support is part of Shop 0.3.2, available now in the marketplace. Use test keys first: the settings keep test and live credentials apart and show which mode is in use. Mollie keeps working as before, and you can offer both.

The work is tracked in issues #232 to #240. The Shop documentation covers setup, and questions or problems go to support.justflows.com.