This scenario is the normal payments scenario. The physical transmission is mapped and stored in
the database.
A Messaging API transaction is created, and a request to load the physical transmission is
sent to Gateway Server. The flow advances when all of the batches are valid, and advances again
when all of the batches are complete. Finally, the payment origination physical transmission is complete.
The following figure shows a summary of the inbound valid payments scenario. Figure 1. Corporate Payment Services reference application inbound valid payments scenario
