The Lifecycle of a Payment Event Upload Staging Record

The following diagram shows the possible lifecycle of a payment event upload staging record.

The Payment Event Upload Staging lifecycle is comprised of the Incomplete, Pending, Complete, and Error states. A payment event staging record is initially created in Incomplete state. The payment event staging record moves to the Pending state when all processing logics are performed and a payment event is linked to it. Completion of the staging record processing sets the payment event to the Complete state. The C1-PEPL1 or C1-PEPL2 process moves a payment event staging record to the Error state when it is incomplete or pending.

  • Incomplete. A payment event staging record is initially created in incomplete state. The C1-PEPL1 process sets it to pending once it links it to a tender control and determines its tender account.
  • Pending. The C1-PEPL2 process sets a pending record to complete once all processing logic is executed and a payment event is linked to it.
  • Complete. When processing of the staging record is complete the record is in the complete state. This is a final state.
  • Error. A payment event staging record may be set to Error from Incomplete or Pending states by the C1-PEPL1 and C1-PEPL2 processes respectively.
Fastpath:

Refer to To Do Entries Instead of Exceptions for more information on how To Do entries are used to capture processing errors.