Vetting Control API messages

Third-party vetting services and service wrapping applications use the Vetting Control application programming interface (API) to integrate with the Vetting Control engine. The API enables a vetting service to:
  • receive vetting requests for units of work from the Vetting Control engine
  • inform the engine when it determines that a transaction in a unit of work requires further attention, such as an operator review
  • notify the engine that processing has completed for a specific unit of work
  • inform the engine about the decisions made by the vetting service as the service reviews the flagged transactions. The decisions for a transaction are:
    • pay
    • no pay
    • accept and hold

The Vetting Control engine uses MQ Java™ Message Service (JMS) XML messages to communicate with the third-party vetting services and service wrapping applications.