> For the complete documentation index, see [llms.txt](https://timechain.gitbook.io/neucron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timechain.gitbook.io/neucron/go-live-checklist.md).

# Go-Live Checklist

Everything to verify before your Neucron integration handles real funds. Work through each section; nothing here is optional at production scale.

## 1. Environment and credentials

* [ ] Point your integration at the production host (`https://api.neucron.io`), not the dev host.
* [ ] Move secrets (auth tokens, app secrets) into a secret manager. Never ship them in client code.
* [ ] Rotate any credential that was ever used against a test or shared environment.
* [ ] Confirm every server call sends `Authorization`, `X-Identifier`, and, for business operations, `X-Neucron-Business-ID`.

## 2. Custody and wallets

* [ ] Choose the [custody model](https://timechain.gitbook.io/neucron/core-concepts/custody-models.md) per wallet deliberately: non-custodial for end users, server-side MPC for treasury, single-shard only for low-value operational wallets.
* [ ] Verify recovery: every MPC wallet shows a completed backup shard (`backup_status` synced). Run a test recovery with `recoverWallet` before launch.
* [ ] Separate funds by purpose: treasury, operations, collections, and app wallets. No single wallet should hold everything.
* [ ] Sweep rules decided: how and when collected revenue moves from collection wallets to treasury.

## 3. Policies and approvals

* [ ] [Approval bands](https://timechain.gitbook.io/neucron/payments/bills-payouts-and-approvals.md) configured: quorum requirements scale with amount, and no band allows unlimited unapproved transfers.
* [ ] Amount-dependent MFA enabled for material amounts.
* [ ] Velocity caps set on outgoing volume per day and per asset.
* [ ] Address whitelist enabled for treasury payouts; ad-hoc sends either disabled or tightly limited.
* [ ] Dry-run a payout with `POST /v1/payout/preview` and confirm the expected gates trigger.

## 4. Team and app permissions

* [ ] Every team member has a role with least-privilege [permissions](https://timechain.gitbook.io/neucron/core-concepts/accounts-businesses-teams.md). No shared logins.
* [ ] Bill entry and payout approval are held by different people (separation of duties).
* [ ] Each [app](https://timechain.gitbook.io/neucron/core-concepts/apps-and-whitelabel.md) has only the permissions its workflow needs; app wallets are scoped to the app.
* [ ] [Agents](https://timechain.gitbook.io/neucron/core-concepts/agentic-wallets.md), if any, operate inside an app permission envelope with human approval above a low threshold.

## 5. Compliance

* [ ] Your business KYB is at the [level](https://timechain.gitbook.io/neucron/core-concepts/compliance-levels.md) your features require: level 2 for invoicing and payouts, level 3 for fiat ramps.
* [ ] Your own regulatory obligations (KYC of your end users, licensing per custody model) are signed off by counsel.
* [ ] Audit trail access verified: you can answer "who approved this payout, under which rule" for any transaction.

## 6. Money movement end to end

* [ ] Raise a real invoice, pay it through its payment link (full and partial), and reconcile it in the customer ledger.
* [ ] Run a vendor bill through review, approval, scheduled payout, and execution on each rail you support.
* [ ] Test payment-link branding: logo and display name appear on customer-facing pages and emails.
* [ ] Test expiry and refund paths for unpaid collections.

## 7. Rails and assets

* [ ] Every rail you accept is on the [live matrix](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks.md), and you have designed around its caveats (for example, polled receives on Tron).
* [ ] Gas and fee budgeting per rail is understood and funded.
* [ ] Webhook consumers for inbound payments are idempotent and handle retries.

## 8. Observability

* [ ] Notification settings configured for the business: payout state changes, approvals pending, inbound payments.
* [ ] Dashboards or reports for treasury balances, revenue, and expense summaries are wired to the APIs.
* [ ] Alerting on failed or stale intents so approvals never silently pile up.

{% hint style="success" %}
When every box is checked, run one full day of operations with a small amount before opening the floodgates. Real money is the best integration test.
{% endhint %}