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

Fintech software development for platforms that move money

Pixel builds the parts of a platform that take payments, split them, pay people out and keep the accounts straight. We have built subscription billing, marketplace payouts, direct debit, bank payment files and accounting sync in production, on Laravel.

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 builds financial software for Australian businesses: payment platforms, recurring billing, marketplace payouts and accounting integrations. The service is for businesses whose product depends on money moving correctly between customers, sellers, suppliers and the books. Each build starts with a fixed-fee Technical Blueprint and is quoted as a fixed price.

The problems

Where Financial Software Goes Wrong

Money features look simple in a demo. The difficulty is in the cases a demo never shows: the payment that fails, the refund that crosses a payout, the job that runs twice.

01

A payment is taken twice

A timeout causes a retry, and the retry charges the customer again. Preventing it has to be designed in from the start.

02

The ledger and the bank disagree

The platform says a seller is owed one amount and the payout says another, and nobody can explain the difference.

03

Refunds after the money has moved

A customer is refunded for an order whose seller has already been paid. Someone has to carry that balance and recover it.

04

Failed payments left to chance

Without a retry schedule and clear rules, recurring revenue leaks every cycle and nobody sees it happen.

05

Finance still works from exports

Transactions live in the platform, the accounts live in Xero, and a person re-keys one into the other every week.

06

No record of who did what

When an amount is questioned, there is no trail showing what was charged, when, by which process and what the provider said back.

What we build for finance-heavy platforms

Each of these is running in a production system we built.

Payment platforms

Card payments, saved payment methods, 3D Secure and payment status handled through signed, idempotent webhooks.

Subscription and recurring billing

Billing engines for amounts that change every cycle, with retry schedules, pausing and cancellation rules.

Marketplace payouts

One payment split across several sellers, platform commission, fee allocation, transfer reversals and a ledger of balances owed.

Direct debit

Bank account mandates and a payment per order, with status confirmed days later by webhook.

Bank payment files

ABA files generated for batch payouts through Australian banks, for payees who are paid outside a card network.

Accounting integrations

Invoices, bills and credit notes posted to Xero or MYOB, with payment and reconciliation status read back.

Systems

The systems these platforms connect to

Financial software is mostly integration. The platform holds the rules, and regulated providers hold the money.

Payments. Stripe for cards, subscriptions and Stripe Connect payouts, and GoCardless for direct debit. We have run both side by side in one platform.

Accounting. Xero and MYOB, including customer invoices and supplier bills raised from the same job, account codes chosen by rule, and paid status flowing back.

Banks. Batch payments by ABA file. Our team maintains an open-source PHP library for generating ABA files, and we use it for seller payouts.

Open banking. We have not yet built on the Consumer Data Right. If your product needs bank data, the Blueprint covers which accredited provider to build on and what that involves, before you commit to it.

In production

Three payment systems we built

Weekly subscription billing. Nourish'd charges customers each week for an order that changes from one week to the next, by card or by direct debit. The platform decides what each customer owes, retries failed payments on a schedule, pauses a subscription when a bank asks for authentication, and bills funded-care customers through their provider.

A marketplace with two kinds of seller. Rethread, our second-hand school uniform marketplace, pays school uniform shops through Stripe Connect and pays individual sellers by bank transfer using ABA files. One cart can contain items from several sellers. Commission, Stripe's fee and refunds are allocated to each seller, and anything a seller owes is carried on a ledger and deducted from their next payout.

Invoices and bills for every job. A national services marketplace we built raises a customer invoice and a contractor bill for each job, posts both to the accounting system with the right account, tax code and state, and reads back when each is paid so remittance advice can be sent.

How We Build Software That Handles Money

The same engineering rules apply to every payment system we build.

01

Idempotency

Every charge, transfer and webhook can be processed twice without doing anything twice.

02

Authorise, then capture

Where stock or eligibility has to be confirmed, the payment is held first and captured only once the order is certain.

03

Reconciliation

Scheduled jobs compare the platform's records with the provider's and resolve or report any difference.

04

Ledgers, not flags

Balances are derived from recorded entries, so every figure can be traced to the transactions behind it.

05

Tested rules

Billing rules are covered by automated tests, because a mistake here is paid for in real money.

06

Alerts

Failed transfers, disputes and unmatched payments notify people immediately, and errors are tracked in Sentry.

Scope

What we do, and what we leave to licensed providers

We build the software. We do not hold client money, provide credit or give financial advice, and the platforms we build rely on licensed providers such as Stripe and GoCardless for the regulated parts.

That is usually the right design for a new financial product. It keeps card data and bank credentials out of your systems, reduces what you have to be audited for, and lets the product reach customers sooner.

If your product will need its own licence or accreditation, bring your compliance adviser into the Blueprint. We will design the system around the obligations they identify.

Billing in production

Nourish'd runs card and direct debit subscription billing on 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

Fintech software
FAQs

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

Contact Us

Do you hold a financial services licence?

chevron-down

No. We build software. The regulated parts, such as holding funds and processing cards, are handled by licensed providers like Stripe and GoCardless that your platform integrates with.

Have you built open banking or Consumer Data Right integrations?

chevron-down

Not yet. If your product needs bank data, the Blueprint covers which accredited provider to build on and what the integration involves before you commit.

How do you stop a customer being charged twice?

chevron-down

Every charge and transfer is sent with an idempotency key, and every webhook is recorded when it is processed. A retry after a timeout or a repeated event is recognised and does nothing.

Can you build payouts to sellers or contractors?

chevron-down

Yes. We have built payouts through Stripe Connect and by ABA file for Australian bank transfers, with commission, fee allocation and a ledger of amounts owed.

Can payments be reconciled with Xero or MYOB?

chevron-down

Yes. Invoices and bills are posted to the accounting system, and payment status is read back so the platform and the accounts agree.

How much does fintech software cost to build?

chevron-down

It depends on how many payment flows there are and how many parties money moves between. We quote a fixed price after scoping the work in a Technical Blueprint, which is $2,990 including GST and credited against your first invoice if you build with us.

Get the money rules written down before the build starts

A Technical Blueprint maps how payments, payouts, refunds and reconciliation should work in your product, 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 pages

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