# Going live

> What to check before launch, the go-live checklist, and whom to contact before and after launch.

Section: Essentials · Last updated: 2026-11-15

Before your integration runs in production, you build and test it on staging. When it is ready,
Transferz gives you production credentials. This guide lists what to check before you go live and
what to do then.

## Before you go live

- Your system verifies [webhook signatures](https://developers.test.transferz.com/guides/essentials/webhooks#verify-the-signature) and
  answers `401` to a forged event.
- Webhook processing is idempotent and does not block on slow work.
- You log the `X-Request-ID` of each call.
- You handle every [journey status](https://developers.test.transferz.com/guides/essentials/constants#journey-status), including ones you
  do not expect.
- API keys and signing keys are in a secret store, not in code.

## Go-live checklist

Work through this list when Transferz confirms that you can go live. The portal does not check the
items.

1. Change the base URLs to production; see [Environments and base URLs](https://developers.test.transferz.com/guides/get-started/environments).
2. Obtain production credentials from Transferz.
3. Create a production API key.
4. Register your production webhook endpoint and store the production signing key.
5. Make a first booking in production and follow it closely.

> **To be confirmed by Transferz:** How production credentials are issued and how the production webhook is registered is still to be
> confirmed by Transferz.

## Whom to contact

> **To be confirmed by Transferz:** The support contact for integration questions and after go-live is still to be confirmed by
> Transferz. Until then, contact the Transferz person who arranged your access.

When you report a problem, include the request ID, the time, the endpoint and the response. Never
send an API key or signing key.
