Payments and invoicing
CrexiPay
A payments back office for growing businesses. CrexiPay turns invoices, subscriptions, deposits and donations into a branded, secure Stripe checkout, and runs every one of a business's Stripe accounts from a single login.

The problem
Service businesses wanted to send a payment request and get paid by card without building their own checkout, and some run more than one Stripe account. The first version was a plain PHP app on shared hosting that could not support Stripe Connect safely.
My role
- Replaced the first plain PHP version with a Laravel rebuild on its own server, backed by automated tests and background queues.
- Chose Stripe Connect with OAuth, so each business connects its own Stripe account and keeps control of its payments.
- Phased delivery so the core payment features shipped first, then added opt-in Stripe Tax in October 2026.
Key decisions
| # | Decision | Why |
|---|---|---|
| 1 | Rebuild instead of patching the first version | Payment logic needed tests and a safer foundation |
| 2 | Stripe Connect with OAuth only | Businesses keep their own Stripe accounts and liability |
| 3 | Stripe Tax as an opt-in | Businesses choose when to collect tax |
Results
- Live in production on Stripe Connect since September 2026.
- Invoices and pay links, subscriptions, deposits and donations from one back office.
- Role
- Project manager and lead developer
- Users
- Service businesses
- Stack
- Laravel, MySQL, Redis, Stripe Connect
- Status
- Live in production since September 2026
- Live
- crexipay.com
- Employer
- Social Points Media