CTI Transaction Flow

CTI Transaction Flow

  1. Your RPG is a program within your application that first occupies the KCYB DB2 tables with relevant transactional information. The DB key from writing those records is then passed to the KCYBSV *SRVPGM. Credit card numbers and security numbers ARE NOT stored in DB2 tables for PCI compliance reasons and are instead passed as parameters on the call to the exported sub procedure.
  2. The KCYBSV *SRVPGM sub procedure is invoked.
  3. KCYBSV reads the DB2 tables to compose the XML documents.
  4. KCYBSV communicates with the remote web service including the digital signing of the transaction and all encryption.
  5. KCYBSV receives the response from the Cybersource web service and parses the response.
  6. KCYBSV places the parsed XML into the corresponding DB2 tables.
  7. Control is passed back to Your RPG program.
  8. Your RPG program can then read the response from the DB2 tables and relay relevant information back to the user (if it is an interactive program)