> ## Documentation Index
> Fetch the complete documentation index at: https://api.corpay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test environment guide

This guide explains how to use the Fleet API's test environment to test an implementation.

### **Card ordering and fulfilment in test environment**

In the production environment, when a card is ordered, the card is physically produced and then shipped to the customer. Since this physical process does not happen in test environment, Fleet API simulates the production and fulfilment process automatically. This allows the full card lifecycle to be tested in test environment without waiting for actual card production or shipment.

#### **Card ordering**

Card orders can be created in test environment using the Fleet API in the same way as in production. After a card has been ordered, it will initially have the status `ordered`. This status indicates that the card order has been received, but the card has not yet been fulfilled.

#### **Simulated card fulfilment**

In production, card fulfilment happens after the card has been produced and shipped. In test environment, this process is simulated once per day. The fulfilment simulation runs daily at 13:30 CET. During this process, all cards that previously had the status `ordered` are updated to `fulfilled`.

This means that if a card is ordered before the daily fulfilment simulation runs, it should become fulfilled during the next scheduled test environment fulfilment job.

#### **Card activation**

Cards in test environment have an activation period based on the card creation date. A card becomes active two days after the card creation date. Cards are usually activated early in the morning, around 00:30 CET. After the card has become active, it takes approximately another 30 minutes before the card can be used for charging sessions.