Adding Stripe payments to a business tool

In many business tools, payment stays outside: an invoice goes out as a PDF, the customer pays by bank transfer, someone reconciles by hand. Building Stripe into the tool changes that: the customer pays where they order or view their invoice, and the status updates itself. Stripe is part of my usual stack. Here is what the integration allows, what Stripe costs based on its public pricing as checked in October 2026, and the rules that keep the system reliable.

What Stripe enables in a business tool

• Online invoice payment from a customer portal, by card or direct debit.
• Deposits and balances: collect 30% at order, the rest on delivery.
• Subscriptions: recurring billing for a service, with automatic retries when a payment fails.
• SEPA Direct Debit: a mandate signed once, then recurring debits, well suited to regular payments.
• Multi-party platforms: with Stripe Connect, split a payment between several recipients, such as a partner network.

According to Stripe’s SEPA documentation, SEPA Direct Debit is supported through the Core scheme (not the B2B scheme), with a €10,000 limit per transaction, about six business days before a payment can be treated as successful, and a no-questions-asked dispute window of eight weeks.

Stripe’s fees

Standard rates published on Stripe France’s pricing page, checked in October 2026. Stripe charges them on each transaction, with no subscription for payments.

An illustrative example, with made-up amounts to replace with your own: 200 invoices of €1,500 a month paid by SEPA Direct Debit cost 200 × €0.35 = €70 in Stripe fees. The same invoices paid with standard EEA cards cost 200 × (€22.50 + €0.25) = €4,550. For large amounts, the choice of payment method matters more than the tool.

Integration budget

In my pricing, the “online payment” building block is $1,700 (€1,500)excl. VAT. It is added to the app’s base price and to the other relevant blocks (customer area, quotes and invoices, notifications).

The estimator calculates a range in one minute with the payment block included. Stripe’s fees are paid by you, like any third-party service.

Rules for a reliable integration

According to Stripe’s webhook documentation, Stripe sends events (payment succeeded, failed, disputed) to your app, signs them, and retries delivery for up to three days in live mode. It guarantees neither the order nor the uniqueness of events. Hence these rules:

1. The webhook is the source of truth, not the return page. An invoice becomes “paid” when Stripe confirms it by webhook, not when the customer lands back on the site.
2. Signatures verified on every event, using the secret specific to each endpoint.
3. Duplicates and out-of-order events neutralized: each event is stored by ID and processed only once.
4. Delayed payments handled: a SEPA debit stays “processing” for several days, and the tool must show that clearly.
5. No card data on your side: entered in Stripe’s components or hosted page.

When this is not the right approach

If your business customers pay by bank transfer at 30 days and it works, adding online payment will not change their habits. Automatic bank reconciliation in your accounting software will do more for you.

And if you only need to send a payment link now and then, Stripe’s payment links are enough, with no development. A custom integration makes sense when payment is part of the process: ordering, booking, subscription, deposit, customer portal.

How the project works

1. A 30-minute call: your current payment methods, amounts and collection delays.
2. Scoping (1 to 2 weeks): payment methods, deposit and reminder rules, fit with your e-invoicing circuit, fixed quote.
3. A Stripe account in your name: you collect the money, I only handle the technical side.
4. Development and testing in Stripe test mode, failure scenarios included.
5. Go-live and monitoring of the first payments, with 3 months of included support.

For a complete customer area, see the client portal solution and the business apps page.