Australia's Only Premier Laravel Partner Brisbane-based, Australia-wide

Stripe integration for subscriptions, marketplaces and custom billing

Pixel builds payments on Stripe into custom Laravel platforms: recurring subscriptions, marketplace payouts with Stripe Connect, refunds and failed payment recovery. We have built each of these in production, for clients and for our own products.

Start with a Technical Blueprint
Our Clients
chemist-warehouse-logo
hellofresh-logo
absolute-domestics-logo
factor-logo
youfoodz-logo
trilogy-care-logo
nourishd-logo
canary-logo
astrid-logo
cannabis-warehouse-logo
dress-for-dignity-logo
cannareviews-logo

Pixel is a team of Stripe developers who build subscriptions, marketplace payouts, invoicing and payments on Stripe into custom Laravel platforms. The service is for businesses whose billing rules are more specific than a standard checkout allows, such as weekly subscriptions, split payouts to sellers or funded billing. Each build is scoped in a fixed-fee Technical Blueprint and quoted as a fixed price.

Where it breaks

When a Standard Stripe Setup Stops Being Enough

Stripe handles the card. Everything around the card is your business logic, and that is where off-the-shelf checkouts run out.

01

Subscriptions that do not fit a plan

Orders that change every week, skipped deliveries, paused accounts and customers billed on a cut-off day do not map cleanly to a fixed monthly plan.

02

Money that belongs to someone else

A marketplace takes a payment that mostly belongs to a seller. Splitting it, taking a commission and paying out correctly is a system in its own right.

03

Failed payments nobody chases

A card declines, the order still ships or the customer quietly lapses. Without a retry schedule and clear rules, revenue leaks every billing cycle.

04

Refunds that leave the books wrong

A partial refund on a split order has to come back from the right seller, with the fee handled correctly, or the platform absorbs the difference.

05

Payments and orders that disagree

The customer was charged but the order was never saved, or the reverse. Without reconciliation, support finds out from the customer.

What we build on Stripe

These are the parts of Stripe we have used in production systems.

Recurring billing

Off-session charges against saved cards on your own schedule, or Stripe Billing subscriptions with Checkout and the customer Billing Portal.

Stripe Connect

Connected accounts for sellers or service providers, onboarding and verification inside your own site, commissions and payouts.

Checkout and saved cards

PaymentIntents and SetupIntents, 3D Secure, saved payment methods on web and in mobile apps, and card updates from the customer account.

Refunds and adjustments

Full and partial refunds, transfer reversals on marketplace orders, and extra charges when an order changes after payment.

Failed payment recovery

Scheduled retries, customer notifications, pausing when authentication is required and cancellation rules you define.

Webhooks and reconciliation

Signed, idempotent webhook handling, plus scheduled jobs that check Stripe for anything a webhook missed.

Subscriptions

Subscriptions and recurring billing

There are two ways to run subscriptions on Stripe, and choosing between them is the first design decision.

Stripe Billing suits products with fixed plans. Stripe owns the schedule, the invoices and the retries. We use it for Pulsewise, our own monitoring product, with Stripe Checkout for sign-up, free trials and the Billing Portal for plan changes and cancellation.

A subscription engine of your own suits businesses where the order changes from one cycle to the next. The platform decides what each customer owes, then charges the saved card off-session. We built this for Nourish'd, a meal delivery business whose customers choose meals weekly, skip weeks and pause their accounts.

In that model the platform also owns the rules Stripe would otherwise apply: when the weekly charge runs, how many times a failed payment is retried and over what period, what happens when the bank asks for 3D Secure on an unattended charge, and when a subscription is cancelled after repeated failures. Those rules are written down, tested and run on a schedule.

Marketplaces

Stripe Connect for marketplaces

Stripe Connect lets a platform take a payment and pay other parties from it. We built Rethread, our own marketplace for second-hand school uniforms, on Connect, and the same patterns apply to any multi-seller platform.

Onboarding inside your site. Rethread uses Custom connected accounts. A school uniform shop enters its business details, representative, identity documents and bank account in Rethread, and never sees a Stripe screen. Stripe's verification status comes back by webhook, and the shop is told exactly what is outstanding.

Separate charges and transfers. A cart can contain items from several sellers. The buyer is charged once. The payment is authorised first, captured only after stock is confirmed and the order is saved, and released if anything fails. Each shop is then paid by a transfer linked to the original charge.

Commission and fees. The platform commission is set per seller. Stripe's actual processing fee is read back from the charge and shared across the sellers in the cart in proportion to their part of the order.

Refunds. A refund reverses the matching transfer. Where a reversal is not possible, the amount goes on a ledger and is deducted from that seller's next payout, so the platform is not left carrying it.

The unhappy path

Invoicing, refunds, failed payments and dunning

Most of the work in a payments build is in what happens when a payment does not go to plan.

Failed payments. A declined recurring charge is retried on a schedule, the customer is notified through email or your marketing platform, and the subscription is paused or cancelled after a number of consecutive failures that you choose.

Disputes. A chargeback raises an alert to your team straight away, with the order attached, so evidence can be submitted inside Stripe's deadline.

Reconciliation. If a customer is charged but the order was not saved, a scheduled check finds the mismatch and alerts staff. Refunds that stay pending are checked against Stripe until they settle.

Invoices and accounts. Payments and refunds can be posted to your accounting system as they happen. See our Xero integration page for how that side works.

How We Build Stripe Integrations

Payments code has to be correct when it runs twice, runs late or runs out of order.

01

Verified webhooks

Every webhook is checked against Stripe's signature before it is trusted.

02

Idempotent handling

Each event is recorded, so a repeated delivery from Stripe is recognised and ignored.

03

Idempotency keys

Charges and transfers are sent with a key per order, so a retry after a timeout cannot charge or pay twice.

04

Queued jobs

Follow-up work runs in background jobs with retries and increasing delays.

05

Scheduled reconciliation

Regular checks compare your records with Stripe and resolve anything left pending.

06

Alerts

Failed transfers, disputes and unmatched payments notify your team, and errors are tracked in Sentry.

Stripe in production

Nourish'd runs weekly subscription billing on Stripe through a platform we built and maintain.

Nourish'd

A custom meal delivery platform managing subscriptions, funded-care billing, fulfilment, and operational reporting across three customer segments.

30+

Operational Reports

199

Support at Home Providers

3

Customer Segments

Read the Nourish'd case study →
FAQ

Stripe integration
FAQs

Couldn't find the answer you were looking for? No worries, get in touch with us.

Contact Us

Should we use Stripe Billing or build our own subscription logic?

chevron-down

Use Stripe Billing when you sell fixed plans at fixed intervals. It is faster to build and Stripe handles invoices and retries.

Build your own when the amount or contents change each cycle, when customers skip or pause often, or when billing depends on rules Stripe cannot express. You still use Stripe to store cards and take the payment.

Can you set up Stripe Connect for a marketplace?

chevron-down

Yes. We built our own marketplace, Rethread, on Stripe Connect, including seller onboarding inside the site, payments split across several sellers in one cart, commissions, refunds and payouts.

Which type of Connect account should we use?

chevron-down

It depends on how much of the experience you want to own. Custom accounts keep sellers entirely inside your site but make you responsible for collecting verification details. Express and Standard accounts hand more of that to Stripe.

We recommend one in the Technical Blueprint based on who your sellers are and how much support load you can carry.

How do you handle failed subscription payments?

chevron-down

With a retry schedule, customer notifications and clear rules for pausing and cancelling. Where the bank requires authentication on an unattended charge, the customer is asked to complete it and the subscription waits.

Can Stripe payments sync to Xero or MYOB?

chevron-down

Yes. The invoices and bills behind Stripe payments can be posted to your accounting system automatically. We have built Xero and MYOB sync on a platform that takes its payments through Stripe.

Can you take over an existing Stripe integration?

chevron-down

Yes, if the application is built on Laravel. We audit how payments, webhooks and refunds are handled before changing anything, because payment code that looks untidy is often handling a case somebody learned about the hard way.

Get your billing rules written down before anyone writes code

A Technical Blueprint maps how payments, refunds and failures should work in your platform, with a fixed price to build it.

Book a Technical Blueprint

$2,990 inc. GST · credited against your first invoice if you build with us

Related integrations

Discovery Call

One call.
We'll both know.

20 minutes to walk through your project, ask the hard questions, and work out honestly if we're the right team for it.

  • One call per day - it gets our full attention
  • Australia's only Laravel Premier Partner
  • Trusted by Chemist Warehouse, HelloFresh and Youfoodz
  • Senior engineers only - no juniors on your project
  • Brisbane-based, onshore team

Press Esc to close  ·  B to reopen