Processing Scheduled One Time Payments
When it is time to process a scheduled one time payment, the third party payment processing will process the payment as it does an immediate one time payment. However, in this case, it will call the C1-ThirdPartyOneTimePayNotification inbound web service with a Process action, passing in the pending one time payment’s Service Task ID and the payment details.
-
The system transitions the existing Third Party One Time Payment Task so that it proceeds to create a frozen payment event.
-
The payment date/time sent in by the third party payment processor is stored as a characteristic on the payment tender using the Processing Date/Time Characteristic Type in the Third Party One Time Payment Processing Integration master configuration. This is to capture the actual date/time when the payment was processed. This information is used in tender control processing.
-
A reference to the Third Party One Time Payment Task’s Service Task ID is stored as a characteristic on the payment tender using the Processing Reference Characteristic Type in the Third Party One Time Payment Processing Integration master configuration. This helps identify that the payment event/tender was created from third party payment processing.
-
The Payment Event ID is sent back to the third party payment processing system so that it has a way to identify the payment should there be a need to cancel the payment in the future.
-
The system checks if a frozen payment was already created from a previous web service call.
-
The account is locked during payment event creation.
For more information about the lifecycle of the Third Party One Time Payment Notification service task, refer to the C1-ThirdPartyOneTimePayTask business object in the system.
For more information about master configuration settings, refer to the Third Party Payment Processing Integration master configuration in the system.