Bluefin's Ingenico Bluechip application provide clients with a semi-integrated solution via the utilization of localized websocket communication.

Websocket Request Flow

1. The ISV's POS reaches out to the Ingenico machine over websocket with the payment request.
2. The Ingenico device running in Semi-Integrated (Server Mode) receives the receives the request and prompts for payment. Once the customer insert/swipes/taps or manual enters their card number, the device will send the encrypted card data to the Payconex Gateway
3. The Payconex Gateway receives the payment request and sends it over to the processor
4. The processor will process the payment and send the payment outcome back to the Payconex Gateway
5. The Payconex gateway will return a response to the Ingenico device advising of the payment outcome.
6. The Ingenico device will send a response back to the POS advising of a successful or failed transaction.

JSON Request Format

All messages to the Ingenico terminal will follow the same format.

• Each request must include a unique flow_id
• Each request will have a resource field (“resource” is a TSI payment transaction object instance)
• The required and optional parameters are set in the parameters list section

{
"flow_id":"12345",
"resource":
{
<parameters list>
}

}

Transaction Message-Flow

The request/response flow for Websockets follows a request event flow. Each request to the machine must have a unique flow_id. Once the device receives a request and there are no errors it will start the relevant transaction service on the terminal.

The device will instantly return a response indicating the start of the transaction service. Once this response has been returned to the device and the transaction has been handled, the device will change to an event message flow.

The event message flow will respond with the status of the transaction. If the status attribute is "ok", it will also respond with the transaction results, otherwise it will display the error. Once the event has been received, the terminal will respond with an event ack to indicate the response is accepted.

1. POS reaches out the payment terminal with a request.
2. The payment terminal will respond back to the POS advising the request is starting and the device will light up for payment.
3. Once the payment has been completed, the device will respond with an event response. This response will include the relevant transaction information.
4. The POS will respond with an Event ACK indicating the transaction response has been accepted.