Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.unseen.finance/llms.txt

Use this file to discover all available pages before exploring further.

Architecture showed who talks to whom. Here every request shares the same baseUrl (or equivalent network on the server SDK)—if these drift between browser and backend, checkout and verification will disagree in subtle ways.

​
Server SDK (@unseen_fi/sdk)

UnseenClient accepts:
  • apiKey (required)
  • network: "mainnet" | "devnet" (defaults to "devnet")
  • baseUrl: optional override for self-hosted or staging gateways
When baseUrl is omitted, the SDK uses per-network defaults (currently aligned with Unseen deployment — check your installed version for exact URLs).
networkTypical default baseUrl (when not overridden)
mainnethttps://unseen.finance
devnethttp://unseen.finance
All REST calls are made to {baseUrl}/api/v1/... (and /api/v1/merchants/me for me()).

​
React UI (@unseen_fi/ui)

<UnseenProvider>:
  • baseUrl defaults to https://unseen.finance
  • defines the origin used for browser fetch calls to Unseen’s HTTP API
This is not always identical to the server SDK default in every setup. If your app talks to a staging stack, set baseUrl on the provider and the same host in your server SDK via baseUrl or network so both sides hit the same gateway.

​
Choosing a pattern

  • Production: same logical environment for UI + server; webhook URL registered in the merchant dashboard.
  • Local development: run your app against devnet or a local gateway; pass explicit baseUrl on both SDK and provider if defaults do not match your stack.
Next: Payment lifecycle