Getting Started & Choosing the Right Pay.POS Integration
Pay.POS offers multiple integration methods, each designed for different use cases and levels of integration. This article helps you choose the right integration and guides you to the corresponding implementation checklist.
Before you choose an integration
Regardless of the integration method, every Pay.POS implementation should meet the following basic requirements.
Merchant requirements
- Your Pay. merchant account is active.
- A sales location has been created.
- Card-present payment methods have been activated.
- The correct acquiring configuration is in place.
Device requirements
- Your device is supported. View the complete list of supported devices here.
- NFC is available and enabled.
- The device has a stable internet connection.
- The latest version of PAY.POS is installed.
- The operating system is up to date.
- The device is not rooted or jailbroken.
Choose your integration
Inject
The fastest and easiest way to integrate Pay.POS. Your application launches Pay.POS, passes the payment amount, and Pay.POS handles the complete payment flow.
Best suited for:
- POS systems that only need to initiate a payment
- Developers looking for the quickest implementation
- Merchants who are happy to use the standard PAY.POS interface
- Integrations with minimal development effort
➡ Continue with Pay.POS Inject.
Full Integrated SDK
Embed the payment experience directly into your own application for a seamless and fully customized user experience. The SDK gives you full control over the payment flow and user interface.
Best suited for:
- Custom POS applications
- White-label solutions
- Businesses that require a fully integrated payment experience
- Developers who need complete control over the payment flow and UI
Cloud Connect
Initiate and manage payments remotely through the PAY cloud. The payment is started from your POS or back-office application and processed on a linked Pay.POS device.
Best suited for:
- Existing POS systems with one or multiple payment devices
- Retail and hospitality environments
- Centrally managed terminals
- Businesses that want to remotely initiate payments without embedding payment logic in their application