Inbound payment transaction

The inbound payment transaction FSM uses this master object selector template:
SELECT ID,
       CID,
       SUBTYPE,
       TRANSMISSION_ID,
       BATCH_ID
FROM $DBSchema.TXN_PAYMENT_V T
WHERE STATUS=?
This finite state machine does the final state change for inbound payment transactions and records select information from the EDI X12 acknowledgments in the original outbound database tables. The EDI X12 acknowledgment data identifies payments and batches that were originally sent from the financial institution now receiving the acknowledgment. This FSM initiates an action for the receipt acknowledgment (EDI 997) and processed acknowledgment (EDI 824) transaction sets. This FSM action updates the original payments and batches with recipient state information. The available state values are shown in the following list.
  • receipt_accept
  • receipt_partial
  • receipt_reject
  • proc_accept
  • proc_partial
  • proc_reject
  • proc_held
Older state values for an object are overwritten when new states of the same transaction set type arrive for it. When processed acknowledgments for payments arrive, they overwrite any receipt acknowledgment states.
Important: EDI is not supported in this version.

The following figure shows the state diagram for the inbound payment transaction FSM.

Figure 1. Corporate Payment Services reference application inbound payment transaction FSM
gpyInboundPaymentTxnFSM.jpg