Hostra for fintechs
Fintech teams usually do not fail at the happy path — they fail in the middle of a transaction, at reconciliation and at the accounting story they have to tell afterwards. Hostra supplies the settlement engine, ledger and APIs so your team can spend its time on the product rather than on rebuilding exactly-once semantics.
What you build on top
- Embedded money movement: create a settlement intent from your product flow and let the engine own execution and final state.
- Ledger-backed balances: balances derived from double-entry postings instead of a mutable counter in your database.
- Card funding: tokenised card payments through Stripe, without your product touching a card number.
- Stablecoin payouts: USDT and USDC on Tron, Ethereum, Polygon and BSC as an alternative payout rail.
- Event-driven experience: HMAC-signed webhooks drive your notifications instead of polling loops in the client.
Integration shape
The integration is REST described by OpenAPI 3.0. A typical path: request a quote, create a transfer with a UUID v4 Idempotency-Key, then poll the transfer or consume the webhook. Errors are RFC 7807 problem documents, and every request carries an X-Request-ID so support can trace a specific call. Machine-to-machine keys are merchant-scoped with role-based scopes, so an integration only reaches what it needs.
Operational control
- Deterministic retries: check-before-retry and exclusive leases prevent duplicate charges or payouts.
- Final states you can act on: pending, in_flight, succeeded, failed, reversed — no ambiguous 'processing' limbo.
- Reversals through a dedicated settlement endpoint rather than ad-hoc corrections.
- A tamper-evident audit trail for support, disputes and internal review.
What Hostra does not do
Hostra is infrastructure. It is not a bank, not a regulated payment institution and not a licence provider. KYC/KYB/AML, wallet custody and card issuing are in development, so a fintech integrating now brings its own compliance and provider relationships for those areas.