Payment systems and fintech products from people who have built them
We built the core of a white-label payment gateway — state machine, double-entry ledger, acquirer routing, settlements — and we run our own accounting SaaS that files tax returns with the Latvian tax office. That is the experience we bring to your payment flow, ledger or fintech product.
What we build
Money software has to be right before it is pretty. These are the parts we have designed and shipped.
Payment gateway cores
A merchant API with idempotency keys and signed requests, a payment state machine with enforced transitions, cascading acquirer routing and signed webhooks with retries.
Ledgers and settlements
Double-entry ledgers in integer minor units, client funds kept apart from fee revenue, settlements with rolling reserve and reconciliation against acquirer statements.
Checkout and provider integration
Stripe, PayPal and other payment providers wired into your product: checkout, webhooks, refunds, payouts — and the edge cases that come with them.
Accounting, invoicing and tax
Invoices with VAT, payroll with a full gross-to-net breakdown, VAT and corporate tax declarations generated in the tax office’s XML format.
Compliance-aware architecture
Card data kept out of your systems from the first commit, audit logs, role-based access and data stored in the EU.
Fintech product sites
Marketing sites for payment providers that speak to merchants — open banking, acquiring, alternative payment methods and payouts — in a compliance-first tone.
Fintech we have shipped
How we build money software
- 1
Money in integers, never floats
Amounts are stored in minor units and every balance comes from a double-entry ledger, so the books always reconcile.
- 2
Every state change is explicit
Payments, refunds and payouts move through state machines with enforced transitions — an impossible state cannot be written.
- 3
Honest about scope
Where an acquirer contract, a licence or a PCI audit is needed, we say so up front and design the seams for it instead of pretending a prototype is production.
Selected work
Payments and fintech projects
Questions we get asked
Can you build a payment gateway?
We have built the core of one for a fintech client — merchant API, payment state machine, double-entry ledger, acquirer routing, settlements and a hosted checkout — as a working prototype with simulated acquirers. Going live also needs acquirer contracts, KYB and AML onboarding and the right licence, which we plan for from the start.
Do you integrate Stripe, PayPal or other providers?
Yes — checkout, webhooks, refunds and reconciliation for the providers your business uses. If you are still choosing, we compare fees, payout times and supported payment methods for your markets first.
Will card data touch our servers?
Not if we can help it. A hosted checkout or the provider’s hosted fields keep card data with the provider, which keeps your PCI scope as small as possible.
Tell us about your payment flow
What moves money in your product today, what has to change and which providers or regulators are involved. We reply within a day.