Skip to main content
Archer is a stablecoin payments platform. Every end user gets a smart wallet that holds USDC on Base, tracks its own transaction history, and can cash out to a linked bank account through Bridge. The @archermoney/sdk package embeds that experience directly into your product. Point it at your existing identity provider, and Archer takes care of authentication, wallet provisioning, balance display, history, and payouts.

​
What the SDK gives you

  • Balances and history for the end user’s Archer smart wallet, on Base or Base Sepolia.
  • Cash-out to a bank account via Bridge KYC, external accounts, and liquidation addresses.
  • Wallet intents with host-signed authorization, so the end user’s Privy-backed smart wallet only moves funds you explicitly approve.
  • Three integration surfaces:
    • @archermoney/sdk — framework-agnostic TypeScript client.
    • @archermoney/sdk/react — ArcherWorkerProvider, useArcherWorker, and a prebuilt ArcherWorkerView.
    • @archermoney/sdk/embed — script-tag widget for non-React hosts.

​
How it fits together

1

Your app authenticates the user

You already know who the user is. Give the SDK a getSubjectToken() callback that returns a signed JWT identifying that user.
2

The SDK exchanges it for an Archer session

ArcherWorkerClient.exchangeToken() calls POST /auth/token_exchange, receives a short-lived bearer token, and uses it for every subsequent request.
3

Render balances, history, and cash-out

Drop in <ArcherWorkerView />, mount the embed widget, or drive the raw client yourself. Cash-outs settle through Bridge to the end user’s linked bank account.

​
Where to go next

Quickstart

Install the SDK and render the prebuilt worker view in a React app.

Authentication

How subject tokens, tenant IDs, and session tokens work.

React provider

Wire ArcherWorkerProvider into your app and read state with useArcherWorker.

Client reference

Full ArcherWorkerClient API: account, history, Bridge, wallet intents.