Testing & Demo Environment

This guide covers everything you need to know about setting up a testing environment for myPOS integrations — from registering a demo account to understanding the limitations of the sandbox and demo terminals.


Demo vs. Production — Key Differences

⚠️Never mix credentials across environments
Demo and production environments use separate API endpoints. Using demo credentials against the production API (or vice versa) will cause all requests to fail with cryptic errors.
FeatureDemo / SandboxProduction
Registration URLmerchant-demo.mypos.eumypos.com
2FA methodSMS only (static code: 1111)SMS or authenticator app
Accepted cardsDemo cards onlyReal payment cards
PIN transactionsNot supportedSupported
Apple Pay / Google PayNot availableAvailable (isSandbox=false)
Callback URLRequires public HTTPS IPRequires public HTTPS IP
isSandbox valuetruefalse

Demo Account Registration

Register at merchant-demo.mypos.eu — this is a separate environment from the production login at mypos.com.

  • No documents or personal data are required for demo account creation.
  • If you receive a 500 error during registration, wait a few minutes and try again (temporary server issues).
  • If you receive an "account already exists" error, use the Forgotten Password flow at merchant-demo.mypos.eu/en/forgotten-password instead of creating a new account.
    • Use birth date 1.1.2000 and country UK if prompted during password recovery.

Adding users to a demo account

To add a team member to an existing demo account, you will need their: email address, phone number, date of birth, and country. Contact support with these details.


Demo 2FA

ℹ️Authenticator apps do NOT work in the demo environment
Google Authenticator, Authy, and similar apps will not work for demo 2FA. Select the SMS option — the demo environment sends a static verification code: 1111.

isSandbox Parameter

The isSandbox parameter controls which API endpoint your integration targets:

isSandbox=trueUse with demo/sandbox credentials against the test endpoint. Never use with production credentials.
isSandbox=falseUse with production credentials against the live endpoint. Required for Apple Pay and Google Pay.

Mixing the wrong isSandbox value with the wrong credentials will cause all payment requests to fail.


Test Cards & Transactions

  • Demo terminals only accept the included myPOS demo card — real credit cards will not work on demo terminals.
  • Demo cards only work on demo/test terminals — they cannot be used on production terminals.
  • For contactless demo tests, use amounts under €25. PIN entry is not supported in the demo environment.
  • Demo cards are labeled "demo" on the card surface.
  • Confirm the terminal type via Settings → About Terminal before testing to ensure you are using the correct card type.

Demo transactions failing — Error 12

Error 12 on a demo device indicates you are using a real credit card instead of the included demo card. Use the demo card that was shipped with the device.

Demo card declined — Error 78

Error 78 indicates that required functions are not enabled on the terminal. Contact support to enable the necessary functions for the demo device.


Sandbox for Online Payments

1
Use the test API endpoint

The PHP SDK uses the test API endpoint — not just a flag. Confirm the correct endpoint for your environment. Refer to the myPOS developer documentation for current test endpoints and test data.

2
Use unique order IDs

Duplicate order IDs will cause errors in both test and production environments. Use a unique ID for each payment request.

3
Ensure a publicly accessible callback URL

Your URL_Notify endpoint must be accessible from the internet — even during testing. localhost or private IPs will not receive callbacks. Use a tunneling tool (e.g. ngrok) for local development.


Setting Up a Demo Device

  1. Activate the device and link it to the demo account (use myPOS mobile app to scan QR or enter serial number).
  2. Access the demo environment at merchant-demo.mypos.eu/en/login.
  3. The device ships with a test card — use this card for demo transactions, not real payment cards.
  4. When sharing credentials, be careful with characters that look similar (0 vs O, 1 vs l).

Clearing a stuck demo transaction

If a Sigma demo device is stuck and cannot process transactions:

  1. Go to Settings → About Terminal.
  2. Tap the TID number 6 times.
  3. Confirm.
  4. Enter code 98710240.
  5. Confirm.
⚠️The stuck transaction will be lost when cleared using this procedure.

Partner Portal vs. Merchant Account

These are two separate accounts with separate credentials:

Account TypePurposeLogin URL
Merchant AccountDay-to-day transactions, store management, API credentialsmypos.com
Partner / Developer PortalPublishing apps to App Market, managing integrationsappmarket.mypos.com
Demo Merchant AccountTesting integrations with sandbox credentialsmerchant-demo.mypos.eu
Demo App MarketTesting App Market app submissionsdemo.appmarket.mypos.eu

You cannot log into the Partner Portal with merchant account credentials, and vice versa. For App Market publishing, you need a separate Partner account — independent of your merchant account.