Velg Training Membership & Events Platform Modernisation
A full rebuild of Velg Training's membership, events, shop and invoicing platform onto Laravel 13, taking it from end-of-life technology to a secure, search-friendly site in four months.
Limited availability. Two project slots remaining for November 2026 2 project slots remaining for November 2026
Tokenised cards, recurring billing, and direct debit with production-tested handling for PayWay’s less common API flows.
PayWay is not Stripe. The documentation is thinner, the developer experience is dated, and most agencies will try to talk you out of it because they have never shipped it. Sometimes that advice is right and you should move. Often it is not: your merchant rates, your bank relationship, or your finance team's existing processes make PayWay the sensible choice, and what you actually need is someone who has already done the work. We have shipped PayWay in production, including tokenised card storage and recurring billing.
Proven in client projects
Westpac PayWay in production, alongside Stripe and Braintree. If your bank relationship points at PayWay, that should not mean settling for a worse build.
The Westpac PayWay integration work our senior team most often takes on.
Card Payments & Tokenisation
Card payments through the PayWay REST API with tokenised storage, so you can charge a returning customer without ever holding their card number. This is the right way to keep PCI scope small, and it is not the default if nobody sets it up deliberately.
Recurring Billing
Scheduled and recurring payments against stored tokens, with proper handling of declines, retries, and expiring cards. Recurring billing that silently stops collecting is worse than no recurring billing, because nobody notices for a month.
Direct Debit & Batch Payments
Direct debit from bank accounts and batch payment files, which are still how a lot of Australian B2B and membership billing actually happens. Unglamorous, well suited to PayWay, and genuinely useful when your customers are not paying by card.
Reliability & Reconciliation
Idempotent payment requests so a network timeout does not double-charge a customer, plus reconciliation against your settlement reports. Payment code is the one place where "probably fine" is not good enough.
Migration To or From PayWay
Moving onto PayWay from another gateway, or off it onto Stripe. Either direction, the tricky part is stored cards: tokens are gateway-specific and generally cannot simply be exported, so the migration has to be planned around re-collecting or re-tokenising without annoying your customers.
Someone Who Has Actually Shipped It
The honest advantage here is unglamorous: we have already worked out PayWay's quirks on someone else's clock. You are not paying us to learn a poorly documented API on your project.
The same approach behind every integration we deliver, from the first conversation to the years of maintenance that follow.
Scope & map
We define the data, events, responsibilities, source of truth, and failure cases across Westpac PayWay and the systems around it.
Build for failure
We design around real failure modes with appropriate retries, idempotent writes, validation, and reconciliation so a temporary outage does not become silent data loss.
Test & reconcile
We test representative data in a safe environment, verify each data path, and reconcile the expected outcomes before go-live.
Monitor & maintain
Monitoring and alerting start at launch. Our senior team keeps the project context and remains responsible for changes, incidents, and long-term operation.
A full rebuild of Velg Training's membership, events, shop and invoicing platform onto Laravel 13, taking it from end-of-life technology to a secure, search-friendly site in four months.
Impact Office Supplies' B2B and B2C eCommerce website, built in Laravel and integrated with their Options ERP. We've been their exclusive development partner since 2018.
A Back to School ordering platform for Impact School Supplies, where schools approve booklists, parents order online, and student eBook licences are managed and sent to publishers.
The services and platforms a Westpac PayWay integration most often plugs into.
For organisations that need websites, ERPs, finance, CRM, fulfilment, or identity systems to exchange data reliably.
Ordering portals, operations software and quoting systems for when off-the-shelf tools no longer fit how you work.
Online stores for consumer brands, built to keep selling when traffic spikes.
A good fit for custom applications, complex business rules, APIs, and integrations that need a maintainable long-term codebase.
Scheduled or event-driven updates can be safer, cheaper and easier to recover.
Each field and business rule needs one accountable owner across the connected systems.
Retries, logs, alerts and reconciliation are part of the integration—not optional support work.
PayWay’s thinner documentation and less common implementation path make discovery, error handling, and testing especially important. Our team has already shipped it in production.
A common shortcut
The implementation relies on assumptions around undocumented edges.
Pushes you onto Stripe by default, because it is the gateway they know, not because it is the right call for your bank relationship.
Bolts tokenisation on as an afterthought, or stores card details directly, quietly dragging your whole system into PCI scope.
Recurring billing that silently stops collecting when cards expire or declines pile up, and nobody notices for a month.
Our senior-team model
Has already shipped it in production.
A straight answer on whether PayWay actually suits you, from someone who has shipped both and gains nothing from steering you either way.
Tokenised storage from the start, so you charge returning customers without ever holding a card number and your PCI scope stays small.
Declines, retries, and expiring cards handled deliberately, with reconciliation against your settlement reports so a stalled collection surfaces the same day.
“ Digital Bird has had a huge influence on our business providing many solutions besides just a fantastic reliable website. Jonathan is great to work with and has a solution to every challenge. Jonathan also has the ability to “dumb it down” and provide timely advice and assistance if something goes astray. With Jonathan we have in excess of 99% uptime on all three websites. ”
Systems commonly compared, connected, or operated in the same workflow.
ERP & Accounting
Payments
Integration
Book a free strategy session with the senior people who scope and deliver the work. We will help clarify the problem, test assumptions and identify a practical next step—without turning the session into a generic sales call.
Planning a website or platform project? Planning a project?