Linkly Cloud Pairing Guide

Applies to: StamPOS Cloud REST integration using Linkly VirtualPinpad in sandbox, and compatible production terminals supplied through the merchant's approved Linkly or acquirer setup.

Before you begin

This process applies across supported Linkly Cloud terminal providers and acquirers. Ask your bank, acquirer or terminal provider to confirm that the merchant and terminal are provisioned for Linkly Cloud integration with StamPOS. An activated standalone EFTPOS terminal does not by itself confirm that Cloud integration is enabled.

Confirm that the StamPOS computer and payment terminal both have working internet access. Use the terminal's supported connection method and follow the provider's instructions to enable Linkly Cloud mode. Some terminals require Wi-Fi or Ethernet for Cloud integration; do not assume that a mobile connection used for standalone payments also supports it.

Have the Linkly Cloud username and password for the correct environment available. For production, obtain these through the merchant onboarding process with your bank, acquirer or Linkly. These are Linkly Cloud credentials, separate from internet banking credentials. If they have not arrived, contact your provider or Linkly support. Do not reuse sandbox credentials in production.

1. Prepare payment settings in StamPOS

Sign in to StamPOS using an administrator account, then open Hardware integration and the EFTPOS terminal tab.

Set Terminal provider to Linkly Cloud REST. Set Linkly environment to PRODUCTION for live payments, or TEST for sandbox testing. Selecting the environment updates the Cloud service address automatically. Complete this step before pairing.

If available, enter the actual Merchant ID (MID) and Terminal ID (TID) supplied by your provider for this merchant and terminal, then select Save settings.

MID and TID are optional for Linkly Cloud pairing in StamPOS: the pairing request uses the username, password and pairing code. However, StamPOS also uses MID and TID to generate its POS identifier for Linkly authentication, so entering the correct values before pairing is recommended. For multiple terminals, use the corresponding TID and assigned Cloud credentials for each setup.

2. Start pairing on the terminal

Open the pairing or cloud-login function on the Linkly terminal. On Linkly VirtualPinpad, start the cloud pairing process from the VirtualPinpad interface.

The terminal displays a temporary six-digit pairing code. Keep this screen visible while completing the next steps.

3. Enter the Linkly Cloud details

In StamPOS, select Pair terminal. Enter the Linkly Cloud username and password for the selected environment in the pairing dialog. If Username is prefilled with your MID, replace it with the assigned Linkly Cloud username.

Enter the six-digit pairing code exactly as shown on the terminal. Pairing codes are temporary, so generate a new code if the displayed code expires.

4. Complete the pairing request

Select OK in the pairing dialog. StamPOS sends the credentials and pairing code to Linkly Cloud.

Both devices communicate through Linkly Cloud, so they do not need to be connected to the same local network. They must both be able to reach the internet.

5. Confirm the result

When pairing succeeds, StamPOS displays PAIRED and stores the pairing details required for future sessions. It manages authentication tokens automatically.

The terminal should also leave the pairing screen and return to its normal ready state. Select Test connection and confirm a successful result. Restart StamPOS once during setup and test the connection again to confirm that the pairing remains available after application restart.

6. Verify a purchase and refund

Run a controlled, low-value purchase in the selected environment. A production purchase is a real charge. Confirm that:

• the payment request appears on the intended terminal;
• the transaction can be approved or cancelled from the terminal;
• StamPOS records the final outcome correctly; and
• the receipt and transaction history contain the expected result.

After confirming that the purchase was approved, use an authorised account to refund that sale through StamPOS, following any terminal or provider prompts. Confirm the refund outcome, receipt and transaction history. If an outcome is uncertain, follow the payment recovery guidance before retrying.

For example, on a setup labelled Counter 1, confirm that both the purchase and refund reach Counter 1's intended terminal and are recorded against the correct sale. Repeat these checks for each POS and terminal arrangement before trading.

Troubleshooting

Pairing code rejected: Confirm all six digits, check that the code has not expired, and generate a new code if required.

Authentication failed: Confirm that the username and password belong to the selected TEST or PRODUCTION environment. When moving from sandbox to production, select and save PRODUCTION, then pair with production credentials and a fresh code from the intended terminal.

Terminal not found or request times out: Confirm Cloud provisioning and Cloud mode with the provider, check the terminal's supported internet connection, and check that security software is not blocking StamPOS or the terminal application.

Wrong terminal receives transactions: Remove the existing pairing and repeat the process with the intended terminal. A Linkly Cloud pairing secret is intended for one lane and one PIN pad at a time.

Security guidance

Treat the Linkly username, password and stored pairing secret as sensitive business credentials. Do not include them in screenshots, support tickets or public documentation. Never email pairing secrets or payment credentials.

Environment summary

Sandbox: Select TEST in StamPOS and use Linkly VirtualPinpad with sandbox credentials.

Production: Select PRODUCTION before pairing, after merchant or acquirer onboarding and Cloud provisioning, with the production login details assigned to the setup.

Document version: 1.2 · Last updated: 26 September 2026