GS805 integrations · a technical overview for machine owners
GS805 Integrations: More Control Over Your Protein Shake Vending Machines
A GS805 comes with the maker's app on its screen and the maker's cloud behind it. VendCaptain is independent software that works with both: Connect uses the machine account you already have and changes nothing on the machine, Run replaces the app on the machine's own screen. This page says what each one does for you, what it touches, how a Nayax card reader fits in, and which APIs, SDKs and third-party integrations VendCaptain does not offer.
What you get, before the technical detail
- Keep the money you lose todayEvery card payment that made no drink, with what the customer is still owed, and a warning when a machine keeps failing. From the account you already have, on day one.
- Drive only when a machine needs youWhen each machine will run out, and a service checklist with photos for whoever goes.
- Sell more from each machineWhat every price change did to cups and income, happy hours and discount codes, and which machines would earn more somewhere else.
All of this is Connect: nothing changes on your machines, and the pilot is free for 15 days with no card. Run, the software on the machine's own screen, adds the stamp card, exact stock and a maintenance switch, and is in its final tests on our own machine, where it is planned to take over selling at the end of October 2026. The rest of this page is the technical detail behind both.
What a GS805 is, as software
The GS805 is a protein shake vending machine made by Wuhan Gao Sheng Wei Ye Technology Co., Ltd of Wuhan, China: powder stations, water, a mixer and a cup drop, behind a touch screen and a card reader. It is also sold under distributors' and operators' own brands, with the same app and cloud underneath. Four parts of it matter to anyone who wants to integrate with it.
- The touch screenAn Android touch panel. The maker's app runs on it. It shows the menu, asks the card reader for payment and tells the machine board to make the drink.
- The machine boardDrives the powder stations, the water, the mixing and the cup drop. The screen tells it what to make.
- The card readerA cashless device on an MDB bus (Multi-Drop Bus, the vending industry's standard for payment devices). On most GS805 machines in Europe it is a Nayax reader. It takes the card and answers approved or declined. The machine never sees card data.
- The factory cloudThe maker's web portal. The machine's app reports each sale and its stock levels to it, and takes menu and price changes from it. It is the only interface the maker gives you to your machines.
What the maker does not publish, as far as we know: an API, an SDK, webhooks or developer documentation, for the machine or for its cloud. The web portal is the whole interface. That is the wall every search for a GS805 API, SDK or Open API runs into, and it is the reason VendCaptain integrates the way it does: through the account you already have, or by becoming the software on the machine.
Two integration paths, one portal
- GS805 machineThe maker's app sells. The Nayax reader takes payment over MDB. Nothing is installed.
- Factory cloudReceives each sale, the shelf and stock levels, as it does today.
- VendCaptainUses the account you already have. Reads every hour. Writes prices, availability and discounts when you ask, and checks they landed.
- GS805 machineVendCaptain's kiosk app sells: the menu, the payment through the card reader, the drink through the machine board.
- VendCaptain cloudMenu, prices, tests and screen content go down. Sales, stock, faults and service actions come up.
- VendCaptain portalThe same portal as Connect, with exact stock, a maintenance switch and the stamp card.
- Nayax readerProcesses the card over its own modem. Reports approved or declined to whichever app is selling.
- Nayax CoreNayax's own portal: every card transaction, its authorisation, settlement and refund.
- VendCaptainTakes the transactions by report upload or by Nayax's push to a queue you own, and pairs each one with a sale.
Connect: integration through the factory cloud. Nothing changes on the machine.
Connect uses the factory cloud as the integration point, because it is the only one the machine offers. You connect the account you already use for your machines, once, from the portal's Settings page, and from then on the connection renews itself every hour. There is no new login for your staff and no change on any machine.
What Connect does with the factory cloud
- Reads
- Every sale, every hour: machine, drink, price, time, and whether the machine reported it made. At least daily: each machine's shelf with the drinks listed and their prices, the stock figures the cloud holds, and the advertising programmes and schedules on the screens.
- Reads once
- Your full sales history, from the account's first day, in one pass that resumes where it stopped if the connection drops.
- Writes, when you ask
- Prices and availability per machine, for one drink or for every machine from one spreadsheet. A failing machine's drinks taken off sale, and the same shelf put back at the same prices. Discount windows: happy hours, launch discounts and discount codes.
- Checks every write
- After each write, VendCaptain reads the cloud back and reports what it holds. A discount is shown as running only when the cloud says it is. When the cloud cannot be reached, the page says "could not confirm", never "done".
- Never
- Changes the customer screen, the recipes or any software on the machine. Shares your account with anyone, or stores it anywhere but encrypted in your own workspace.
On top of that read, VendCaptain adds what the factory portal leaves out: the list of card payments that made no drink and what each customer is still owed, a warning when a machine keeps failing, when each machine will run out, what each price change did to cups and to income, which machines would earn more somewhere else, a service checklist with photos, reports by email on a schedule, and a login per partner gym that shows only its machines.
The limits, stated plainly
Connect is a read of someone else's system, so three things follow. Data arrives every hour, not live. Stock on Connect is an estimate: the factory cloud reports levels when the machine does, and VendCaptain fills the gaps from sales and from the refills your crew logs. And the connection depends on your account with the maker, who has not endorsed it. The maker can change or withdraw that access, and VendCaptain cannot promise continuity. Sales history already imported stays yours. The pilot terms say this in writing, and Run is the path that does not depend on it.
From daily use on our own machine
We have run our own machine on Connect for months. In daily use the portal is complete, and it has been a while since we hit a bug. The iPhone app does our service visits and monitoring, keeps working with no signal and sends everything when the connection is back. The powder estimates, which subtract each drink's recipe from the last refill or reading, have matched what we find in the containers on the visit. One machine, one operator: that is the whole sample, and it is ours.
Try Connect free for 15 daysWhat is supported, and what is not
Run: VendCaptain on the machine's own screen
Run installs VendCaptain's kiosk app on the Android panel the machine already has. It becomes the program that sells: it shows the menu, drives the card reader, tells the machine board to make the drink and reports to VendCaptain's own cloud. Same machine, no new hardware, and the factory app stays installed, switched off.
How Run talks to the machine
- The machine board
- VendCaptain drives the machine board directly, as the maker's app does, with no change to the hardware. The pour sequence, the cup check and the fault handling are VendCaptain's: a fault takes the machine out of service on the spot, and a drink that is being made always finishes first.
- The card reader
- VendCaptain is the one program driving the card reader. Payment first, then the drink. If the machine cannot make the drink, the sale is marked failed at that moment and the payment is listed with what is owed, instead of being found in a report a week later. Two sellers never run at once: the switch to Run refuses while the maker's app is still active.
- The cloud
- The kiosk pulls its menu, prices, promotions, tests and screen content, and pushes every sale, every change in stock, every fault, every service action and every crash report. It keeps selling with no internet and uploads when the connection is back. The portal shows when each machine last talked to the cloud.
What Run adds to everything Connect does
- Exact stock
- Grams and cups after every drink, from the machine itself. Refills and service cups are logged at the machine, behind your service PIN.
- A maintenance switch from anywhere
- Take a machine out of service from the portal; the kiosk obeys within about 20 seconds and shows its out-of-service screen until you put it back. Staff can do the same at the machine.
- Price and menu tests
- Two prices or two menu orders on the same machine, assigned per customer, measured in cups and income, so a price rise is a measured decision. What a 40 percent rise did to one fleet is in the operator case study.
- The stamp card
- In Apple Wallet and Google Wallet, with no app to download. One stamp per paid shake, redeemed at the machine with a single-use code, and a reminder on the customer's phone near the gym. Everything Run adds for loyalty is on GS805 loyalty and promotions.
- Something to do while it mixes
- A game and a leaderboard on the screen during the minute the shake takes.
- Your standby screen
- The gym's classes and offers on the attract screen, scheduled from the portal.
- It comes back by itself
- After a power cut or a crash the kiosk restarts on its own. If the app keeps failing, it stops selling and says so on the screen, instead of charging in a loop.
Today's facts about Run
Run is installed on our own machine in Madrid, where it has made real drinks since June 2026 and is in its final tests before it takes over selling, planned for the end of October 2026. No operator's machine runs it yet. Yours would be the first operator's machine, planned and installed with us, one machine at a time, and updates are installed by hand as well. It comes with a Nayax reader, and any MDB payment terminal can be connected on request. Customer screens are in English and Spanish. A workspace can have some machines on Connect and others on Run. Going back is a switch on the machine's service screen, behind your PIN: it hands the screen and the card reader back to the maker's app.
Where Nayax fits: MDB on the machine, Nayax Core in the cloud, and the Nayax API
Nayax is the payment side, and it is separate from the maker at both ends. On the machine, the Nayax reader sits on the MDB bus: whichever app is selling asks it for a payment, the reader processes the card over its own modem and answers approved or declined. In the cloud, every card transaction lands in Nayax's own portal, Nayax Core, which is the record of the money: authorisation, settlement and refunds. The factory cloud knows a drink was sold. Nayax knows a card was charged. Neither one knows the other.
VendCaptain reads both and matches them. Each card transaction is paired with the sale on the same machine, at the same price, within a few minutes, in the machine's local time. The pairs tell you what no single system can: a charge with no drink and no refund, a refund already made at Nayax, a drink that was made but never charged.
Three ways card transactions can reach VendCaptain
- 1. A report you upload
- Nayax Core's Dynamic Transactions Monitor export, as Nayax produces it, in English or in Spanish. The portal recognises either language, and uploading the same period twice never double counts. Every Connect pilot has this on day one.
- 2. Nayax's push to a queue you own
- Nayax can send each transaction as a message to an Amazon SQS queue in your own AWS account. VendCaptain reads it every hour. No uploads, and a richer identity for each payment: card brand and last four digits plus Nayax's payment token. Set up with us: the push is switched on from the Nayax side.
- 3. The Nayax Lynx API
- Nayax publishes the Lynx API for its customers. VendCaptain does not use it today: it needs a role that Nayax grants per account, and the two paths above carry the same transactions without it. VendCaptain does not resell Nayax services or configure your Nayax account.
What VendCaptain does with card data
Card brand and last four digits only, as Nayax's own export carries them. Never a full card number, and never from the machine, which does not see card data at all. Refunds are made in your Nayax account, as today. VendCaptain tells you which ones to make and marks the ones you have.
The full story, with what we observed on our own Nayax account, is on GS805 and Nayax. What each path shows you day to day is on GS805 remote monitoring, and the problems it catches are on GS805 troubleshooting.
Work on request: other payment terminals, consultations and features
Not everything an operator needs is a switch in the portal. Some of it is work we do for you, with a scope and a price agreed first and a date it is delivered. Three kinds come up most.
- Any MDB payment terminal for Run
- Run drives the card reader through MDB, the vending industry's standard, so it is not tied to Nayax. A bank's unattended payment terminal, a local acquirer's reader, another provider's: if it speaks MDB, we can connect it, in any country. Tell us the terminal and the country. We integrate it with you and test it on your machine before it sells. On Connect nothing changes, whatever the reader.
- A consultation on your machines
- A technical review before anything is installed: your machines, your reader, your account with the maker, what Connect and Run would each change for you, and what they would not. Or a review of your sales data after the pilot, machine by machine: payments with no drink, idle machines, what your prices did. On a call, with your numbers on the screen.
- A feature you need that is not here
- An export in the shape your accountant wants, an alert rule, a report, a screen language. Agreed as a scope first, then built, delivered in a release, and kept in the product.
To ask for any of these, write to the address below with the terminal, the country and the number of machines. You get an answer in one working day: yes with a scope, or no with the reason.
What is supported, and what is not offered
Searches for GS805 integrations lead to a lot of words and few facts. These are the facts for VendCaptain, as of October 2026.
Supported today
Each line says how it is delivered. Self-serve: you do it from the portal. Set up with us: we do it together on a call. Our own machine first: in use on our own machine and phones before any operator's. Run is planned to go live there at the end of October 2026, and the iPhone app is on our own phones with an App Store listing planned; yours would be the first operator's.
- Connect: your GS805 factory cloud account, read every hour and written to when you ask. Self-serve
- Run: VendCaptain's app on GS805 machines, with Nayax or any MDB payment terminal. Our own machine first
- Nayax card transactions by report upload. Self-serve
- Nayax card transactions by Nayax's push to an Amazon SQS queue you own. Set up with us
- Mixed fleets: some machines on Connect and some on Run, in one workspace. Set up with us
- Your data out: any table as CSV or Excel, reports by email on a schedule, and everything on request when you leave. Self-serve
- Logins by role: operator, crew (the service checklist only) and partner (read-only, its own machines). Self-serve
- Accounting: one invoice per machine per day posted to Holded, with stock-outs documented. Set up with us
- Stamp card in Apple Wallet and Google Wallet, with Run. Our own machine first
- iPhone app for service visits and monitoring, working with no signal and syncing later. Our own machine first
- Courtesy codes and repeat-buyer analytics from card taps, on either path. Self-serve
- Alerts by email: a machine that charges without pouring, a connection that stopped. Self-serve
- Hosting: servers in the European Union, each operator's data kept apart, a restore we have tested.
Not offered
- A public REST API, webhooks or an Open API for VendCaptain's data. What exists is the export, the scheduled reports and your data on request. If you need an API, tell us what you would connect it to.
- An SDK or developer kit for the GS805. The maker publishes none that we know of, and Run is a finished product, not a kit.
- Access to the factory cloud's interface, resold or proxied. Connect uses your own account, and the maker has not endorsed it.
- The Nayax Lynx API, Nayax account set-up or Nayax reselling.
- Integrations with gym membership, access or class-booking software: no member check-in at the machine, no membership discounts read from another system. Loyalty today is the stamp card and the codes.
- Card readers that do not speak MDB. Any MDB payment terminal can be connected to Run (see work on request). Connect works with whatever reader you have, because it reads the machine's sales, not the reader.
- Payment processing. VendCaptain never touches card data or money and never processes a payment itself.
- Remote installation of Run. It is installed on site, by hand.
- Other machine models. GS805 only, today.
- Forwarding telemetry to another vending management platform.
Questions GS805 owners ask
Does the GS805 have an API or an SDK?
Not that its maker publishes. The machine's app talks to the maker's cloud, and the maker's web portal is the only interface to that cloud. VendCaptain's Connect works through that same portal with your own account. Run replaces the app on the screen instead.
Can I keep the factory app and still use VendCaptain?
Yes. That is Connect. The factory app keeps selling, the machine is untouched, and VendCaptain works from the cloud the machine already reports to. The pilot uses Connect.
Is Connect endorsed by the maker? What happens if they cut it off?
No. Connect uses your own account with the maker, who has not endorsed it. If they change or withdraw that access, the hourly read stops and you get an email. Everything already imported stays in your workspace, and Run is the path that does not depend on the maker's cloud at all.
Which card reader does Run need, and why Nayax?
Run comes with Nayax, the reader fitted to GS805 machines sold in Europe and the one on our own machine. Run drives the reader through MDB, so any MDB payment terminal, such as a bank's unattended terminal, can be connected: tell us which one. Connect does not care which reader you have.
Does VendCaptain see card numbers?
No. From Nayax's export or feed it stores the card brand and the last four digits, which is what lets it recognise a returning customer. The machine never sees card data: the reader processes the card and only reports approved or declined.
Can I run some machines on Connect and others on Run?
Yes. One workspace can read some machines from the factory cloud and others from VendCaptain's kiosk, and the pages show them side by side. The pilot starts every machine on Connect; the first machine on Run is planned with us.
What does Run change on the machine, and can I undo it?
Run installs VendCaptain's app on the machine's screen and switches the maker's app off; nothing is uninstalled and no hardware is touched. The machine's service screen, behind your PIN, switches the seller back to the maker's app.
Can VendCaptain connect to my gym's membership software?
Not today. There is no member check-in at the machine and no discount read from a membership system. What exists for gyms is the stamp card in Apple and Google Wallet, courtesy codes, the gym's own content on the standby screen, and a read-only login per partner gym.
Does Run affect my machine's warranty?
Run touches no hardware and keeps the maker's app installed, but the warranty is a contract between you and your supplier, and only they can answer for it. Ask them before the first machine moves to Run.
Where is my data, and can I take it with me?
On servers in the European Union, in a workspace kept apart from every other operator's. You can export any table at any time. If you leave, you can ask for everything to be sent to you or deleted.
My machine was sold under another brand. Does this apply?
If it is a GS805 underneath, yes. Distributors and operators across Europe sell the GS805 with their own name on the wrap, and the maker's app and cloud stay the same, so Connect works from the same account and Run installs on the same screen. The tells are seven powder containers behind the door, an Android touch screen running the maker's app and a dispensing window marked AUTO; the owner's guide has the full list. If in doubt, send us a photo of the open door.
More GS805 guides
- GS805 and NayaxHow the payment and the drink are connected, and what happens to the money after a failed vend.
- GS805 troubleshootingPaid but no drink, idle machines, run-outs, the waste bucket, a frozen screen: what each is and what to do.
- GS805 remote monitoringFactory telemetry against VendCaptain Connect and Run, and which data exists at all.
- GS805 owner's guideSoftware, payments, setup, calibration and cleaning, with the official manuals linked.
- GS805 loyalty and promotionsDiscount windows and codes in the factory software, and the stamp card and happy hours VendCaptain adds.
- Running a GS805 in a gymOne machine in a Madrid studio since May 2026: what we found, and what changes when our software becomes the seller.
Try it on your own GS805 machines, free for 15 days.
The pilot uses Connect, so nothing changes on your machines. No card needed.
Daniel Escobar escobar@vendcaptain.com +34 623 345 790 Email, WhatsApp or phone