> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://bcdtravel.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://bcdtravel.ferndocs.com/_mcp/server.

# Making test reservations

Please follow all procedures detailed below to ensure you produce only test bookings. BCD Travel is not responsible for any live bookings you create during the testing process.

## Important rules

* Always make test bookings for dates **at least a few months in the future**.
* Always read the **cancellation policy** before booking and verify that you are booking outside of the cancellation policy. Never book non-refundable fares.
* Avoid booking over a **holiday season** where inventory may be in high demand.
* Don't use **fake-looking traveler information** (names, emails) for test bookings.

## Fake booking tests

This procedure will test your API integration against our API core but will cut off prior to supplier interaction, producing a fake booking. Your `pnr_id` will be `000000` and your `supplier_confirmation_number` will be `FAKE`.

You must use **`4111111111111111` VISA card** for the reservation to produce a true test booking. Any other card will result in a real reservation.

## Live booking tests

If you are at the integration stage that requires real supplier interaction:

* The only true live test is to **use your own credit card** to produce a live booking.
* **Non-refundable bookings** will NOT be refunded by suppliers.
* Use fake bookings for all development activities. Use live booking testing at the **very final stage**.
* Keep live tests to an **absolute minimum**.
* Reservations made with "test" credit cards obtained elsewhere could be treated as fraud by suppliers.