Taking Payments in Person: Embedded Checkout
Overview
We offer two styles of embedded integration, ensuring a seamless experience for your cashiers. One uses our In-Person Widget, and the other is a direct integration to our PIN pad APIs. Both use a similar flow but do have minor differences. This page provides a high level overview of the embedded in-person checkout and a comparison of the Embedded Widget vs. Direct Integration. You can find more detailed information on the Embedded Widget and Direct Integration requirements on their respective pages.
Local System Requirements
Before starting integration, confirm that the workstation has internet access to communicate with PaymentExpress APIs.
Comparison Summary
| Feature | Widget | Direct PIN Integration |
|---|---|---|
| Integration Style | PIN pad interaction handled by in-site iframe widget | PIN pad interaction handled directly by the cashiering system |
| Branding and UI Control | Partial control over design and layout of your site | Full control over design and layout of your site |
| PCI Exposure | None – PaymentExpress provided PIN Pads securely handle all card information, ensuring compliance. | None – PaymentExpress provided PIN Pads securely handle all card information, ensuring compliance. |
| Implementation Complexity | Moderate – requires front-end configuration in addition to API integration. However, the widget handles the API calls to activate, and deactivate the PIN Pad. Your system just needs to call the widget via JavaScript. | Moderate to High – Requires more frequent API calls to the PIN pad. |
| Ideal Use Case | When lower complexity integration is priority. | When having control over all API calls is a priority. |
Updated 2 days ago
Did this page help you?
