Environments
Qerko provides two main environments for integration: Sandbox (for safe testing) and Production (for real customers). This page will help you set up both, so you can develop and test your integration with confidence.
Sandbox Environment
The sandbox is your playground. Here, you can safely build and test your integration with simulated payments—no risk, no real money.
Getting Started
-
Install the Qerko App Download the app for iOS or Android.
iOS Android -
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 redTEST
mark will appear in the top part of the screen which indicates that the app has been switched to sandbox mode.Production Sandbox -
Register and Add a Test Card Once in sandbox mode, register your account and add a test card. Payments are simulated, so feel free to pay anything.
ČSOB (CZ)
Card number Expiration CVC 4000 0070 0001 0006 12/30 600 PayU (SK, DE, AT)
Contact techsupport@qerko.com to enable the correct payment gateway for you, please. The default payment gateway is ČSOB
Card number Expiration CVC 5150 0300 9035 0186 12/29 123 Adyen (HU)
Contact techsupport@qerko.com to enable the correct payment gateway for you, please. 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. It will take you to the restaurant creation form after registration. Preferably, use your POS name as a restaurant name. You can create any number of restaurants. Before payment testing, let our tech support know, they will enable the necessary payment gateways for your testing restaurants.
-
Create an API Key Each restaurant gets its own API key. You’ll need this for authorization. There is a link
API keys admin
in the left column (accessible by the icon in the top left corner on a smartphone). This key will be used on the “restaurant level” where each restaurant has its own key so it has to be editable in the POS by restaurant, or by 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.
-
You’re Ready! You can now test payments and integration features.
- You have set up the app on your smartphone.
- You have added the credit card into the app.
- You have an API key for POS authorization.
Tools for Testing
- Demo POS: Try out our Demo POS to see how things work. This is a simple POS that serves as our testing environment. Feel free to use it to see how things work. DEMO2 uses WebSocket and the current API v2.
- API Tester: Send raw requests and see responses. https://sandbox.qerko.com/api/v2/pos/ This is a simple tool that sends requests to the API. Use it to test raw requests and responses.
- API Key Checker: Use this function to verify your API key format.
function verifyApiKey(apiKey: string): boolean { const KEY_LENGTH = 29; if (apiKey.length != KEY_LENGTH) { return false; } const HASH_LENGTH = 4; let base = apiKey.substr(0, apiKey.length - HASH_LENGTH); let hash = apiKey.substr(apiKey.length - HASH_LENGTH, HASH_LENGTH); return hex(sha1(base)).toLowerCase().startsWith(hash); }
Production Environment
When you’re ready to go live:
- Switch your API URL to https://qerko.com/api/v2/pos/
- Use your production Pos-Id (assigned by Qerko support). Start using the production Pos-Id, which will be assigned to you by tech support at techsupport@qerko.com. The process of assigning a production Pos-Id mostly consists of testing the documented functionalities in the sandbox environment—having it tested on your own and ready for our testing will be greatly appreciated. We recommend hardcoding the Pos-Id into your POS or distributing the value with the POS. It is not supposed to be user-configurable.
Need help? If you get stuck or have questions, email us at techsupport@qerko.com—we’re here for you!