Hostra Payment Infrastructure
Hostra provides payment settlement infrastructure for fintechs, payment service providers and businesses, combining transaction processing, deterministic settlement, double-entry ledger capabilities, REST APIs, card infrastructure and stablecoin settlement. Hostra is infrastructure you integrate — not a consumer wallet, not an exchange, and not a regulated financial institution.
The problem Hostra solves
Money movement fails in the middle. A provider call times out, a worker dies after the charge but before the payout, a retry lands twice, and the accounting record disagrees with what actually happened on the rail. Hostra treats that failure mode as the primary design constraint: every movement of money starts as a durable settlement intent, is executed exactly once — never zero times, never twice — and is recorded as balanced double-entry postings that can be reconciled against the rail afterwards.
Platform layers
- API surface
- REST described by OpenAPI 3.0, RFC 7807 problem responses, Idempotency-Key on mutations and X-Request-ID on every request.
- Settlement engine
- Durable settlement intents, saga orchestration with compensation, leases and retry orchestration, exactly-once commit.
- Double-entry ledger
- Balanced postings and immutable entries; balances are derived from entries rather than stored and mutated.
- Rails
- Card charge and card push (Visa Direct OCT) via the card provider, and on-chain stablecoin disbursement.
- Eventing
- Outbound webhooks signed with HMAC-SHA256, retried and dead-lettered from a transactional outbox.
- Audit
- Tamper-evident hash-chain over state changes with a proof-of-integrity endpoint.
What is available today
- Settlement engine with durable intents, exactly-once commit and compensating sagas.
- Double-entry ledger as the source of truth, with a tamper-evident audit hash-chain.
- Settlement methods: card_charge (pull), card_push (Visa Direct OCT) and on_chain.
- Server-side quotes with a 60-second TTL; a stale quote is rejected rather than silently repriced.
- Card payments through Stripe tokenisation — Hostra never receives or stores a PAN or CVV.
- Stablecoin disbursement in USDT and USDC on Tron, Ethereum, Polygon and BSC.
- M2M API keys with RBAC scopes, HMAC-signed outbound webhooks and an ISO 8583 / ISO 20022 protocol layer.
In development
The following are scaffolded or planned and are not currently available: wallet custody, card issuance and management, Apple Pay and Google Pay, KYC/KYB/AML, payment links and checkout, recurring billing, crypto-to-fiat and crypto-to-card payout, additional EVM networks, ACH/SEPA/SWIFT, Mastercard Send, and the risk engine. The roadmap tracks their status.
Explore the platform
- Settlement engine — durability, sagas and exactly-once execution.
- Ledger — the double-entry model behind every balance.
- Virtual cards — the card data surface available today and what is still in development.
- Stablecoin settlement — USDT and USDC as one of the supported settlement rails.
Settlement engineLedgerVirtual cardsStablecoin settlementArchitectureAPI documentation
Who Hostra is for
Teams that need money movement to be correct under failure: fintechs building products on top of payment primitives, payment service providers running acquiring and payouts, and enterprise payment teams embedding settlement in existing systems.