# Test data

> How to get test journeys and bookings on staging, and how to trigger each scenario you need to test.

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

Staging behaves like production, but nobody drives the journeys. This guide shows how to create the
data you need to test each part of your integration. You need a staging account and an API key.

## Use fictional data

Staging is shared. Use made-up travellers with addresses at `example.com` and fictional phone
numbers, such as +44 20 7946 0123. Never use real traveller data on staging.

## Transfer companies: get a test journey

Journeys reach you only when someone books them. The portal books them for you:

1. Open **Test data** in the [workspace](https://developers.transferz.com/workspace).
2. Choose a hub, an address and the direction.
3. The portal books and pays a journey that is assigned to your company.

You receive [`journeyFleetAssignedEvent`](https://developers.transferz.com/reference/webhooks/journey-assigned) on your webhook endpoint,
and the journey appears in [Search journeys](https://developers.transferz.com/reference/transfer-companies/search-journeys). Use it to assign a
driver and a vehicle and to report progress.

Certification test cases create their own journeys when you start them; see
[Going live](https://developers.transferz.com/guides/essentials/going-live).

## Partners: run a journey

Your bookings on staging are not driven by a real transfer company. To see the events a real journey
produces, use **Send a test driver** in the [workspace](https://developers.transferz.com/workspace): a simulated transfer company
assigns a driver and a vehicle and moves the journey through its statuses, one stage at a time or
automatically. Your endpoint receives the status, driver, vehicle and position events.

## Hubs and routes

Quote requests need a hub as origin or destination. Most airports return quotes on staging.

## Payments

Paying by invoice works on staging without extra data. To pay through a payment link, use one of
Adyen's [test card numbers](https://docs.adyen.com/development-resources/test-cards-and-credentials/test-card-numbers).
The same page explains how to trigger a refused payment, with specific cards or a specific card
holder name.

## Scenarios

| To test                             | How on staging                                                                                         |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------ |
| A new journey (transfer company)    | Create a test journey in the workspace.                                                                |
| Driver and vehicle events (partner) | Book and pay, then send a test driver from the workspace.                                              |
| A cancellation                      | Partners cancel their own booking. Transfer companies: a certification case cancels a journey for you. |
| A change                            | Partners change their own journey. Transfer companies: a certification case changes a journey for you. |
| A webhook event of a given type     | Transfer companies: **Send a test event** in the workspace webhook settings.                           |
| A forged webhook                    | The certification case "Reject a forged event" sends one.                                              |
| An error                            | Send a request with a missing required field, or a page size above 100.                                |

## How long data stays

Staging has no fixed retention period. Transferz refreshes the staging data from time to time and
announces each refresh ahead of time. Your user accounts, API keys and webhook signing key are kept
across a refresh.

## Related

### Certification cases

- [Transfer company: direct assignment](https://developers.transferz.com/certification/transfer-companies/direct-assignment)
- [Partner: follow a journey](https://developers.transferz.com/certification/partners/follow-a-journey)
