Charging Policies (beta)

A charging policy holds the price of a charging session and the rules that decide who is allowed to charge at that price.

How the pieces fit together

• A policy carries one or more tariff rules. Each rule holds a tariff configuration (the price components) and, optionally, the customer groups it applies to. A rule with an empty customerGroupIds applies to every token presented.
• A policy is applied to connectors by associating it with one or more charging groups through associatedChargingGroupIds. A charging group selects connectors individually, or by the locations or accounts they belong to. A provider policy with an empty associatedChargingGroupIds applies to every charging station instead; a provider can have only one such policy, and account-owned policies (/mine) never apply this way.
• When a token is presented at a connector, the platform collects the charging groups that contain that connector and evaluates the policies associated with them. Within a policy, tariff rules are evaluated in the order they were supplied. The first rule that matches the token both authorises the session and prices it.
• To give one card a different price (a negotiated rate, or free charging), put that card in a customer group and add a rule naming that group above the open rule in the same policy. The card matches the first rule and gets its price; every other card falls through to the open one. Keep both prices in one policy rather than splitting them across policies on overlapping charging groups, because the order in which separate policies are evaluated is not part of this contract.

This API is in preview. It is functional and safe to build against, but breaking changes may still occur; any breaking change is announced in advance.