Skip to content

docs(headless-sdk): refactor implementation for zero-config AppKit #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
enesozturk merged 3 commits into from
Jul 9, 2026
Merged

docs(headless-sdk): refactor implementation for zero-config AppKit #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c4b6986
docs(headless-sdk): refactor implementation for zero-config AppKit
enesozturk Jul 8, 2026
71525bc
docs(headless-sdk): address PR feedback + point examples to new repo
enesozturk Jul 8, 2026
625410d
docs(headless-sdk): clarify Signer seam has one entrypoint
enesozturk Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions payments/psps/headless-sdk/how-it-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,12 +69,12 @@ The five seams the runtime depends on:
| ---------------- | ------------------------------------------ | ---------------------------------------------------- |
| `Transport` | Engine HTTP calls | `pay-core` `createHttpTransport` → your server route |
| `WalletProvider` | connect / accounts / provider / switch | `pay-appkit`, or your own wallet integration |
| `Signer` | sign a payment option's wallet-RPC actions | `pay-state` signing strategies over the wallet seam |
| `Signer` | sign a payment option's wallet-RPC actions | `pay-appkit` `createAppKitSigner` — one call (wraps `pay-state`'s signing; drop to its raw strategies only for a custom, non-AppKit wallet) |
| `Clock` | intervals + page visibility (for polling) | browser timers (the SDK ships a default) |
| `Telemetry` | analytics breadcrumbs | your analytics pipeline (optional) |

<Note>
`@walletconnect/pay-state` ships browser-ready `Clock` and `Telemetry` defaults (`browserClock`, `noopTelemetry`). In practice a React/Next.js gateway wires three seams itself — a `Transport` (pointed at your server route), a `WalletProvider` (the AppKit adapter), and a `Signer` (built from the wallet) — and reuses `browserClock` for the rest. `Telemetry` is optional.
`@walletconnect/pay-state` ships browser-ready `Clock` and `Telemetry` defaults (`browserClock`, `noopTelemetry`). In practice a React/Next.js gateway wires just the `Transport` (pointed at your server route); the `WalletProvider` and `Signer` come ready-made from `pay-appkit` (`<PayAppKitProvider>` + `createAppKitSigner`), and it reuses `browserClock` for the rest. `Telemetry` is optional.
</Note>

## The Engine API key never reaches the browser
Expand Down
Loading