Contents
What is this integration?
The Comercia Global Payments integration connects Golfmanager's POS with the card terminal (dataphone) from Comercia Global Payments. When you take a card payment for a sale at the POS, Golfmanager sends the amount directly to the terminal: the customer pays on the terminal and the result comes back to Golfmanager, which marks the sale as paid.
It's an in-person, over-the-counter payment integration (taking card payment at the till), not an online-payments one.
There are two variants of the integration depending on the terminal type: the classic one (Comercia Global Payments) and the "Agnostica" one (the newer one — for example, the ITOS CM35 dataphone connected over the network). Taking payment at the POS works the same way; what changes is the module you install, the terminal type and how it connects. The old semi-integrated version is obsolete: today the Agnostica technology is used.
What problem does it solve?
Avoids typing the amount into the dataphone: the amount is sent automatically from the POS, eliminating errors.
Reconciles the till automatically: the card payment is recorded in the Golfmanager sale with no manual steps.
Speeds up payment at the counter and reduces mismatches between the POS and the terminal.
Prevents duplicate charges: if there's a connection drop, Golfmanager checks whether the operation was already done on the terminal before charging again.
Contracting contact in Spain: Pablo Castiglia — pablocastiglia@comerciaglobalpay.com
Which systems does it connect, and which way does the data flow?
It connects Golfmanager's POS with the Comercia Global Payments dataphone, over the club's local network:
Golfmanager sends the amount to charge (or to refund) to the terminal.
The customer pays with their card on the dataphone.
The terminal returns the result (approved or declined) and a ticket identifier, which Golfmanager stores so it can void or refund later.
If all goes well, the sale is marked as paid in the POS.
What information is exchanged?
Information | Direction | Purpose |
Amount to charge (or to refund) | Golfmanager → Dataphone | Have the terminal ask the customer to pay |
Payment result and ticket identifier | Dataphone → Golfmanager | Confirm the charge and allow voiding/refunding it |
🔒 Security: the card is read and processed on the dataphone itself. Golfmanager only sends the amount and receives the result; sensitive card data never passes through the software.
Prerequisites (before turning the integration on)
Have a compatible Comercia Global Payments dataphone. For the Agnostica variant, the ITOS CM35 model, requested from the bank with Agnostica technology (the previous semi-integrated version is obsolete).
Have the corresponding module installed in your Golfmanager (Comercia Global Payments or its Agnostica version), along with the POS and billing modules.
The dataphone and the POS computer must be on the same local network (the same WiFi) and the terminal must be reachable from the POS.
Know the dataphone's address (IP/URL) so you can link it to the POS.
The right permissions (manage billing) to configure the POS and billing.
How to set it up (step by step)
The steps below describe getting started (with the detail for the Agnostica / ITOS CM35 variant, the most common one). The classic variant is equivalent, changing the module and the terminal URL field.
Step 1 — Prepare the dataphone
Make sure you have the ITOS CM35 model, requested from the bank with Agnostica technology.
Connect the dataphone to the same WiFi network as the POS computer.
Step 2 — Install the module in Golfmanager
Go to Settings > System > App Market.
Install the Comercia Globalpayments Agnostica module (or the classic variant, depending on your terminal).
A new payment method is added automatically in the POS: Comercia Global Payments Agnostica. It's a "gateway" type, but at the till you'll see it as a card payment.
Step 3 — Get the dataphone's IP
On the dataphone, go to the network settings.
Press and hold on the right-hand side of your WiFi network to open the advanced settings.
Enter the password:
thb357.Find the IP address assigned to the device (for example,
192.168.20.211).
Step 4 — Link the dataphone to the POS
In Golfmanager, go to Settings > POS > POS list.
Select the POS you're going to link to the dataphone.
In the Agnostica terminal URL field, enter the address in the format
https://DATAPHONE_IP:3000(for example,https://192.168.20.211:3000).Save your changes.
⚠️ Important: you must add :3000 at the end, and the address must start with https://. Each POS is linked to its own dataphone. (In the classic variant, the field is Terminal url and the charge goes through the POS printer's local server.)
Step 5 — Run a test
Go into the POS.
Create a test ticket.
Select the card payment method (Comercia Global Payments Agnostica).
Confirm that the amount is sent automatically to the dataphone (you shouldn't have to type it in by hand).
Each configuration field explained
Below, each field is explained: what it is, how it affects the system, how it behaves, and an example of use showing what happens when you use it.
Agnostica terminal URL
Field name: Agnostica terminal URL, on the POS record (Settings > POS > POS list).
Description: the address of the Agnostica dataphone on the local network, including the port.
System impact: it's how the POS sends the amount to the terminal. Without it (or if it's wrong), the POS can't take card payments with that dataphone.
System behavior: on payment, Golfmanager connects to this address to send the payment and receive the result.
Example of use / what happens: you set
https://192.168.20.211:3000(withhttps://and:3000required) and save. From then on, that POS charges against that dataphone.
Terminal url (classic variant)
Field name: Terminal url, on the POS record (classic variant only).
Description: the address of the classic-variant dataphone (for example,
https://192.168.1.72:2001).System impact: it tells the POS which terminal to send the charge to in the classic variant.
System behavior: the charge is routed through the POS printer's local server to the terminal.
Example of use / what happens: you fill in the classic terminal's address and save; the POS can now charge against that dataphone.
Local server / URL Server (classic variant)
Field name: URL Server, on the printer linked to the POS (for example,
http://localhost:9090).Description: the address of the local server (the POS printer's) that bridges to the dataphone in the classic variant.
System impact: without a configured local server, the classic-variant charge can't reach the terminal.
System behavior: the POS sends the request to the local server, and it forwards it to the dataphone.
Example of use / what happens: if you get the "There is no configured local server" warning, check that the POS printer has its URL Server filled in.
Agnostica API key
Field name: API key (the Agnostica integration key). Managed by Golfmanager at system level.
Description: the key that authorizes the communication between Golfmanager and the Agnostica dataphone.
System impact: if the key is wrong, the terminal rejects the requests with an authentication error.
System behavior: it's sent with every request to the dataphone.
Example of use / what happens: you don't normally need to touch it. If you see "Authentication error. Check the API key", contact support to verify it.
Card reader configuration (action)
Field name: it's an action (a button), not a text field: "Dataphone configuration" / "Card reader configuration (Agnostica)".
Description: opens the dataphone's own settings screen.
System impact: it lets you adjust the terminal without leaving the POS environment.
System behavior: it's only available from the dataphone itself (the terminal app). From a regular browser it will show a notice that this action can only be used from the dataphone.
Example of use / what happens: if you need to adjust the reader, use this action from the device; on another computer it won't be available.
How it works day to day
Taking a card payment
In the POS, add the products and go to take payment.
Select Comercia Global Payments (the card payment method) as the payment method.
Golfmanager sends the amount to the dataphone. The customer pays with their card on the terminal.
When the terminal approves the payment, the sale is marked as paid automatically, and the payment details (card type, authorization number, etc.) can be printed on the receipt.
Refunds / voids
To refund a charge, Golfmanager sends the void to the dataphone using the stored ticket identifier from the original operation. The terminal processes the refund to the card. The refund needs the original transaction's details (its ticket identifier), which is why it's done from the original sale.
If there's a connection drop
If the payment completed on the dataphone but didn't get recorded in Golfmanager (for example, due to a network drop), the integration detects it on the next attempt and doesn't charge again: it recognizes those sales were already paid. In addition, the Agnostica variant can query the transaction status on the terminal to recover it. And if the server were to reject a payment after it had been charged on the dataphone, the integration tries to automatically reverse that charge. This is how duplicate charges are avoided.
Reviewing the transactions
In Billing > GlobalPayments transactions (or GlobalPayments Agnostica transactions, depending on the variant) you'll see every operation sent to the dataphone. Each record shows:
The shopping cart and the amount.
The terminal's TicketId (needed for voids).
The associated sales.
The operation's status (Success / No) and whether it has a refund.
The message or result returned by the terminal.
It's the first screen to check when a charge didn't complete or there are doubts about an operation; also, the error message you'll see here is the one to give to Comercia support if needed.
Limitations to keep in mind
It's for in-person payment at the POS with a physical dataphone, not for online payments.
It requires a local network: the dataphone must be reachable from the POS computer (same WiFi). Without the network, there's no automatic charge.
Each POS is linked to its own terminal via its address (URL/IP).
There are two variants (classic and Agnostica) depending on the dataphone type; use the module and field that match your terminal. The old semi-integrated one is obsolete.
It doesn't save cards: it's an in-person charge; there are no saved cards or recurring charges this way.
The Agnostica variant charges in euros.
It depends on the terminal: if the dataphone is off, has no connection, has no injected keys, or has issues, you can't charge this way.
Frequently asked questions
Is this integration for online or in-person payments?
For in-person payments at the counter: card payment at the POS using a physical dataphone. It's not for taking payment on the online booking website.
What's the difference between the classic and Agnostica variants?
Taking payment at the till works the same; what changes is the module you install, the terminal type and how it connects. The Agnostica one (for example, the ITOS CM35) is the newer architecture and connects over the network with a URL like https://IP:3000. The classic one routes the charge through the POS printer's local server. Use the module and field that match your dataphone.
What dataphone do I need?
For the Agnostica variant, the ITOS CM35 model, requested from the bank with Agnostica technology. The previous semi-integrated version is obsolete. If you're unsure about your terminal, check with Comercia Global Payments.
Why do I have to add ":3000" to the terminal URL?
Because the Agnostica dataphone listens on port 3000. The address must be in the format https://DATAPHONE_IP:3000, starting with https:// and ending in :3000. If the port or the https:// is missing, the POS won't be able to connect to the terminal.
How do I find the dataphone's IP address?
On the dataphone, go into the network settings, press and hold on the right-hand side of your WiFi network to open the advanced settings, enter the password thb357, and find the IP address assigned to the device (for example, 192.168.20.211).
The POS doesn't send the amount to the dataphone. What should I check?
Check, in this order: that the POS and the dataphone are on the same network; that the IP entered is correct; that the URL includes https:// and the :3000 suffix; and that the dataphone is the ITOS CM35 model with Agnostica technology and is powered on. If after these checks it still doesn't work, contact support.
I get "There is no configured local server". What does it mean?
It's specific to the classic variant: the charge goes through the POS printer's local server, and that server isn't configured. Check that the printer linked to the POS has its URL Server filled in.
I get "There is no configured terminal URL". What should I check?
The POS is missing the dataphone's address. Go to Settings > POS > POS list, open that POS and fill in the Agnostica terminal URL (or "Terminal url" in the classic one), and save.
I get an error that the dataphone isn't responding or can't connect. What do I do?
It means Golfmanager couldn't communicate with the terminal. Check that the dataphone is powered on and connected to the network, that the address (IP and port) is correct, and that both are on the same WiFi. These warnings usually include the terminal URL to help you verify it.
I get "Authentication error. Check the API key". What does it mean?
It's specific to the Agnostica variant: the integration key (API key) isn't valid, so the terminal rejects the requests. This key is managed by Golfmanager at system level; contact support to verify it.
The payment was charged on the dataphone but the sale is still unpaid. What do I do?
Usually a connection drop between the terminal and Golfmanager. Retry the charge: the integration detects the payment was already made on the dataphone and doesn't charge again — it simply marks the sale as paid. Don't type the amount into the dataphone by hand, to avoid charging twice.
I get "Sales are already paid". What does it mean?
Those sales were already charged on the dataphone on a previous attempt. Don't charge again; check the status of the sale and the transaction in GlobalPayments transactions.
What happens if the system rejects a payment after it was charged on the dataphone?
The integration tries to automatically reverse that charge on the terminal and tells you it's undoing the payment. If the automatic reversal isn't possible, you'll see "Could not auto-revert the terminal charge. Please refund it manually": in that case, issue the refund from the dataphone.
How do I refund a customer?
From the original sale, trigger the void/refund. Golfmanager sends the order to the dataphone using the ticket identifier of the original operation, and the terminal returns the amount to the card. That's why you have to start from the original sale (which is where that identifier is stored).
Can I save a customer's card for recurring charges?
No. This integration is for in-person payment with the dataphone; it doesn't save cards or allow automatic recurring charges. For that, other online payment gateways are used.
What currency are charges in?
The Agnostica variant operates in euros. In the classic variant, the currency is determined by the terminal's own configuration.
I see messages like "The terminal has no injected keys" or "Merchant number not established". What do they mean?
They're warnings that the dataphone itself isn't correctly provisioned/configured by the bank (it's missing the keys or the merchant number). They can't be fixed from Golfmanager: contact Comercia Global Payments support to get the terminal ready.
The customer or the terminal cancels the operation (by timeout or manually). What do I see?
You'll see a message like "Payment cancelled by the user" or "Transaction cancelled due to timeout". Simply try the charge again when the customer is ready.
I get "The payment app is busy. Please try again". What do I do?
It's a temporary notice: the terminal is busy processing something else. Wait a few seconds and retry the charge.
Does each POS need its own dataphone?
Yes. Each POS is linked to a terminal via its address (URL/IP). If you have several payment points, each one points to its own dataphone.
Does the payment method appear as a "gateway" or as "card"?
Internally it's a gateway type, but at the till you'll see and use it as a normal card payment.
Where do I check whether a charge went through?
In Billing > GlobalPayments (Agnostica) transactions. Each operation shows the cart, the amount, the TicketId, the associated sales, the status (Success / No), whether it has a refund, and the terminal message.
What permissions do I need to configure the integration and view the transactions?
Manage billing permission (and access to the POS settings). With it, you can link the dataphone to the POS and review the transactions list.
Do I need an internet connection to take payment?
The exchange between the POS and the dataphone goes over the local network. The dataphone, in turn, needs its connection to the bank to authorize the card. If the local network fails, the POS won't be able to send the amount automatically.
Who do I contact if the problem is with the dataphone?
If the issue is with the terminal (connection, dataphone errors, technical problems with the device), contact Comercia Global Payments' official support (see the "Support and contact" section). First, check the error message in GlobalPayments transactions, as they may ask you for it.
Support and contact
Golfmanager support: for questions about the configuration in Golfmanager (module, linking the POS, transactions), contact the Golfmanager support team.
Comercia Global Payments support (terminal issues: connection, dataphone errors, technical problems with the device):
Phone: 93 595 43 83 · 902 157 235 · 914 353 028
Hours: Monday to Friday, 9:00 to 20:00.
Contracting in Spain: Pablo Castiglia — pablocastiglia@comerciaglobalpay.com
💡 Recommendation: before contacting support, check the GlobalPayments transactions section in Golfmanager to identify the error message, as you may need to provide it to the technical team.
Recommended best practices
Verify the dataphone connection with a test charge at go-live and after any network change.
Ensure a stable local network between the POS and the terminal to avoid drops during payment.
If something fails, retry the charge rather than typing it into the dataphone by hand: this avoids duplicate charges.
Check that the terminal URL starts with
https://and includes the port (:3000for Agnostica).For any doubt about an operation, check GlobalPayments transactions: the result and message usually point to the cause, and they're the information support will ask for.