The configuration of the data for the QR-code can be defined in the <extendedproperties> tag for the pay unit.
Ten pre-defined QR-codes can be set in this way, to later be called upon from buttons, via user activity or by using the auto-click method at display page change.
The name attribute of a property must use one of the 10 pre-defined names to later be used by buttons in the UI.
Attributes
Name
| Value: | QRCodePreDefined1 to QRCodePreDefined10 |
Value
| Description: | Text string describing the value of the QR-code |
Worth to note is that ticket variables change their value during the states in the application operation and payment process. If a ticket variable is used in the extendedproperties-tag it must be a variable which is initiated at this moment. In the example below, the terminal Guid is used, accessed via variable @v1620.
type:
| Value: | Static, Dynamic |
| Description: | The QR-code configuration string is built by static text and/or by using dynamic ticket variables. Set this attribute to Dynamic when using variables in the text. |
example:
<PAYUNIT name="Ext2" type="OnlinePaymentProvider" filename="extpuQRCG.dll" mustHaveInternet="false">
<extendedproperties>
<properties name="QRCodePreDefined1" type="Dynamic" value="https://my.parkingsession.com/start/@v1620" />
</extendedproperties>
</PAYUNIT>
For UI configuration. See UI example below in chapter:
