Actively recruiting / 72 applicants
We’re here to help you
Jane Cervantes is in direct contact with the company and can answer any questions you may have. Email
Jane Cervantes, RecruiterAbout the role
The product is built — UI and core screens exist. What's needed is an engineer who can take it from built to live and taking real money. This is not a front-end build; it's commercial plumbing: payment flows, payout logic, and financial correctness under real transactions in two markets.
The work
- Run the core booking-to-payment loop end to end for the first time — it hasn't been proven yet.
- Bring iDEAL live for Dutch customers (EUR) alongside card payments for UK customers (GBP), via Stripe Connect.
- Replace the hardcoded commission rate with a proper rule-based system.
- Handle the full transaction lifecycle: charge, hold, release to provider, payout, and refund — correctly, in both markets.
Definition of done
- A Dutch customer completes a real booking and pays via iDEAL in euro.
- A British customer completes a real booking and pays via card in pounds.
- Commission resolves correctly on both.
- Funds release to the provider correctly in each case.
- One real booking in each market has been taken, released, paid out, and refunded successfully.
What you'll need
- Hands-on Stripe Connect in production: multi-party flows — authorise, capture, hold, transfer, payout, refund, and dispute (rather than checkout integration)
- A redirect-based, asynchronous payment method shipped in production (iDEAL, Bancontact, Sofort, Przelewy24). Confirmation on webhook, never on redirect return.
Note: Card payments launch first; this model lands in a second release, and the architecture must support it without reworking the booking flow.
- PostgreSQL depth: row-level security, migrations, and multi-currency logic across EUR and GBP.
- Comfortable working from an existing interface and a detailed brief, and flagging gaps or risks in scope rather than absorbing them silently.