Introduction

Stridge is crypto payment infrastructure for fintechs. One gateway accepts deposits on any supported chain, picks the cheapest route automatically, and settles to whichever destination chain and token you choose. The same gateway powers withdrawals.

Everything in these docs sits on top of that gateway. You pick a surface — React, TypeScript, or raw HTTPS — and read or write through the same contract.

What you can build

• Cross-chain checkout. Accept any token on any chain and settle to a single destination asset, like USDC on Arbitrum.
• Withdrawals. Move funds out of your treasury on any source chain to a customer's chosen network and token.
• Multi-user deposit ledgers. Provision one Universal Deposit Address per customer and reconcile every deposit through webhooks.

Integration surfaces

Three surfaces share the same gateway and the same Universal Deposit Address model.

The Kit is built on the SDK; the SDK wraps the HTTP API. Drop down a layer when you need more control.

Core concepts

• Gateway key. Browser-safe identifier scoped to a project. The Kit, the SDK, and the HTTP API all authenticate with this header.
• API key. Server-side secret for the REST endpoints (payouts, deposits, settlements). Never ship to the browser.
• Universal Deposit Address (UDA). One persistent multi-chain address per owner. Every deposit on every supported chain settles to the destination configured at create time.
• Settlement. The canonical record of one deposit moving from its source chain to the destination chain and token.

Where to start

• Getting started — generate keys, pick a surface, make your first call.
• Gateway Kit — mount <StridgeProvider /> and render a deposit dialog.
• Universal Deposit Addresses — the settlement model that powers every flow.
• Supported networks — the chains, identifiers, and tokens Stridge routes through.