# Pulse Collect

## Docs

- [Create a session](https://docs.pulseshiga.io/backend/create-session.md): Mint a single-order collection session with pulse.collectionSessions.create — the naira and USD gates, idempotency keys, and the returned shape.
- [Error handling](https://docs.pulseshiga.io/backend/errors.md): The typed errors @pulsebyshiga/node throws, and an optional pattern for mapping them into your own error layer.
- [Install & initialize](https://docs.pulseshiga.io/backend/install.md): Install @pulsebyshiga/node and construct the client once — the server-only component that holds your API key.
- [Onramp (buy crypto)](https://docs.pulseshiga.io/backend/onramp.md): The live engine-direct flow: quote, create an onramp order, show the virtual account, and track it to funded.
- [Orders](https://docs.pulseshiga.io/backend/orders.md): Look up ground truth on a collection order — retrieve, list, and re-lock an expired quote.
- [Preview a rate](https://docs.pulseshiga.io/backend/preview-rate.md): Show a live rate with pulse.rates.preview — no order created — proxied through a thin backend route for the client.
- [Webhooks](https://docs.pulseshiga.io/backend/webhooks.md): Verify and de-duplicate signed webhook deliveries, and credit a customer only off a verified disbursement.completed event.
- [Amounts and precision](https://docs.pulseshiga.io/concepts/amounts.md): How amounts are represented across Pulse Collect, and how a deposit is judged against the quote.
- [Assets and networks](https://docs.pulseshiga.io/concepts/assets-and-networks.md): The stablecoins Pulse Collect accepts, and the two network enums whose casing tells you which surface you're on.
- [Fiat gates](https://docs.pulseshiga.io/concepts/fiat-gates.md): Where settled fiat lands — the naira and USD gates — and which direction the money moves.
- [Order lifecycle](https://docs.pulseshiga.io/concepts/order-lifecycle.md): The states a collection order moves through, the edge states, and the one event you credit on.
- [Rates and quotes](https://docs.pulseshiga.io/concepts/rates-and-quotes.md): How a rate is previewed, locked, and re-locked — and why the rate is all-in with no separate fees.
- [Get your API keys](https://docs.pulseshiga.io/credentials.md): How to obtain sandbox and live Pulse credentials, and where each key is used.
- [How it works](https://docs.pulseshiga.io/how-it-works.md): Sessions and orders, fiat gates, assets and networks, quote locking, and the money-moment lifecycle.
- [Pulse Collect](https://docs.pulseshiga.io/index.md): Collect stablecoin from your users and settle to fiat — one backend integration, your brand on every screen.
- [Quickstart](https://docs.pulseshiga.io/quickstart.md): Zero to a working sandbox integration: create a session, render the payment moment, and credit off the webhook.
- [Changelog](https://docs.pulseshiga.io/reference/changelog.md): Release notes for the Pulse Collect SDKs.
- [Contract status](https://docs.pulseshiga.io/reference/contract-status.md): Which parts of this reference are reconciled against the live engine and which are proposed shapes still being finalized.
- [Frontend packages](https://docs.pulseshiga.io/reference/frontend.md): Props and handles for the browser and native SDKs — @pulsebyshiga/collect-js, @pulsebyshiga/collect-react, and @pulsebyshiga/collect-react-native.
- [Rate limits & operations](https://docs.pulseshiga.io/reference/limits.md): Retries and 429 handling, amount precision, amount_status, and how API changes are communicated.
- [@pulsebyshiga/node](https://docs.pulseshiga.io/reference/node.md): Server-side SDK reference — client construction, collection sessions and orders, rate preview, webhook verification, error classes, and the shared wire types.
- [REST API (raw HTTP)](https://docs.pulseshiga.io/reference/rest.md): A stopgap raw-HTTP reference for non-JavaScript backends until the OpenAPI spec is published.
- [Webhook events](https://docs.pulseshiga.io/reference/webhook-events.md): Every signed lifecycle event and its payload shape, as verified and typed by pulse.webhooks.verify / verifyOnce.
- [Choose a rendering model](https://docs.pulseshiga.io/render/choose-a-model.md): Four ways to render the payment moment — compare credential, runtime, and engineering effort before you pick one.
- [Dashboard configuration](https://docs.pulseshiga.io/render/dashboard-config.md): Set theme, copy, enabled networks/assets, and flow once in the Pulse dashboard — no frontend deploy required.
- [Embedded iframe (Tier A)](https://docs.pulseshiga.io/render/embedded-iframe.md): Mount the payment surface inside a Pulse-controlled iframe on your own page, driven by a session token.
- [Headless / API (Tier C)](https://docs.pulseshiga.io/render/headless-api.md): Build your own UI end to end against the order object — no Pulse-rendered surface at all.
- [Hosted page (Tier B)](https://docs.pulseshiga.io/render/hosted-page.md): The same embed served as a full white-label page, for partners wanting the least engineering lift.
- [In-app component](https://docs.pulseshiga.io/render/in-app-checkout.md): The in-app PulseCheckout component renders in your React tree, driven by your API key — for trusted runtimes only.
- [Theming & copy](https://docs.pulseshiga.io/render/theming.md): Every theme token, string placeholder, the attribution toggle, density, and the formatting helpers that keep your screens in sync.
- [Supported stablecoins](https://docs.pulseshiga.io/supported-stablecoins.md): The stablecoins and networks Pulse Collect supports, and what's coming next.
- [Embed deployment & CSP](https://docs.pulseshiga.io/testing/embed-deployment.md): The embed is Pulse-hosted — the Content-Security-Policy, frame-ancestors, and CNAME details that govern how it's framed inside your page, and what to configure if you host Tier B on your own subdomain.
- [Go-live checklist](https://docs.pulseshiga.io/testing/go-live.md): Everything to verify before switching from sandbox to production.
- [Observability](https://docs.pulseshiga.io/testing/observability.md): How to get visibility into your Pulse Collect integration: your own logging around the SDK, identification headers, and correlating with Pulse support.
- [React Native checklist](https://docs.pulseshiga.io/testing/react-native.md): Validate @pulsebyshiga/collect-react-native in your own app — install, mint a sandbox session, render the payment surface, and verify the lifecycle before you ship.
- [Sandbox](https://docs.pulseshiga.io/testing/sandbox.md): Point the SDK at a sandbox key and simulate the full collection lifecycle — deposit, confirmation, and disbursement — without moving funds.
- [Why Pulse](https://docs.pulseshiga.io/why-pulse.md): A stablecoin-to-fiat settlement layer: one backend integration, your brand on every screen, and settlement you can build a ledger on.