| Note: The flows described below are implemented in the Standard configuration. If the standard flows do not support your business case contact Flowbird Support to get help with implementing your needs. |
The payment panels are displayed when the customer shall start payment and during the payment process. The payment panels are divided into groups based on the payment service selection during the PAT-selection phase of the purchase.
Different payment panels will be displayed depending on the setup of the payment service selected during the PAT-selection (or they are selected automatically by the system).
A terminal can contain different payment services, each with a different setup (for example prepayment with code input and prepayment without code input), which means that the user interface can contain display panels for these groups.
The available groups of payment service display panels are:
Payment service panel groups |
Description |
|---|---|
“Prepay Easy” |
Normal pre-payment without requirement of input of customer identity, like license plate number, during the purchase. |
“Prepay Code” |
Pre-payment with customer identity input, such as license plate number, during the purchase. |
“Prepay Easy Step” |
Pre-payment used with external pay units. It is required that the purchase has started and that the amount to pay is determined before a debit request is sent to the pay unit. |
“Prepay Code Step” |
Pre-payment used with external pay units. It is required that the purchase has started and that the amount to pay is determined before a debit request is sent to the pay unit. Input of customer identity, license plate number for instance, is also required during the purchase. |
“PostPay” |
Payment when leaving the parking area |
The unique panel names are preceded by a prefix defining the group to which the panels belong. Hence, “Prepay Easy” panels will always have the prefix “PrePay_Easy_” and “Prepay Code” panels will always have the prefix “PrePay_Code_”, both followed by the unique panel name.
All groups contain one common start panel named "StartPanel". This is always displayed after the PAT-selection has been finished by the customer, or automatically by the terminal, but before the payment has started.
For setups that require customer identity input during the purchase, the global panel “CodeInputPanel” will be displayed before the start panel.
For the Prepay Easy panel group the full name of the start panel is set to Name=“PrePay_Easy_StartPanel” in the property when that particular panel is defined in the ui.xaml file.
Example definition of “PrePay_Easy_StartPanel” for the TFT display:
Example
<TFT:Panel Name='PrePay_Easy_StartPanel'>
<Controls>
- - -
</Controls>
</TFT:Panel>
The other panels required within a payment service group are named with an index such as Panel1, Panel2, etc. The number of panels to be set up to create a complete user interface depends on the type of payment service.
Sections Prepay Easy, Prepay Code, Prepay Easy Step, Prepay Code Step, and PostPay describe the difference between the panels in each payment service panel group and the stage at which each panel is displayed.
the sections Pay by Space and Purchase Pre-Requisites describe additional flows that can be added to the Prepay and Postpay flows.
| It is very important that a payment service has got all panels defined. Otherwise, the software will not find the correct panels and will not be able to present the expected panels correctly, which might cause unexpected results. |
