# Dashboard Guides

Use dashboard walkthroughs when operators need to complete a workflow without touching API code.

{% hint style="info" %}
**Screenshot note:** Add screenshots in GitBook after each UI change stabilizes. Until then, keep the written steps accurate and outcome-based so operators can still follow the workflow.
{% endhint %}

### Create an invoice

1. Open the business dashboard.
2. Go to **Invoices**.
3. Select **New invoice**.
4. Choose the customer if one already exists, or create a customer.
5. Enter amount, token, network, expiry, and metadata.
6. Review the fee preview and minimum invoice warning if shown.
7. Create the invoice.
8. Share the hosted invoice link or payment details.

Expected result:

* The invoice appears as `pending`.
* The invoice has a hosted link and payment address.
* When payment settles, the invoice moves to `paid` or `overpaid`.

### Monitor invoice settlement

1. Open **Invoices** or **Transactions**.
2. Search by invoice ID, customer, order reference, token, or network.
3. Review invoice status.
4. Open invoice detail to view payment information.
5. Use webhook delivery logs if your backend did not update.

Expected result:

* Operators can see whether the payment is pending, confirming, settled, underpaid, overpaid, or failed.

### Create a payout route

1. Open **Payout routes**.
2. Choose chain, network, and token.
3. Name the route.
4. Add one or more recipients.
5. Enter each recipient address and percentage.
6. Confirm the total is 100%.
7. Create the route.

Expected result:

* The route becomes available for future invoices on the same chain, network, and token.
* Existing invoices are not changed by later route edits.

### Use dynamic payout recipients

Dynamic payout recipients are normally created by a trusted backend rather than manually in the dashboard. Operators should use this pattern for one-time receivers such as marketplace or on/off-ramp orders.

Expected result:

* The invoice carries invoice-specific recipients.
* PayChain creates payout withdrawals after full settlement.

### Create a withdrawal

1. Open **Withdrawals**.
2. Select token and network.
3. Enter destination and amount.
4. Review quote, fee, and gas behavior.
5. Confirm the withdrawal.
6. Track status until completed or failed.

Expected result:

* The withdrawal appears in the withdrawal list.
* Webhooks are sent for lifecycle updates.
* If sponsored gas is insufficient, the withdrawal may show as gas-blocked.

### Top up gas credits

1. Open **Billing**.
2. Review included gas remaining and prepaid gas balance.
3. Choose a top-up pack.
4. Pay the billing invoice.
5. Return to billing or settlement status.

Expected result:

* Prepaid gas balance increases.
* Gas-blocked sponsored operations resume oldest-first while credit is available.

### Review usage

1. Open **Billing**.
2. Review current plan, invoice fee, payout quota, and gas credits.
3. Review payout API withdrawal usage.
4. Review gas usage and blocked operation count.
5. Upgrade plan or top up gas credits if needed.

Expected result:

* Operators understand whether limits, gas credits, or billing state can affect outbound operations.

### Common operator mistakes

* Sharing an invoice before confirming token and network.
* Treating `confirming` as paid.
* Creating payout routes for the wrong network or token.
* Forgetting that each split recipient counts as a payout API withdrawal.
* Assuming gas exhaustion blocks receiving payments.
* Creating a withdrawal without checking destination policy.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paychainhq.io/paychainhq-documentation-page/dashboard-guides.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.