Batch Flow - One-Time Payment Tender Controls

This section includes the following:

Third-Party One-Time Payment Controls Pre-Processing (C1-TOPPP)

This batch process ensures that the one-time payment tender control includes payments that were processed within the designated cutoff time.

This batch process will retrieve auto pay staging records and check the processing date/time from the associated payment tender's characteristic. If the processing date/time is past the cut-off defined in the third-party integration master configuration, the batch number will be updated to the next batch number, which indicates that the record will not be processed.

This plug-in driven batch process is delivered with a Select Records algorithm and a Process Record algorithm. Refer to the C1-TOPPP-SR and C1-TOPPP-PR algorithm type descriptions in the application for more details.

Note:

The Third Party Payment Pre-Processing batch control is stamped on the auto pay staging record as soon as the one-time payment is created and frozen. A post-processing script defined in the Third Party Payment Processing Integration master configuration does this. Refer to the Third-Party One-Time Payment - Post-Processing script (C1POSTTPOTP) section for more details. This script gets the batch code from the One-Time Payment Pre-Processing section of the master configuration where the C1-TOPPP batch control should be defined.

Third-Party One-Time Payment Tender Controls (C1-TOPCT)

This batch process creates a new tender control (with an associated deposit control) for each batch control and run number encountered for third-party one-time payments that are not already linked to a tender control.

This plug-in driven batch process is delivered with a Select Records algorithm and a Process Record algorithm. Refer to the C1-TPCT-SR and C1-BLAPY-PR algorithm type descriptions in the application for more details.

Refer to the Automatic Payment Confirmations and Cancellations section in the user documentation for more details.