Choose your integration
yetipay offers different integration paths depending on where and how your customers pay. Use this guide to find the right API for your setup.
Where are your customers paying?
Online — website or app
Your customer pays on a web page or in a mobile app. The payment form is shown in a browser or embedded in your app. You need to accept cards (and other methods) without a physical terminal.
| Fit | Integration | Best for |
|---|---|---|
| ✓ | Online Payments API | E‑commerce, checkout flows, digital goods etc |
Your server creates sessions and talks to the API. Adyen's Drop-in or Components handle the payment form and 3D Secure on the frontend. Get started →
In person — customer at a terminal
Your customer pays by tapping, inserting, or swiping their card at a yetipay terminal. The terminal is connected to the cloud. You need to initiate or receive payments from a POS, kitchen display, or backend system.
Who starts the payment?
| Started by | Integration | Best for |
|---|---|---|
| Your POS / backend | Pay At Counter | Retail checkout, hospitality front desk, any POS-initiated flow |
| The terminal (waiter brings it) | Pay At Table | Tableside payments, tabs, tips, hospitality |
Pay At Counter: Your system sends a "charge £X" request to a specific terminal. The customer interacts with that terminal. Your POS waits for the result and completes the order.
Pay At Table: The terminal is brought to the table. The waiter or customer initiates the payment on the device. Your POS receives the result via WebSocket and updates the tab.
On device — your app on the terminal
Your Android app runs directly on a yetipay device. You want to trigger a payment from your app (e.g. custom kiosk, self-service, or integrated POS) and get the result back in-process.
| Fit | Integration | Best for |
|---|---|---|
| ✓ | On Device Integrations | Custom apps on yetipay hardware, kiosks, self-service |
Install your own app on yetipay devices. Use the Android Intent API to hand off to the Yeti payment app when the customer pays, then receive the result back in your app.
Quick comparison
| Integration | Customer location | Who initiates? | API type |
|---|---|---|---|
| Online Payments | Browser / app | Customer (via Drop-in) | REST |
| Pay At Counter | At terminal | Your POS | REST |
| Pay At Table | At table | Waiter / customer on terminal | WebSocket + REST |
| On Device | At terminal | Your app on device | Android Intents |
Still not sure?
- E‑commerce or digital checkout? → Online Payments
- Retail or front-desk counter? → Pay At Counter
- Restaurant tableside? → Pay At Table
- Custom app on a yetipay device? → On Device
Need help deciding? Reach out via the Support Center.