---
title: "Go live"
description: "How to build and test a Nodu integration in the sandbox, recommended integration practices, and how you then get access to production."
url: "/guides/get-started/go-live/"
index: "/llms.txt"
---

# Go live

You build and test your whole integration in the sandbox, Nodu's test environment, before you use production. Nodu gives you access to production after you have onboarded a customer and made at least one transfer in the sandbox with the integration flow agreed with Nodu.

## Build the agreed integration flow in the sandbox

First, agree with Nodu on the final functionality that your integration will use:

- **Onboarding.** The [onboarding model](/guides/customers/onboarding-models/index.md). With API onboarding, also the exact list of the fields and documents that an application needs.
- **Currencies and rails.** The currencies and the payment rails on each side of a transfer: see [Payment channels](/guides/transfers/payment-channels/index.md).
- **Other features.** For example, [Nodu wallets](/guides/nodu-wallets/balances-and-wallet-scopes/index.md) and [relays](/guides/relays/index.md).

Build the agreed integration flow in the sandbox. Before requesting production access, complete this checklist:

- [ ] Onboard individual and business customers, as your integration flow includes them. See [Test onboarding in the sandbox](/guides/sandbox/test-onboarding/index.md).
- [ ] Make transfers from and to every rail and currency of your integration flow, from the quote to the result. See [Simulate funding in the sandbox](/guides/sandbox/simulate-funding/index.md).
- [ ] Test proof of ownership for crypto wallets when it applies to your transfers. See [Simulate crypto wallet verification](/guides/sandbox/simulate-wallet-verification/index.md).

Use the sandbox to find and resolve problems before real customers and funds are involved.

Build the handling of failed transfers, and of the customer statuses `suspended` and `blocked`, from their descriptions: see [Track and cancel a transfer](/guides/transfers/track-a-transfer/index.md) and [Suspended and blocked customers](/guides/customers/resubmission-and-rejection/index.md#suspended-and-blocked-customers).

## Recommended practices

### Make requests safe to repeat

- **Idempotency keys.** Send an `Idempotency-Key` header with every `POST` request that creates an object or moves money. Store the key and the exact body before you send the request: see [Idempotency](/guides/api-basics/idempotency/index.md).
- **Client reference ids.** Send your own identifier as `clientReferenceId` when you create a customer, an external account, a counterparty, a relay or a wallet. It helps you match API objects to your records and complements idempotency handling: see [Idempotency](/guides/api-basics/idempotency/index.md#use-clientreferenceid-with-idempotency).
- **Timeouts.** Repeat a request that timed out with the same key and the same body. A new key can create a second object.
- **Errors.** Handle errors by `status`, `code` and `rule`. Do not compare the text of `title` or `detail`. Handle a `rule` that you do not know: see [Errors and rule codes](/guides/api-basics/errors-and-rule-codes/index.md).

### Handle webhooks

[Receive and verify webhooks](/guides/api-basics/webhooks/index.md) explains each of these items.

- **Signatures.** Verify the signature of every webhook before you act on it.
- **Duplicates and order.** Record the `id` of each event. Skip an event that you have already processed. Events can arrive more than once. They can also arrive out of order.
- **Unknown types.** Return `2xx` for an event type that you do not handle.
- **Reconciliation.** Do not depend on webhooks alone. Compare your records with the API from time to time: see [Reconcile with the list](/guides/transfers/track-a-transfer/index.md#reconcile-with-the-list).

### Handle every status and state

- **Customers.** Offer transfers only when the customer has `status=active`. Handle a request for more information, a final rejection, and the statuses `suspended` and `blocked`: see [How onboarding works, and customer statuses](/guides/customers/how-onboarding-works/index.md#statuses) and [Resubmission and rejection](/guides/customers/resubmission-and-rejection/index.md).
- **Payment channels.** Handle `inactive`, `pending` and `suspended`: see [Payment channels](/guides/transfers/payment-channels/index.md#channel-statuses).
- **Transfers.** Handle every `state`, including `info_required`, `undeliverable`, `returned`, `refunded`, `canceled` and `error`: see [Track and cancel a transfer](/guides/transfers/track-a-transfer/index.md) and [Handle the `info_required` state](/guides/transfers/handle-a-transfer-that-needs-action/index.md#handle-the-info_required-state).
- **External accounts.** Handle `update_required` and `archived`: see [External accounts and counterparties](/guides/transfers/external-accounts/first-party-and-third-party-accounts/index.md#statuses).

## Request access to production

When your integration works in the sandbox:

1. **Ask Nodu for a production API key.** Store it in a secret manager, and call the API from your backend only: see [Environments and API keys](/guides/get-started/environments-and-api-keys/index.md#get-a-key) and [Authentication](/guides/api-basics/authentication/index.md#keep-api-keys-safe).
2. **Give Nodu the URL of your production webhook endpoint,** and the list of event types that you act on. Nodu registers the endpoint. You receive its signing secret separately. Store the secret as carefully as an API key.

Production starts empty: none of your sandbox customers, external accounts, transfers or other objects exist there. You can keep using the sandbox for later tests and development.

A suggestion for production: start with one customer and one transfer of a small amount. Follow the transfer to its outcome before you offer this transfer flow to all your customers.

## Next steps

- [Environments and API keys](/guides/get-started/environments-and-api-keys/index.md): the production base URL, and what to know about keys.
- [Track and cancel a transfer](/guides/transfers/track-a-transfer/index.md): what you do in each transfer state.
- [Test onboarding in the sandbox](/guides/sandbox/test-onboarding/index.md): produce each verification outcome before you go live.
