# PayGate > Payments API for websites and mobile apps: create a payment, send the buyer to a checkout URL, read the status or receive a webhook, and pay recipients out. REST API with an OpenAPI 3.1 document, plus SDKs for the web, React Native and Node/Bun. Start at the documentation (below); the API reference and the sandbox are the two lookup surfaces you will keep open while you build. PayGate is built for engineers integrating money into an existing product. Amounts are integers in minor units on the REST API. Every write takes an `Idempotency-Key`. Sandbox and live credentials exist for every app from day one, and sandbox payments never move money. ## Start here - [Documentation](https://paygate.example/docs/): the guide a person reads first — quickstart, authentication, payments, payment links, webhooks, payouts, idempotency, errors, SDK reference, and framework pages for Next.js, React, React Native, Python, PHP and Flutter. **Start here.** - [Quickstart](https://paygate.example/docs/quickstart/): a paid sandbox payment end to end, with the Node SDK and cURL. - [Payment links](https://paygate.example/docs/payment-links/): a fixed-price URL for invoices and one-off sales, with no integration. - [Frameworks and SDKs](https://paygate.example/docs/frameworks/): which surface to use, which package holds the Ed25519 key, and a request for every language without an SDK. - [Full integration guide](https://paygate.example/llms-full.txt): the same guide as plain text, for an agent to read in one pass. ## Reference - [API reference](https://paygate.example/api/): every route with its parameters, bodies, responses and credential, rendered from the OpenAPI document. The JSON stays available at `/openapi.json`, and the API serves it at `https://api.paygate.example/v1/openapi.json`. - [OpenAPI 3.1 document](https://paygate.example/openapi.json): every route with request and response descriptions. Use this as the source of truth for schemas. - [Sandbox testing](https://paygate.example/sandbox/): the decline numbers, the scenarios worth running, and a copy-ready request for every public operation. `bun run sandbox:test` in the repository proves them locally. ## SDKs - `@paygate/server`: Node and Bun backend. Holds the Ed25519 key, creates payments, releases funds, requests payouts, verifies webhooks. - `@paygate/mobile`: React Native, Expo and any JS runtime. Lists methods, starts a payment, waits for the server's verdict. Talks to your backend relay, never to PayGate directly. - `@paygate/web`: the buyer's browser. Publishable key only: lists methods and opens hosted checkout. - `@paygate/mobile/relay`: the five routes your backend exposes to the mobile app. ## Facts an agent needs first - Environments: `sandbox` (simulator, no real money) and `live`. Reads are scoped to the credential's environment. - Base URL: `https://api.paygate.example`. - Payment statuses: `created`, `requires_action`, `processing`, `succeeded`, `failed`, `cancelled`, `expired`. - Settlement is only reported after the provider is queried. A redirect, a deep link or a buyer's word is never proof of payment. - Webhooks are signed: `x-paygate-signature: t=,v1=`, HMAC-SHA256 over `${t}.${rawBody}`, five-minute tolerance. ## Optional - [Console](https://console.paygate.example): operator view for payments, payouts and health. - [Health](https://api.paygate.example/healthz): liveness probe.