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. The device submits the transaction directly with the bank and at no point does Cardknox have access to the credit card or any other 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. Note: This does not apply to a Pax S300 that is set up to process the transaction through Cardknox.
Semi-integration Process
Semi-Integration Considerations
The following are several differences a developer should keep in mind when deciding whether to implement a semi-integrated POS device.
Cardknox tokens are not returned to the POS for future use since Cardknox does not have the card data.
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.
Ways to Integrate – Considerations
SDK (Payment Engine)
​https://kb.cardknox.com/payment-engine-sdk/​
Supported devices:
All Cardknox supported devices
Benefits:
Supports all Cardknox devices
Limitations:
Only supported on Windows
BBPOS
​https://kb.cardknox.com/bbpos/​
Supported devices:
All Cardknox supported devices
Benefits:
Supports all Cardknox devices
Limitations:
Only supported on Windows and Mac (The installation on Mac can be difficult)
Requires the BBPOS application to be installed and needs to run in the background all the time
JSSDK
​https://kb.cardknox.com/sdk-javascript/​
Supported devices:
PAX S300, S920 and A series devices
Benefits:
Supports any platform that can use JavaScript
No installation needed
Limitations:
Supports a limited number of devices
The US Only
API + Keyboard Emulator
​https://kb.cardknox.com/api/​
Supported devices:
ID Tech Augusta and VP8300
Benefits:
Minimal integration
Plug n Play Devices
Limitations:
Supports a limited number of devices
Does not support PIN entry
Augusta does not support tap
The US Only

Devices - Previous

IDTech VP3300

Last modified 1yr ago

Export as PDF

Copy link

Outline

Full Integration

Full-integration Process

Semi Integration

Semi-integration Process

Semi-Integration Considerations

Ways to Integrate – Considerations

SDK (Payment Engine)

BBPOS

JSSDK

API + Keyboard Emulator