Payment process and scenarios

The following are the message types that are sent by the system to the payment processor:
Table 1. Message Types
Message Process
Authorization This amount equals the rental total plus any additional Authorization needed ("pad") as determined by business rules.
Incremental Authorization This amount is sent by CPQ when the record is modified such as a VAS is added, the record goes into Overdue status and so on and the record is still in On Rent status.
Completion This message is sent for credit cards that have previously had an authorization processed and equals the Amount to be Charged.
Reversal This message is sent for cards that have previously had an authorization processed and in the message being sent authorization equals the amount being charged on the card. However, on the screen, system displays the difference from the original authorizations minus the payment amount.
Sale This message is sent when a payment is applied to a card that has NOT been previously authorized. This message does both the authorization and completion. No Authorization is diplayed on the screen.
Refund This message is sent when there is a refund due to the renter.
Table 2. Payment Scenarios
Fields Scenarios Button Triggered Action
Amount to be Authorized field contains a value Pickup/Pre Rent User selects the Rent button or answers Yes to putting the record to Pre Rent status during Loyalty Pre-Assign: The Authorization is processed for the full amount in the Amount to be Authorized field and posted to the payment grid.
Amount to be Charged field contains a value; Amount to be Authorized field contains a value Modifying the record PRIOR to return The user selects the Save button on the toolbar or the Save Modified button: The Incremental Authorization message is sent for the value in the Amount to be Authorized field; the Amount to be Charged value is ignored.
Amount to be Charged field contains a value; Amount to be Authorized field is NULL Modifying the record PRIOR to return The user selects the Save button on the toolbar or the Save Modified button: The Amount to be Charged value is ignored and no messages are sent.
Amount to be Authorized field contains a value; Amount to be Charged contains a value Return - Existing Authorization in the payment grid is greater than the Amount to be Charged. User selects the Return button: The Amount to be Authorized is ignored - the Amount to be Charged is posted (using the Completion message) and the Reversal is posted (using the partial reversal message).
Amount to be Authorized field contains a value; Amount to be Charged contains a value Return - Existing Authorization in the payment grid is LESS than the Amount to be Charged User selects the Return button: The Amount to be Authorized is processed first; the Completion is then sent if the Authorization does not fail. The screen displays both the Authorization and the Payment.
Amount to be Charged field contains a value Split Billing; 2 credit cards need to be charged for the full rental total. Card A - is authorized for the full amount Card B - is being applied at Return User selects the Submit button on the Split Payment popup: Card A is charged the amount entered (completion message is sent) and the Reversal is run to bring the Authorization amount to the proper total. Card B is charged the amount entered (the Sale message is sent). When the user processes the return for the car the remainder of the payment messages is sent and applied towards Card A (the message that will be sent depends on the charge amount and authorization amounts remaining).
Amount to be Charged field contains a value; Amount to be Authorized contains a value Split Billing; 2 credit cards need to be charged for the full rental total. Card A - has been authorized for the full amount Card B - is being applied at Return The above process is run; the Amount to be Authorized is ignored until the user processes the Return. See scenarios 'Return - Existing Authorization is Greater than the Amount to be Charged' and 'Return - Existing Authorization is LESS than the Amount to be Charged'
Amount to be Charged field contains a value; Amount to be Authorized is Null Renter is changing the Credit Card to use. For example, Renter gave Credit Card A at pickup and the full authorization was taken. At return the renter wants to change the card and apply the charges to Card B. The user adds the new Credit Card number - Card B in the validation pop-up; the user navigates to the Finalize Payment tab and selects the new card from the Existing Payment drop-down and selects Apply button - the Sale message is sent for Card B first. Then the Reversal message is sent for Card A for the full amount of the Authorization.