> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/prepay-car-parking/understanding-the-prepay-car-parking-feature.md).

# Understanding the Prepay Car Parking feature

### How does Prepay work?

One of the following prepay options can be used:

* **Fixed periodic payment**

A Cardholder pays a fixed amount of money for a defined period of time, (e.g. an amount is deducted from a Cardholder's salary/wage per month). The Command Centre operator then activates the Cardholder's Car Parking Competency for the defined period of time. The Cardholder can then access the paid car parks during the defined period of time.

* **Prepay**

A Cardholder purchases car parking credits, (e.g. number of 'parks' allowed). The Command Centre operator then activates the Cardholder's Car Parking Competency and updates the Cardholder's limited credit amount. The Cardholder can then access the paid car parks, until their credit runs out.

### When is the Cardholder charged?

A Cardholder is charged if:

* The Cardholder has the required Car Parking Competency, and
* The Cardholder has limited credit on the Car Parking Competency, and
* The Cardholder's car has stayed in the managed car parks for more than the free parking duration, and
* When the Cardholder exits the managed car parks, the Cardholder is found not having been charged within the previous 'charged parking duration' period.

### Limitations

* One Car Park can belong to one Car Park Group only. This restriction is not suitable for managing shared prepay car parks that may serve multiple tenant companies, where each company is charged differently.

  A car parking credit is a whole unit only. If cash value is to be used as credit, the value should be entered in the unit of cents.
* As long as a prepay Cardholder has the active car parking credit Competency, the Cardholder is allowed access to paid car parks even when the Cardholder does not have the minimum required car parking credit.
* For long stays, (e.g. one month), the Cardholder's Competency credit is deducted only once (the 'Credit to deduct' value) when the Cardholder exits the car park. The credit deduction event details, include a warning, indicating the stay time has been longer than the charged parking duration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/prepay-car-parking/understanding-the-prepay-car-parking-feature.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
