# Certification requirements: transfer company track

Certification proves on staging that an integration does what it must before it goes live. Every company on this track passes the core cases and the cases of the modules it selects; a Transferz reviewer approves the result. Reviews usually take 2 working days.

## How cases are verified

- **Request observed**: Your own system sent the expected call to staging for this case's journey or booking, with the required fields, and got a success response.
- **Webhook acknowledged**: Transferz delivered the event and your endpoint answered with success.
- **Proof of receipt**: You enter a value that only your endpoint received. The portal hides it on screen.
- **Rejection**: The portal sends something invalid and your system must refuse it.
- **Resulting state**: The journey or booking on staging ended in the expected state.
- **Declaration**: You confirm something the portal cannot observe, optionally with a screenshot. The reviewer judges it.

## Core

The cases every transfer company must pass.

- [Direct assignment](https://developers.transferz.com/certification/transfer-companies/direct-assignment) (Webhook acknowledged, Proof of receipt): Proves your system receives a journey that Transferz assigns directly to your company, follows its changes and handles its unassignment, and that it reads the details correctly.
- [Driver, vehicle and tracking](https://developers.transferz.com/certification/transfer-companies/driver-vehicle-and-tracking) (Webhook acknowledged, Request observed): Proves your system assigns a driver and a vehicle to a journey and, if you use your own system instead of the Transferz Driver App, reports the driver's progress and position until the journey is completed.
- [Cancelling journeys](https://developers.transferz.com/certification/transfer-companies/cancelling-journeys) (Webhook acknowledged, Declaration): Proves your system handles a free cancellation and a cancellation that still pays you.
