Contents
Who this article is for: it applies to golf clubs operating mainly in Mexico.
What is this integration?
The GetNet integration connects Golfmanager with the GetNet payment gateway (by Santander), widely used in Mexico. It lets you charge by card both in the customer's online payments (bookings and shop) and at the club's POS.
It also lets you save the customer's card (tokenize it) to charge it later from the POS or admin without them re-entering the details, and process refunds from Golfmanager.
A payment gateway is the service that connects your business with the banks to charge by card securely. To tokenize a card means saving it as a code (token): Golfmanager doesn't store the full number, only that code and the last digits. Operations are processed in Mexican pesos (MXN).
What problem does it solve?
Charging by card both online and at the counter, with a single provider.
It increases security: the card is processed on GetNet's platform; Golfmanager only stores a token and the last digits, not the full number (PCI compliance).
Saved cards: the customer doesn't have to re-enter the card; the front desk can charge it on the saved card.
Refunds from Golfmanager for POS charges, without going into the GetNet dashboard.
Which systems does it connect, and which way does the data flow?
It connects Golfmanager (POS and online checkout) with the GetNet payment platform, in real time:
Online payment: Golfmanager takes the customer to GetNet's secure payment page, where they enter the card; GetNet confirms the result to Golfmanager.
POS payment with a saved card: Golfmanager sends the charge to GetNet using the customer's tokenized card and gets the approval on the spot.
If it's approved, the sale is marked as paid.
To refund, Golfmanager sends the cancellation to GetNet.
What information is exchanged?
Information | Direction | Purpose |
Amount and operation reference | Golfmanager → GetNet | Start the charge |
Card data to save (token, last digits, expiry) | GetNet → Golfmanager | Save the card for future charges |
Charge result (approved / declined) | GetNet → Golfmanager | Confirm the payment and keep a record |
Cancellation / refund request | Golfmanager → GetNet | Refund the customer |
🔒 Security: the full card number isn't stored in Golfmanager. Only a token and the last digits are kept, needed for saved-card charges and refunds. Communication with GetNet is encrypted.
Prerequisites (before turning the integration on)
Have a merchant account with GetNet and the access details for its payment platform.
Have the GetNet module installed in your Golfmanager, along with the billing module.
The credentials GetNet provides: username and key, merchant and branch identifiers, GetNet identifier and merchant, the service addresses (URLs) and the encryption key.
Billing management permissions to configure the integration and view the transactions.
How to set it up (step by step)
Step 1 — Install the module
Install the GetNet module (from the App Market or with support's help). Afterwards the GetNet configuration and the transactions and cards menus appear.
Step 2 — Gather the credentials
Ask GetNet for all your account details: username, key, merchant identifier (eTL), branch identifier, GetNet identifier and merchant, the service URLs and the encryption key.
Step 3 — Enter the details in Golfmanager
Go to Settings > GetNet (the GetNet configuration section).
Enter the Username and the User key.
Enter the Merchant identifier (eTL) and the Branch identifier.
Enter the GetNet identifier and the GetNet merchant.
Enter the GetNet URL, the URL to tokenize cards and the Encryption key.
Save your changes. The keys are stored encrypted.
Step 4 — Test
Make a test charge (online and/or at the POS) and check in GetNet Transactions that it shows as successful before operating for real.
⚠️ Important: all these details are required. If any is missing, the charge gives an error stating which one (for example, "The GetNet user is missing"). The test and production URLs are different: use the matching ones for the environment.
Each configuration field explained
Below, each field in Settings > GetNet is explained: what it is, how it affects the system, how it behaves, and an example of use. The sensitive data (keys) is stored encrypted.
Username
Field name: Username.
Description: the user for accessing the GetNet platform.
System impact: it authenticates the charge requests to GetNet. It's required.
System behavior: if it's missing, the charge warns that "the GetNet user is missing".
Example of use / what happens: you copy it from the details GetNet gives you and enter it here.
User key
Field name: User key.
Description: the password of the GetNet user.
System impact: it completes the authentication. It's required and stored encrypted.
System behavior: if it's missing, the charge warns that "the GetNet password is missing".
Example of use / what happens: you enter it once; it travels encrypted on every request to GetNet.
Merchant identifier (eTL)
Field name: Merchant identifier (eTL).
Description: the identifier of your merchant/company in GetNet.
System impact: it identifies your merchant account on every operation.
System behavior: if it's missing, the charge warns that "the GetNet company (eTL) ID is missing".
Example of use / what happens: you set it with the value GetNet provides.
Branch identifier
Field name: Branch identifier.
Description: the identifier of the merchant's branch in GetNet.
System impact: it indicates which branch the operations belong to.
System behavior: if it's missing, the charge warns that "the GetNet branch ID is missing".
Example of use / what happens: you set it with your branch's value.
GetNet identifier
Field name: GetNet identifier.
Description: the payment identifier GetNet assigns to your merchant.
System impact: it's used in the online payment operations.
System behavior: if it's missing, the charge warns that "the GetNet ID is missing".
Example of use / what happens: you set it with the value GetNet provides.
GetNet merchant
Field name: GetNet merchant.
Description: the merchant code GetNet uses for saved-card charges.
System impact: it's needed for the POS charges with a tokenized card.
System behavior: if it's missing, the saved-card charge warns that "the GetNet merchant is missing".
Example of use / what happens: you set it with the merchant code GetNet provides.
GetNet URL
Field name: GetNet URL.
Description: the address of the GetNet service for online payments (the payment page).
System impact: it's where Golfmanager sends the online payment requests.
System behavior: if it's missing, the online payment warns that "the GetNet payments URL is missing". The test and production URLs are different.
Example of use / what happens: you set the address GetNet tells you (test or production).
URL to tokenize cards
Field name: URL to tokenize cards.
Description: the address of the GetNet service for saving cards and for the POS charges.
System impact: it's needed to tokenize and to charge with a saved card.
System behavior: if it's missing, those operations warn that "the GetNet token URL is missing".
Example of use / what happens: you set the address GetNet tells you for tokenization.
GetNet encryption key
Field name: GetNet encryption key.
Description: the key shared with GetNet to encrypt the communications.
System impact: it protects the data sent and received; without it, you can't operate.
System behavior: it's required and stored encrypted; if it's missing, the operations warn that "the GetNet encryption key is missing".
Example of use / what happens: you set it with the key GetNet provides.
How it works day to day
The customer's online payment
The customer makes a booking or a purchase and goes to pay.
They select GetNet as the payment method.
GetNet's secure payment page opens, where they enter their card.
On approval, they return to Golfmanager with the message "Confirmed payment" and the sale is marked as paid.
Saving (tokenizing) a customer's card
On the customer's record, use the Tokenize card option.
Enter the card number and the expiration date (MM/YY).
Click Tokenize card. You'll see "Card successfully tokenized".
Golfmanager stores only the token and the last digits, and tags the customer with the "Card" label to find them easily. The saved card appears in the GetNet tab of their record.
Charging at the POS with a saved card
At the POS, when charging, choose GetNet.
The "Select card for payment with GetNet" window opens, where you choose the customer's saved card (by its last digits and expiry).
Confirm the charge. If it's approved, you'll see "Payment successfully completed" and the sale is paid.
Refunds
To refund a charge made at the POS with GetNet, cancel the original payment from Golfmanager: the system sends the cancellation to GetNet and records the refund (full or partial).
ℹ️ A refund is always made against an original payment in GetNet. For payments made on the online page, depending on the operation, the refund may need to be processed from the GetNet dashboard.
Checking transactions and cards
The module keeps two logs, accessible from the Billing menu:
GetNet Transactions: all charges and refunds, with the customer, the amount, whether they were successful or failed, the operation identifier and the error detail if there was one.
GetNet Cards: each customer's tokenized cards (last digits, expiry and whether they're active).
It's the first information to check when a charge or a refund hasn't gone as expected.
Limitations to keep in mind
It's oriented to Mexico: operations are processed in Mexican pesos (MXN); there's no other-currency selection.
It's not an automatic/recurring charge: saved cards are used to charge manually from the POS or admin, not for automatic direct-debit of fees.
To charge with a saved card, the customer must have at least one saved and active card.
Refunds from Golfmanager apply to the POS charges; online payments may require the GetNet dashboard.
It requires quite a few configuration details: if any is missing, the charge isn't made.
It depends on an external service: if the GetNet platform is unavailable, payments can't be processed.
Frequently asked questions
Does it work for online payments and for the POS?
Yes, for both. Online: the customer pays on GetNet's secure page. POS: the front desk charges with the customer's saved card.
Which currency does it charge in?
In Mexican pesos (MXN). The integration is oriented to Mexico and doesn't allow selecting another currency.
Where are the card details entered?
On GetNet's secure page (online payments) or, when tokenizing, in the card form. Golfmanager doesn't store the full number: only a token and the last digits.
How do I save a customer's card?
On their record, use Tokenize card, enter the number and the expiry (MM/YY) and click Tokenize card. You'll see "Card successfully tokenized" and the customer is tagged with the "Card" label.
Can I use GetNet for automatic fee charges?
Not automatically. GetNet isn't enabled for automatic direct-debit/recurring charges. Saved cards are used to charge manually from the POS or admin when you need to.
How do I charge at the POS with a saved card?
When charging, choose GetNet; the "Select card for payment with GetNet" window opens, you choose the customer's card and confirm. If it's approved, you'll see "Payment successfully completed".
I get "No tokenized cards were found for this customer". What do I do?
The customer has no saved card. Tokenize a card on their record first and try the charge again.
I get "You must select a card". What's going on?
In the charge window you haven't chosen any card. Select one of the saved ones and confirm.
When paying, it says a GetNet detail is missing (user, key, merchant…). What should I check?
A configuration detail is missing. Go to Settings > GetNet and check that they're all filled in: username, key, merchant and branch identifiers, GetNet identifier and merchant, the URLs and the encryption key.
The payment was declined. What do I do?
The card was declined by the bank or by GetNet. Review the detail in GetNet Transactions; the customer can try another card.
How do I make a refund?
For POS charges, cancel the original payment from Golfmanager and the system sends the cancellation to GetNet (full or partial). For payments made on the online page, depending on the operation it may be necessary to process the refund from the GetNet dashboard.
I get "You must void the original payment" when trying to refund. What's going on?
A refund needs a reference payment. Make sure you cancel against the original GetNet payment operation; you can't refund without it.
Can I make partial refunds?
Yes, POS charges allow a full or partial refund. The refund is always made against the original payment.
What happens if the customer doesn't finish the online payment?
The sale remains unpaid. The operation is recorded as not approved in Transactions. The customer can try again.
Where do I see a customer's saved cards?
In the GetNet tab of the customer's record, and in the GetNet Cards list of the Billing menu. You'll see the last digits, the expiry and whether they're active.
What card data is stored?
Only the token (a code that represents the card) and the last digits and the expiry. The full number isn't stored in Golfmanager.
Is there a test environment?
Yes: the test and production URLs are different. Configure the test ones to validate and switch them for the production ones when you're going to charge for real.
Are the keys secure?
Yes. The user key and the encryption key are stored encrypted, and communication with GetNet is encrypted. Even so, don't share the credentials.
Do I need to reauthorize or renew anything periodically?
No. As long as the credentials are valid, the integration works. It doesn't use session tokens that expire.
What can GetNet online payments be used for?
For whatever the customer pays from the portal: bookings and shop purchases. At the POS, additionally, you charge with the saved card.
Does it support pre-authorization (hold and capture later)?
No. Charges are immediate (authorization and capture in the same operation); there's no hold-and-later-capture flow.
What permissions do I need to configure the integration?
Billing management permissions, which give access to the GetNet configuration, the transactions and the cards.
A saved card appears disabled. What does that mean?
That card is marked as not active and isn't offered for charging. Tokenize a new card or reactivate it if applicable.
What should I do before charging for real?
Gather all the credentials, configure them, and make a test charge and a test refund (online and at the POS), validating them in Transactions before going to production.
Recommended best practices
Gather all the GetNet credentials before configuring, so you don't leave any detail empty.
Make a test charge and a test refund at go-live, to validate the whole cycle.
Keep the keys safe and don't share them; they're stored encrypted in Golfmanager.
Use the URLs of the right environment (test or production).
On a failure, check Transactions first: the error detail usually shows the cause.