ORMPOS communicates with CSCA as part of the ASA/Retail integration. The lets the associate tender a credit card in ASA, and this connectivity also lets an associate suspend an order in ASA and transfer it to the retail environment for payment at an in-store POS terminal.

Shared Session

ORMPOS shares the ASA/CSC HTTP session, performing actions against CSC without risking concurrent order update exceptions. ORMPOS uses the agent’s login and performing functions on behalf of ASA, sharing a single CSC server session, except for end of day web service requests when there is no active ASA session.

The ASA to ORMPOS communication begins with login and shares session information to ORMPOS by adding the session information to the LoadOrder API. ASA calls LoadOrder and ORMPOS responds by querying CSC for the details of the order. Both of these parameters come from the REST session object which comes from the login response.

ORMPOS End of Day

At the end of day, ORMPOS performs various housekeeping tasks, such as removing any suspended and yet-to-be-resumed orders. This end of day processing takes place only when all registers are closed. If an ASA session is in progress, then a register is considered open. On logout, ASA closes the open register. This, however, leads to the scenario where ORMPOS needs to be able to login to CSC when an ASA session is no longer present. In order for ORMPOS to login to CSC independently, ORMPOS must also store the agent’s login information, which is collected during installation.