# 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-18

Before your integration runs in production, it passes certification on staging. This guide explains
certification and lists what to do after approval.

## How certification works

Certification proves on staging that your integration does what it must. The requirements are
public: every test case on your track says what to do and how the portal checks it.

- There is one **track** for partners and one for transfer companies.
- **Core** test cases are required for everyone on your track.
- **Modules** cover optional capabilities, such as payment links for partners. You choose the
  modules that match what you build, and can add more later.
- Each **test case** says what to do and how the portal checks it.
- **Transfer companies** certify in three sections, one after the other: Direct assignment; Driver,
  vehicle and tracking; Cancelling journeys. Each section creates its own test journeys. After each
  change the portal makes, your endpoint answers the webhook event with a `2xx` within 5 minutes, and
  you answer one question about what your system received. Set your webhook URL first.

The portal checks most cases itself, from your traffic on staging:

| Check                | What the portal looks for                                                                         |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| Request observed     | Your system sent the expected call for the case's journey or booking, and got a success response. |
| Webhook acknowledged | Transferz delivered the event and your endpoint answered `2xx`.                                   |
| Proof of receipt     | You enter a value that only your endpoint received.                                               |
| Rejection            | The portal sends something invalid, such as a forged webhook, and your system refuses it.         |
| Resulting state      | The journey or booking ended in the expected status.                                              |
| Declaration          | You confirm something the portal cannot see, optionally with a screenshot.                        |

Calls from the portal's own "Try it" console do not count: the calls must come from your system.
Starting a case creates or picks the journey or booking it applies to, so earlier traffic cannot
pass it. You can retry a case as often as you need.

When core and your modules have passed, submit for review. Transferz reviews your submission within
2 working days, and approves it or asks for changes.

## Before you submit

- Your system verifies [webhook signatures](https://developers.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.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

After approval your certificate page shows this checklist. Tick each item as you do it; the portal
does not check them.

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

## Whom to contact

For technical and integration questions, use [Support](https://developers.transferz.com/support) in the workspace. For business
questions and escalations, contact your destination manager at Transferz.

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

## Related

### Certification cases

- [Authenticate](https://developers.transferz.com/certification/partners/authenticate)
