> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paychainhq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

# Getting Started Journey

Use this sequence to move from first setup to a safe production integration.

<Info>
  **Best first path:** Create a fixed amount invoice, verify the webhook with the raw request body, fetch the canonical invoice, then fulfill from invoice state.
</Info>

## 1. Create a business

What you do: create a PayChain business in the dashboard.

Expected result: you can access sandbox, configure settings, and create test resources.

## 2. Understand sandbox vs live

What you do: test in sandbox before requesting live approval.

Expected result: sandbox credentials, live credentials, webhook secrets, and balances stay separate.

<Warning>
  **Environment note:** Sandbox success does not mean live access is approved. Treat sandbox and live credentials as separate systems.
</Warning>

## 3. Choose a plan and understand fees

What you do: review plan price, invoice fee, minimum fee, payout quota, and gas allowance.

Expected result: your team understands how invoice volume, payout usage, and sponsored gas affect cost.

## 4. Create API keys securely

What you do: create standard keys for collection and reads, and payout keys only when fund movement is required.

Expected result: keys live only in server-side secret storage.

## 5. Create a customer or invoice

What you do: create an invoice through the dashboard, SDK, or REST API.

Expected result: the payer receives a hosted invoice or payment details for the correct token and network.

## 6. Receive payment and verify webhook

What you do: wait for signed webhook events and fetch the canonical invoice before fulfillment.

Expected result: customer payment status is reconciled safely.

<Warning>
  **Fulfillment note:** Do not release customer value from an unverified webhook payload or from raw wallet balance alone. Verify the webhook and fetch the canonical invoice.
</Warning>

## 7. Route payouts or create withdrawals

What you do: attach a payout route, send dynamic payout recipients, or create a withdrawal.

Expected result: payout movement follows approved policies, quotas, and gas-credit rules.

## 8. Monitor usage

What you do: watch billing, gas credits, payout quota, balances, transactions, and webhooks.

Expected result: your team sees problems early and can top up gas credits before sponsored outbound actions pause.

## 9. Go live

What you do: complete production checks for credentials, webhooks, payout policy, rate limits, billing, support, and monitoring.

Expected result: payments can be accepted and operated safely in live mode.