Introduction to Paying at the Counter
payments with myPOS iOS SDK, .NET SDK, and ePOS API
In-store payments remain a critical touchpoint for merchants, and myPOS provides a robust suite of SDKs and APIs to enable fast, secure, and seamless Paying at the Counter experiences. Whether you are building a native mobile app, a desktop-based POS, or a web-integrated system, myPOS offers tailored tools to suit your needs.
This guide introduces three key integration options— iOS SDK, Android SDK, .NET SDK, and ePOS API —to help developers and integrators choose the best approach based on their platform and business logic.
myPOS Android SDK
The myPOS Android SDK provides a native integration for Android-based applications, enabling seamless communication with myPOS terminals via Bluetooth, USB, or directly through Smart POS devices.
Highlights:
- Native integration for Android apps using Java or Kotlin
- Full transaction lifecycle support: sale, refund, void, reversal
- Works with external and Android-based myPOS Smart terminals
- User-friendly API with robust error handling
- Secure and PCI-compliant communication
Ideal For: Retail and service apps running on Android tablets or phones, delivery solutions, and businesses using myPOS Smart devices with integrated card readers.
myPOS iOS SDK
The myPOS iOS SDK allows developers to integrate card-present payment acceptance into iOS apps, enabling transactions through compatible myPOS payment terminals via Bluetooth.
Highlights:
- Native integration for iOS apps (Swift/Objective-C)
- Easy terminal pairing and configuration
- Real-time transaction processing with automatic error handling
- Support for all major card types and contactless payments
Ideal For: Mobile checkout apps, food trucks, pop-up shops, and businesses using iPhones or iPads with myPOS Go or myPOS Combo devices.
myPOS .NET SDK
The myPOS .NET SDK enables Windows-based applications to interface directly with myPOS payment terminals over USB or serial connections. It is designed for traditional desktop POS environments where stable wired connections are preferred.
Highlights:
- Compatible with C#/.NET Framework applications
- Local communication with the terminal
- Full support for sales, refunds, and transaction reversals
- Integrated support for printing and transaction reporting
Ideal For: Retail shops, hospitality venues, and service providers using Windows PCs and static point-of-sale counters.
myPOS ePOS API
The myPOS ePOS API is a lightweight RESTful API that enables payment initiation on a terminal over the local network or cloud without requiring a physical connection or platform-specific SDK.
Highlights:
- Platform-agnostic: works with any language or framework
- Initiate transactions remotely and monitor status in real time
- Ideal for browser-based systems, kiosks, and cloud-based POS
- Requires terminal and POS device to be on the same network
Ideal For: Web-based POS applications, SaaS-based commerce platforms, and businesses seeking quick integration without platform dependency.
myPOS Payment API
The myPOS Payment API enables developers to build custom POS solutions for in-person payments, integrating myPOS payment flows and card readers into any business workflow.
Highlights:
- Standard protocol for connecting POS systems to myPOS devices via Bluetooth or USB
- Supports transaction processing, refunds, and recurring payments
- SDKs available for Android, iOS, and .NET
- PCI-compliant—no sensitive card data handled by your app
Ideal For: Businesses needing advanced, fully integrated POS solutions with custom workflows and device connectivity.
Choosing the Right Integration Approach
| Use Case | Recommended myPOS Tool |
|---|---|
| iOS mobile app with card terminal | myPOS iOS SDK |
| Android app with myPOS terminal | myPOS Android SDK |
| Windows desktop POS with USB terminal | myPOS .NET SDK |
| Web-based or platform-independent POS system | myPOS ePOS API |
| Integrate advanced payment flows and card readers into custom POS solutions. | myPOS Payment API |