When a Terminal is configured for Ongoing Purchases the end user is requested to enter an identifier into the terminal. Commonly this identifier is a Vehicle Registration number or License Plate.
depending on the configuration this Identifier is than sent to WebOffice who in its turn forwards the data to a service provider. The service provider can optionally approve or decline the purchase. This information is sent back all the way to the terminal. If the terminal is configured to wait for the result it will accept or cancel the purchase.
Possible configurations:
•Asynchronous: The CWT sends the purchase data after the purchase is finished. This means that the CWT does not wait for the response from the service provider.
•Synchronous: The service provider must approve the purchase before a ticket can be printed
•Synchronous with fall back: This method works the same as synchronous but when the terminal cannot access WebOffice it will fall back to locally stored values to print on the ticket
Note: |
These options are set in OngoingPurchaseDatabaseReplication in the PAYMENT element and/or in OngoingPurchaseDatabaseReplication in the PAYMENTSERVICE element.
The ongoingPurchaseDatabaseLocation attribute configures where the data will be sent
The following attributes are set in PAYMENTSERVICE element:
•ongoingPurchaseRejectTicket is used to set if a reject ticket shall be printed
•ongoingPurchaseFallbackTicket is u to set if a fallback ticket shall be printed
•ongoingPurchaseDefaultDescription contains the description to print on fallback
•ongoingPurchaseDefaultExternalId containd a default ID to print on fallback
