Full Integration vs. Semi Integration

The purpose of this document is to illustrate the processing differences between fully-integrated POS devices and semi-integrated devices, and how to build integrations differently for each device.

Full Integration

Examples: VX 805 and MX 915 Devices

Full integration means that Cardknox has control over the transaction process from the time the developer’s system hands over the transaction for processing to the Cardknox Payment Engine (PE), such as SDK, BBPOS etc., until transaction processing has been completed.

Full-integration Process

Semi Integration

Examples: PAX S300 and iCT 250 Devices

With semi integration, after the developer’s system hands over the transaction to Cardknox we hand over the transaction to the POS device for processing. This means that we do not have access to most of the information that passes between the device and the bank. After the device finishes processing the transaction with the bank, the device notifies Cardknox of the transaction result and we forward that information to the developer’s system.

Semi-integration Process

Semi-Integration Considerations

The following are several differences a developer should keep in mind when deciding whether to implement with a semi-integrated POS device.

  • You cannot submit voids or refunds directly to the gateway for processing.
  • A void transaction must be submitted to the device that submitted the original sale because the Cardknox gateway does not have the payment card information needed to submit it directly to the bank.
  • You can send a void to the device only if it has not yet been batch processed. Note: Void processing must be enabled on the account.
  • A semi-integrated device does not support refunds.
  • You can submit a credit transaction to the device. The customer will need to insert the card for processing.