Environments
Qerko provides two main environments for integration: Sandbox (for safe testing) and Production (for real customers). This page explains how to set up each environment so you can develop and test with confidence.
Sandbox Environment
Use the sandbox environment to build and test your integration with simulated payments. No real transactions are processed here.
Install the Qerko App
Switch to Sandbox Mode
By default, the app is in production mode. To switch, scan a sandbox QR code or log out and log in with qerko-toggle-test as your email address.
A red TEST mark will appear at the top of the screen, indicating that the app is now in sandbox mode.
Register and Add a Test Card
Once in sandbox mode, register your account and add a test card. Payments are simulated, so you can complete transactions without risk.
ČSOB (CZ)| Card number | Expiration | CVC |
|---|---|---|
| 4000 0070 0001 0006 | 12/30 | 600 |
Contact techsupport@qerko.com to enable the correct payment gateway for you. The default payment gateway is ČSOB.
| Card number | Expiration | CVC |
|---|---|---|
| 5150 0300 9035 0186 | 12/29 | 123 |
Contact techsupport@qerko.com to enable the correct payment gateway for you. The default payment gateway is ČSOB.
| Card number | Expiration | CVC |
|---|---|---|
| 4111 1111 4555 1142 | 03/30 | 737 |
Set Up Your Sandbox Restaurant
Go to Restaurant Admin and create a test restaurant. After registration, you will be taken to the restaurant creation form. Preferably, use your POS name as the restaurant name. You can create any number of restaurants. Before testing payments, let our tech support know so they can enable the necessary payment gateways for your test restaurants.
Create an API Key
Each restaurant receives its own API key. You will need this for authorization.
There is a link API keys admin in the left column (accessible via the icon in the top left corner on a smartphone).
This key operates at the restaurant level, so each restaurant has its own key. Ensure it can be managed per restaurant or by the POS vendor.
Set a Pos-Id
Use any non-empty string in the sandbox. All POS systems are required to use a Pos-Id. This is a unique identifier for every vendor.
Ready to Test
You can now validate payments and integration features:
- The app is installed on your device.
- A test payment card is configured.
- An API key for POS authorization is available.
Production Environment
When you’re ready to go to production, review the following steps:
Switch your API URL
Production calls use a different base URL. Switch to https://qerko.com/api/v2/pos/.
Use your production Pos-Id
Start using the production Pos-Id. Tech support assigns it after you successfully pass the certification process. The production Pos-Id is issued once the documented functionality is verified in the sandbox. Preparing your own test evidence before our review accelerates the process. We recommend hardcoding the Pos-Id into your POS or distributing the value with the POS. It should not be user-configurable.
Tools for Testing
- Demo POS: Use the Demo POS to explore the integration flow. This simple POS powers our testing environment and uses the WebSocket connection with API v2.
- API Tester: Send raw requests and inspect responses. https://sandbox.qerko.com/api/v2/pos/ This tool issues requests against the API so you can verify payloads and responses.
Need help? Contact techsupport@qerko.com for assistance.