Cross-border payments, stablecoin rails, asset issuance, and Soroban smart contracts on a network designed for regulated money movement at negligible cost.
Stellar was designed for one job before it was designed for anything else: moving value between currencies, countries, and institutions quickly and cheaply. It has a built-in decentralised exchange, native asset issuance, path payments that convert between assets in a single transaction, and an anchor model that connects the ledger to real banking rails.
With Soroban, Stellar added a Rust-based smart contract platform on top of that payment core, so programmable logic such as escrows, lending, subscriptions, and tokenised assets can sit directly alongside the settlement layer. We build on both halves: the payment and issuance rails, and the contracts that automate what happens around them.
Ledger 51 204 883
5s close · 412 operations · 0.00001 XLM fee
Ledger 51 204 882
Path payment · EURC → USDC · settled
Ledger 51 204 881
Soroban invoke · escrow release
Payment rails, tokenised assets, and the contracts that automate them.
Cross-border payment flows built on Stellar’s settlement layer, with path payments handling currency conversion in a single transaction.
Issuing regulated assets on Stellar, with the control flags an issuer needs to satisfy its compliance obligations.
Rust contracts compiled to WebAssembly, for programmable logic that runs next to the payment layer.
The bridge between Stellar and the banking system, implemented against the Stellar Ecosystem Proposals that wallets expect.
Key management and wallet experiences appropriate to the amount of money involved.
Running the services your product depends on, rather than hoping a public endpoint stays available.
The payment core, the Soroban contract platform, and the compliance and infrastructure layers around them.
The payment network, its API layer, and the Soroban smart contract platform.
Rust for Soroban contracts, JavaScript and Python for services and integrations.
Anchors, on- and off-ramps, and the compliance plumbing regulated money movement needs.
Horizon instances, Soroban RPC, and the observability around a payment rail.
Working with something else? Our teams pick up new tools quickly. Tell us about your stack.
Money movement leaves no room for approximate engineering.
Authorisation flags, clawback, and SEP-based KYC flows built in from the start rather than retrofitted after a regulator asks.
Sequence number management, fee bumping, and idempotent retries so a network hiccup never turns into a double payment.
Threshold signing and account controls sized to the value at risk, with clear operational procedures behind them.
Trustlines, reserves, and account funding handled correctly, so users are never blocked by a missing balance requirement.
Every payment traceable end to end, with reporting that finance and audit teams can actually work from.
Contracts profiled against Soroban’s CPU, memory, and storage limits, with state archival planned rather than discovered.
Where a payment-first ledger with cheap, fast settlement is the right foundation.
Remittance and B2B corridors that settle in seconds instead of days, at a fraction of correspondent banking cost.
Regulated asset issuance with compliance controls and native DEX liquidity from day one.
Anchors and treasury infrastructure that connect existing banking systems to on-chain settlement.
Creator payouts, usage billing, and disbursements where per-transaction fees would normally kill the model.
A path that treats regulatory and operational requirements as first-class inputs.
We map the money flow before the architecture: who holds funds at each step, which entity is regulated where, what KYC applies, and what the reconciliation and reporting requirements are.
Account structure, asset design, trustlines, signing thresholds, and where Soroban contracts fit, all specified so both engineers and compliance can review it.
Payment flows, issuance, and contracts built in sprints against testnet, with a working demo of the core corridor early rather than at the end.
SEP-compliant anchor endpoints, fiat partner integration, and wallet compatibility testing against the clients your users actually hold.
End-to-end testnet runs including failure paths, contract audit where Soroban is involved, and a full rehearsal of the operational procedures before real money moves.
Mainnet launch with Horizon and RPC infrastructure under monitoring, alerting on submission failures, and support as volume and corridors grow.
What payment and fintech teams ask before building on Stellar.
Stellar has payments in the protocol rather than in a contract: native asset issuance, a built-in order book, path payments that convert currencies atomically, and fees measured in fractions of a cent with roughly five-second finality. On an EVM chain, all of that is contract logic with variable gas costs. If your product is fundamentally about moving money between currencies and jurisdictions, Stellar removes a large amount of work and cost.
Soroban is Stellar’s smart contract platform: Rust compiled to WebAssembly, with an explicit resource-metering and state-archival model. You do not need it for straightforward payments or asset issuance, which the core protocol already handles. You do need it for programmable behaviour: escrows, lending, automated distribution, subscription logic, or tokenised assets with rules attached.
An anchor is the regulated entity that converts between fiat and tokens on Stellar, the on- and off-ramp. You can integrate with existing anchors in the corridors you serve, which is faster and avoids taking on money transmission obligations, or you can operate your own where you already hold the licences. We build both, and the choice is usually driven by your regulatory position rather than by engineering.
Yes. Stellar assets support authorisation flags that require the issuer to approve each holder, revocable authorisation, and clawback for regulatory recovery. Combined with SEP-12 KYC in the wallet flow, that gives issuers a genuinely usable compliance model, which is why regulated stablecoins including USDC operate on the network.
Carefully, because in payments a retry bug is a financial incident. We build submission pipelines with managed sequence numbers, idempotency keys, fee-bump transactions for congestion, bounded retries with reconciliation against ledger state, and alerting when anything falls outside the expected window. Every payment is traceable from initiation to settled ledger entry.
A single-corridor payment flow with an existing anchor is typically 6 to 10 weeks. A full product with issuance, custom anchor endpoints, Soroban contracts, wallet integration, and compliance reporting usually runs 4 to 7 months, with partner and regulatory timelines often setting the critical path rather than engineering.
Payment products often span several chains. We build on all of these.
Tell us the corridors, assets, and compliance constraints you are working with, and we will come back with a ledger architecture and a delivery plan.