The Wallet external pay unit must use a PAYMENTSERVICE with the following parameters:
lockCurrentPATAtCardInserted="true"
startPurchaseWithCard="false"
ongoingPurchaseDatabaseReplication="None"
userIdentifier="Code"
decreaseLeftToPayWhenCashIsPaid="false"
ticketMode="TicketAfterAccept"
You can also configure the system so that user must actively choose a payment service (see “PAT selection” in CWT “Software Configuration Handbook”). This is recommended for Top-Up.
•To allow payment of the remaining amount with cash the decreaseLeftToPayWhenCashIsPaid attribute must be set to "true".
You also must use the click function OnAcceptWithBalanceCheck to verify if additional payment in cash or with card must be done.
If the click function OnAccept is used the parker does not get the possibility to fill up the missing amount in the Wallet with cash. In that case she can only fill up with a Card payment.
•To be able to print a combined ticket/receipt the attribute ticketMode in the PAYMENTSERVICE element must be set to "TicketAfterAccept". Otherwise the receipt part will be blank.
| Important: The ongoingPurchaseDatabaseReplication attribute MUST be set to "None" to prevent duplicate records in the Active Purchase table in WebOffice. Setting this attribute to anything other than "None" will make the terminal send in card, coin, or bill payments made to fill up the wallet as ongoing purchases. These purchases will have the end date equal to the start date. This, in its turn, will create one or two records in the Active Purchase table to be expired (red) or in grace time (yellow). An enforcer may write a ticket for this without seeing the correct active purchase made via the Wallet. |
In the example below the system is configured in the following way:
•The defaultPaymentServiceId is set to ID 0 in CORE.
•The paymentServiceChoice is set to "true" in CORE. this will allow the parker to select the payment method Wallet or No Wallet.
To be able to Top-Up a parking session the parker must select Wallet to log in to her account. Payment of a Top-Up with the Wallet can only be done when the original purchase has been made with the Wallet.
Top-Up can only be done with articles that support Top-Up.
•No inputRules are used!
Example:
<CORE powerSaveMode="Mains" defaultPaymentServiceId="0" defaultArticleId="1" ... forceCodeInput="true" paymentServiceChoice="true">
<PAYMENTSERVICE paymentServiceId="0"
group="Wallet"
name="PD"
step="false"
userIdentifier="Code"
ongoingPurchaseDatabaseReplication="None"
startPurchaseWithCard="false"
defaultArticleId="1"
ticket="Yes"
decreaseLeftToPayWhenCashIsPaid="true"
waitForCard="true">
<payUnit name="Coin" />
<payUnit name="Card" />
<payUnit name="Ext0" />
</PAYMENTSERVICE>
<PAYMENTSERVICE paymentServiceId="1"
group="NoWallet"
name="NoWallet"
step="false"
userIdentifier="Code"
ongoingPurchaseDatabaseReplication="AtPurchase"
forceCodeInputAfterFirstCoin="false"
topUpPurchaseMode="ContinuePurchaseFromEndDate"
startPurchaseWithCard="false"
defaultArticleId="2"
autoCardPay="false"
ticket="Yes"
decreaseLeftToPayWhenCashIsPaid="false"
waitForCard="true">
<payUnit name="Coin" />
<payUnit name="Card" />
</PAYMENTSERVICE>
