
TrustTrack and RMPD: connecting a Ruptela tracker (Linqo, Persey SSM) to trip tracking
Are your trucks in TrustTrack - through Linqo, through the Ukrainian dealer Persey SSM or directly with Ruptela? Then the system connects to your Moisa Logistics account with one API key: the vehicles appear on the fleet map, and RMPD tracking sees where the truck really is. We show where to create the key in TrustTrack, what to do when the option is missing, and why the tracker alone does not replace the locator for RMPD.
Key figures
In short
- TrustTrack and RMPD meet in the Moisa Logistics account: the Ruptela system (from Linqo, Persey SSM or direct) connects with one API key, and your vehicles appear on the fleet map and in trip tracking.
- You create the key in TrustTrack itself: Account settings → API key settings → New API key. We do not need your TrustTrack password.
- No key option? Your company administrator switches it on. No switch either? The dealer enables API access.
- We only see vehicles and their coordinates and change nothing in TrustTrack.
- A TrustTrack tracker on its own is not a locator for RMPD or SENT until an operator registers the device in PUESC for SENT. That is checked separately.
TrustTrack, Linqo and Persey SSM: one system under different names
TrustTrack is the fleet monitoring platform of Ruptela, a company headquartered in Lithuania. Ruptela trackers are sold and serviced by partners, so the sign-in page looks different from carrier to carrier. In Poland it is often Linqo - a Wrocław company within the Ruptela Group whose customers sign in at track.linqo.io. Carriers from Ukraine may have the same system from the dealer Persey SSM (Персей ССМ). The logo on the login page differs, but inside it is the same TrustTrack with the same menus.
That is why the Moisa Logistics account has one system for all three - “Ruptela TrustTrack (Persey SSM, Linqo)” - and one guide. In the provider list, the “ПЕРСЕЙ ССМ” and “Linqo” tiles are marked “via TrustTrack”: whichever you pick, the next step is the same API key.
How to connect TrustTrack to RMPD tracking: 4 steps
The company owner connects it. In the Moisa Logistics account open “Profile” → the “Integrations” tab → “GPS trackers”, pick your provider or the TrustTrack system directly and click “Step-by-step guide”. In TrustTrack do this:
- Open TrustTrack on a computer - track.linqo.io or your dealer’s site.
- Your name at the top right → “Account settings”.
- On the left, “API key settings” → “New API key” → name it Moisa → “Save”.
- Click the key to copy it and paste it into the “Access key” field in the account.
After that, vehicles are matched to your fleet by licence plate on their own. Those that did not match (for example, when a truck has an internal name in TrustTrack) you pick by hand in the list of trackers under the card. Data refreshes every 5 minutes, and the vehicles are visible on the “Fleet map”. If the company has several TrustTrack accounts, each is added separately with “Add another TrustTrack account”.
| What | Where in TrustTrack | Where in the account |
|---|---|---|
| API key | Account settings → API key settings → New API key | The “Access key” field in the “GPS trackers” section |
| Key name | Anything, for example Moisa | Nowhere: the name is for you, to see who has access |
| Vehicles | The ones visible to the user who created the key | Matched to the fleet by licence plate |
Want to share only part of the fleet? Ask your administrator to create a separate TrustTrack user with just those vehicles and create the key from that user.
No “API key settings” item: who switches access on
Access to API keys in TrustTrack is granted separately, so your user may not have this item. The order is:
- There is a “Web users” icon (two people at the top) - your company administrator opens your user and turns on the “API key access” switch. Then “API key settings” appears.
- There is neither the icon nor the switch - API access for the company is turned off at the dealer. Write to the dealer (Persey SSM) or to Linqo support.
The letter to the dealer is in the guide in the account and copies with one button. It reads:
Hello! Please enable API access in TrustTrack for our company “___”: the “API key settings” item and the “API key access” switch for the user “___”. If this user is not an administrator, please grant administrator rights or create a separate API user with our vehicles. The key is needed for the Moisa Logistics service: read-only access to the latest coordinates. If it is simpler, please create the key yourselves and send it to us.
Ruptela’s help centre says a key for the whole fleet is created with administrator rights. If the dealer creates the key and sends it to you, paste it into the same “Access key” field.
What we see from TrustTrack and why it matters for RMPD
The key gives read-only access: the list of vehicles and their coordinates. We change nothing in TrustTrack - no settings, no users, no vehicles. Tracker data works in three places in the account:
| Where | What you see | What it gives you |
|---|---|---|
| Fleet map | Vehicles on a trip with RMPD tracking - with the order number and the route driven; other vehicles - from TrustTrack; next to each, the time of the last point | The whole fleet in one window with the documents |
| RMPD and RMPD 406 trip tracking | Next to the PUESC line, a dashed tracker line if the system provides movement history; a “fine risk” entry when the tracker sees movement and PUESC does not | You see that the RMPD locator is silent while the truck is moving, and can call the driver at once |
| RMPD form | A yellow warning when the vehicle is now far from the start point: the distance, where it is and when it was seen | Check the start date and place before filing; the warning does not block filing |
One more useful detail: when PUESC is silent and the tracker shows the truck standing, tracking pauses without an alert. When we file the RMPD for you, our specialist sees the start-point check before filing.
You can disconnect TrustTrack at any time in the same section: we delete the access on our side, and the trackers disappear from the fleet map. Delete the Moisa key itself in TrustTrack. If you delete the key only in TrustTrack, the account will say the system no longer accepts the saved access - then create a new key and connect again.
TrustTrack and RMPD: why a fleet tracker is not a locator yet
We often hear: “but the truck has GPS”. The locator or device number is a mandatory field of the RMPD notification (art. 28b(3)(12) of the Polish Road Transport Act), but not every GPS sends positions to the register - only:
- the e-TOLL PL app on the driver’s phone;
- an OBU or a fixed ZSL tracker that the operator registered in PUESC for the SENT service and gave a business number like Z00-KT45HM-2.
OBU/ZSL devices for SENT and e-TOLL are registered only by the OBU/ZSL operator (PUESC FAQ 07.05), and the carrier should check that the device is registered for SENT, not just for e-TOLL (07.15). So the question “can I put my tracker into the RMPD” goes to your provider: are they a ZSL operator, and is your device registered for SENT? You can also look up the operator in the official list of OBU/ZSL operators on the e-TOLL website (etoll.gov.pl). Connecting to Moisa Logistics changes nothing here: the API key gives us read access and does not register the tracker in PUESC.
Without positions from the locator entered in the RMPD, the carrier faces a 10,000 zł fine. What counts as a locator and how to set up a main and backup pair is explained in the GPS locator for RMPD and SENT, and three real cases with fleet trackers are in car transporters and GPS fines. Which other systems connect to the account and how a fleet tracker differs from a locator is covered in the overview GPS tracker for RMPD and SENT.
Common mistakes when connecting
| What happened | How it shows | What to do |
|---|---|---|
| A dispatcher connects instead of the company owner | The account says the GPS system is connected by the company owner | Ask the company owner to paste the key in their profile |
| The key was created by a user who does not see all vehicles | Only part of the fleet is on the map | Create the key from the administrator or from a separate user with the right vehicles |
| The plate is written differently in TrustTrack | The tracker did not match a vehicle | Pick the vehicle by hand in the list of trackers under the card |
| The key was deleted in TrustTrack | The account says TrustTrack no longer accepts the saved access | Create a new key and connect the system again |
| The TrustTrack tracker was entered in the RMPD as the locator | RMPD 406 shows no position | Enter the number of e-TOLL PL, an OBU or a ZSL registered in SENT - with an RMPD 101 update |
What trip tracking costs
Trip tracking is part of an RMPD prepared with us, or the separate RMPD 406 service:
- RMPD, full service - 500 UAH per document; self-service in the account - 100 UAH (first 10 days - 0 UAH). Tracking is already included in the RMPD price.
- An RMPD prepared elsewhere - RMPD 406 for 50 UAH: a map from PUESC data and an alert when the GPS signal drops.
Order: RMPD full service, RMPD self-service, RMPD 406. How tracking works is shown in why RMPD 406 and trip tracking, and what to do after an alert - in GPS signal lost.
Frequently asked questions
Sources
- Ruptela - Basic knowledge about API. How to create an API-key? (TrustTrack: Account settings, API key settings, New API key, Administrator rights)checked 21 November 2026
- Ruptela - GPS tracking and fleet management, TrustTrack (headquartered in Lithuania)checked 21 November 2026
- Linqo - monitoring GPS i zarządzanie flotą (Wrocław, Grupa Ruptela, logowanie track.linqo.io)checked 21 November 2026
- PUESC - FAQ SENT, 07. Obsługa zewnętrznych systemów lokalizacji ZSL/OBU (07.05-07.20, aplikacja e-TOLL PL jako lokalizator zapasowy)checked 21 November 2026
- e-TOLL - Urządzenia pokładowe OBU i ZSLchecked 21 November 2026
- e-TOLL - Operatorzy OBU/ZSL dopuszczeni do systemu e-TOLL (lista operatorów i urządzeń, PDF)checked 21 November 2026
- Ustawa z dnia 6 września 2001 r. o transporcie drogowym, tekst jednolity Dz.U. 2025 poz. 1490 (art. 28, 28b, 28c, 89a1, załączniki nr 1 i 3)checked 18 November 2026
Need documents for a trip?
Create a free account and prepare the document in your account - by yourself or with our team’s hands. Or leave a request: we will call you and tell you what you need for your particular trip.
More news



We are on TikTok
How to prepare documents from your phone, what is changing for carriers and where to save - in short videos.



