Development for finance and fintech
Payments, dashboards and services that pass the bank's review and hold up under peak load
What we build
- Payment acceptance
- Client dashboard
- Subscriptions and recurring charges
- Operations panel
- Exports and reports
- Bank and acquiring integration
What usually hurts
“The payment went through but the order never updated”
We split payment and order into separate states and confirm by webhook rather than redirect: the payment survives even if the person closes the tab
“Legal asks for one thing, engineers say it is impossible”
We settle the requirements before the code: what to store, for how long and where. Arguing over a schema is cheaper than rewriting a database
“We cannot see where the money is stuck”
We build an operations panel: the status of every payment, refunds and reconciliation in one place
“We are afraid of double charges”
An idempotency key on every operation: a repeated request does not create a second charge
What we account for
Money is counted in minor units as integers: cents get lost on floating-point types
Storing personal and payment data: what may live with you and what only with the provider
Refunds and partial refunds are designed in from the start, bolting them on later costs more
Operation history is immutable: a correction is a new record, not an edit of the old one
