The EPISHIP Billing Payment Terminal API lets you integrate physical point-of-sale (POS) hardware into your shipping workflow, enabling card-present transactions at kiosks and shipping counters. You can develop applications that integrate with EPISHIP to manage Stripe Terminal readers, initiate secure chip-and-pin payments, and programmatically capture funds after successful card swipes.
View Doc →
The following figure shows the relationship between your EPISHIP app, the EPISHIP API, and physical Payment Terminal hardware.
Figure 1. EPISHIP API relationship diagram. Terminal reader management and transaction flow.
EPISHIP’s terminal services give administrators the ability to register and monitor physical card readers (such as BBPOS or Verifone devices), ensuring that shipping kiosks are ready to accept in-person payments securely.
The REST API that acts as the bridge between your application and the card reader, controlling the state of the hardware and managing the financial transaction lifecycle.
A strict three-step process where a Payment Intent is created, processed on the physical reader (waiting for customer interaction), and finally Captured to move the funds once the card is verified.
A set of dedicated endpoints available in development environments to simulate card presentment events (e.g., swipe, decline, requires auth), allowing developers to build POS flows without physical hardware.
Users can use the EPISHIP Payment Terminal API to perform common workflows, such as:
Terminal properties available to view and filter through the EPISHIP Payment Terminal API:
