Getting started

Stridge ships three integration surfaces over the same gateway. Pick the one that matches your stack — they all settle through the same Universal Deposit Address model.

Surface	Best for
Gateway Kit (`@stridge/kit`)	React apps that want a drop-in deposit / withdraw UI.
TypeScript SDK (`@stridge/sdk`)	Backends, workers, or non-React frontends needing typed gateway access.
REST API	Any language. Direct HTTPS, full control.

Get a key

Create an account in the Stridge Dashboard and generate the right key for your surface:

Gateway key (X-Gateway-Key) for the Gateway Kit, TypeScript SDK, and the Gateway HTTP API. Browser-safe when scoped to a public origin.
API key (X-API-Key) for REST endpoints — payouts, deposits, settlements, networks. Always server-side.

Mount the React Kit (fastest path)

pnpm add @stridge/kit

App.tsx

import { StridgeProvider } from '@stridge/kit'
import { DepositDialog } from '@stridge/kit/deposit/dialog'

export function App({ customer }: { customer: `0x${string}` }) {
  return (
    <StridgeProvider
      gatewayKey={process.env.NEXT_PUBLIC_STRIDGE_GATEWAY_KEY!}
      asset={{ chain: 'bsc', symbol: 'USDC' }}
      flows={{ deposit: { destination: { address: customer } } }}
    >
      <DepositDialog />
    </StridgeProvider>
  )
}

Open the dialog with useDeposit().open() from any descendant. Full setup: Gateway Kit.

Or call the REST API

curl -X GET 'https://api.stridge.com/v1/uda' \
  -H 'X-API-Key: your_api_key_here'

const res = await fetch('https://api.stridge.com/v1/uda', {
  headers: { 'X-API-Key': process.env.STRIDGE_API_KEY! },
})

Gateway Kit — React widgets and headless hooks.
TypeScript SDK — typed client for backends.
API reference — every endpoint and payload.

Warning

Never ship a Stridge API key (X-API-Key) in client-side code. For browser apps, proxy REST calls through your backend, or use the Gateway Kit which uses a public gateway key instead.

FAQ

Was this page helpful?

Getting started

Next

FAQ