Index
What is this integration?
The Nets integration connects Golfmanager with the Nets Easy payment gateway (by Nets/DIBS), widely used in the Nordic countries. It lets your customers pay online by credit or debit card when they make a booking or a purchase, with the security of 3D Secure.
The payment is made in a secure Nets form embedded in the checkout (it is not a physical card terminal/POS), and from Golfmanager you can also process refunds.
A payment gateway is the service that connects your business with the banks to take card payments securely. 3D Secure is the additional verification step (for example, a confirmation in the bank's app) that adds security to the payment.
What problem does it solve?
Lets clubs that operate with Nets take online card payments.
Increases security: the card form is handled by Nets and 3D Secure is applied; the data does not pass through Golfmanager.
Automatic confirmation: when the payment completes, the sale is marked as paid.
Refunds from Golfmanager, without entering the Nets portal.
Which systems does it connect and in which direction does the data flow?
It connects the Golfmanager checkout (payment) with the Nets gateway, in real time:
The customer enters the card in a secure Nets form (embedded in the payment) and, if required, completes the 3D Secure verification.
Nets authorizes and charges the payment and returns the result to Golfmanager.
If approved, the sale is marked as paid automatically.
To refund, Golfmanager asks Nets to reimburse the amount.
What information is exchanged?
Information | Direction | Purpose |
Amount, currency and order detail | Golfmanager → Nets | Start the charge |
Payment result (authorized / failed) and identifiers | Nets → Golfmanager | Confirm the charge and keep a record |
Refund request | Golfmanager → Nets | Reimburse the customer |
🔒 Security: the card data is entered in the Nets form and does not pass through Golfmanager.
Prerequisites (before activating the integration)
Have a Nets Easy account (created in the Nets portal).
Have the Nets module installed in your Golfmanager, together with the invoicing and checkout modules.
The Nets keys: the checkout key and the secret key, both test and production.
Operate in a currency supported by Nets (see Frequently asked questions).
Billing permissions to configure.
How to set it up (step by step)
Log in to the Nets portal.
Go to Company > Integration and copy your Checkout Key and your Secret Key (both the test and production ones).
Log in to Golfmanager with a user that has billing permission.
Go to Nets > Configuration.
Enter the Test secret key and the Test checkout key.
Enter the Production secret key and the Production checkout key.
Leave the Production mode off to start (test environment).
Save the changes. The keys are stored encrypted.
Check that the Nets payment method is active and available at payment.
Make a test payment with the Nets test cards and 3D Secure simulator.
When everything works, turn on the Production mode to take real payments.
⚠️ Recommendation: always start in test mode. Only when a test payment works end to end (including 3D Secure) should you turn on production mode.
Explanation of each field
Below is a description of each field in the integration: where it is, what it means, its impact on the system, and a usage example (what happens when it is used and how the system behaves). The keys are in Nets > Configuration.
1. Production mode
Field name: Production mode.
Description: a switch that indicates whether the gateway works in test (off) or production (on).
Impact on the system: it determines which pair of keys is used (test or production) and whether the charges are real. By default it is off (test).
Usage example: you turn it on when you finish validating the integration.
What happens when it is used: with it off, payments go to the Nets test environment and nothing is really charged; on, the charges are real.
System behavior: based on this switch, Golfmanager uses the test keys or the production keys to connect to Nets.
2. Test secret key
Field name: Test secret key.
Description: the Secret Key of the Nets test environment. It is the credential the Golfmanager server uses to authenticate with the Nets API.
Impact on the system: required to operate in test mode. It is private and stored encrypted.
Usage example: you copy it from the Nets portal and paste it here.
What happens when it is used: while Production mode is off, this key is used to authorize and charge test payments.
System behavior: if it is missing while you are in test, paying shows "Nets is not configured" and the charge cannot be taken.
3. Test checkout key
Field name: Test checkout key.
Description: the Checkout Key of the test environment. It is used by the payment form shown in the customer's browser.
Impact on the system: required for the card form to load in test. It is stored encrypted.
Usage example: you copy it from the Nets portal and paste it here.
What happens when it is used: when a test payment starts, the secure Nets form loads with this key.
System behavior: if it is missing, the payment form cannot be shown and "Nets is not configured" appears.
4. Production secret key
Field name: Production secret key.
Description: the Secret Key of the live Nets environment, which the server uses to authenticate for real charges.
Impact on the system: essential to take real payments. It is private and stored encrypted.
Usage example: you copy it from the Nets portal (production environment) and paste it here.
What happens when it is used: with Production mode on, this key is used to authorize and charge real payments.
System behavior: if you turn on production without this key, paying shows "Nets is not configured".
5. Production checkout key
Field name: Production checkout key.
Description: the Checkout Key of the live environment, used by the customer's payment form in production.
Impact on the system: required to show the card form in real charges. It is stored encrypted.
Usage example: you copy it from the Nets portal (production) and paste it here.
What happens when it is used: with Production mode on, the secure Nets form loads with this key.
System behavior: if it is missing in production, the form cannot load and "Nets is not configured" appears.
6. "Nets" payment method
Field name: Nets payment method.
Description: the payment means the customer chooses when paying online. It is available in the consumer area (bookings and shop) and supports refunds.
Impact on the system: it must be active and available at payment so customers can pay with Nets. It is not a physical terminal/POS method: it is only for online payments.
Usage example: you make sure "Nets" appears as a payment option at checkout.
What happens when it is used: the customer selects it and the Nets card form opens.
System behavior: if it does not appear, check that the method is active and that the keys are configured for the mode (test/production) in use.
How to use it day to day (step by step)
Customer online payment
The customer makes a booking or a purchase and goes to pay.
They select Nets as the payment method.
They enter the card in the Nets form and complete 3D Secure if their bank requires it.
On approval, the sale is marked as paid automatically.
Refunds
Locate the Nets payment you want to refund.
Cancel the original payment from Golfmanager: the system creates a refund operation and sends it to Nets.
Check in the transactions that the refund was recorded correctly.
The refund may take 1 to 3 business days to appear in the Nets portal (it shows as "refund initiated"). Only payments that have been charged successfully can be refunded.
Checking the transactions
In Nets > Transactions you will see all payments and refunds. Each operation has a status:
Status | Meaning |
Draft | The payment started but did not complete (3D Secure rejected or customer abandoned) |
Successful | The payment completed successfully |
Failed | The payment failed (check the error detail) |
By default, draft operations are hidden; remove the "Draft" filter to see them. Clicking a transaction shows the full detail (amount, customer, Nets identifiers and the gateway response).
Limitations to keep in mind
It is for the customer's online payments (bookings and shop), not for the physical terminal.
Nets operates mainly in the Nordic countries; you must have a valid Nets Easy account.
It only supports certain currencies (see Frequently asked questions); if your currency is not supported, you cannot charge.
The test and production keys are different: remember to turn on production mode to take real payments.
Only charged payments can be refunded, and refunds take 1-3 business days to settle in Nets.
It depends on an external service: if Nets is unavailable, payments cannot be processed at that moment.
Frequently asked questions
When paying, "Nets is not configured" appears. What does it mean?
The keys for the mode in use are missing. If you are in test, the test secret key and test checkout key must be set; if you are in production, the production ones. Go to Nets > Configuration, complete them and save.
Nets does not appear as a payment option.
Check two things: that the Nets payment method is active and available at checkout, and that the keys for the mode in use (test or production) are configured. If any is missing, the Nets form cannot load.
The payment stays in "Draft" status. What happened?
The payment started but did not complete: usually because the customer did not finish 3D Secure or abandoned the form. Nothing was charged. The customer can try the payment again. Remember that drafts are hidden by default in the transactions (remove the "Draft" filter to see them).
The payment appears as "Failed".
The charge attempt was not approved: for example, card declined or verification rejected. Open the transaction to see the error detail and ask the customer to retry or use another card.
"The payment gateway rejected the operation" appears.
It is a generic message when Nets returns an error that prevents completing the payment. Review the detail in Transactions (it includes the Nets response and, sometimes, the HTTP code) to identify the cause; it is usually a problem with the card, the verification or the Nets account configuration.
"Payment has already been made" appears.
A charge was attempted twice for the same payment. The first charge already completed successfully; there is no need to repeat it. Check the sale and the transaction to confirm.
"Invalid amount" or an error about the amount appears.
A zero or negative amount cannot be charged. Check that the cart/sale has a correct amount before paying.
It says the currency is not supported by Nets.
Nets supports a specific set of currencies: DKK, EUR, GBP, NOK, SEK, USD, PLN, CHF and CZK. If your club operates in another currency, you cannot charge with Nets. Check the currency configured in your Golfmanager.
How do I run a test before charging for real?
Leave Production mode off, use the test keys and make a payment with the Nets test cards; a 3D Secure simulator will appear with approve or reject options. When the process works end to end, turn on Production mode.
I ran a test and it charged for real (or it doesn't charge in production).
It is the Production mode set incorrectly. For real charges it must be on and with the production keys; for tests, off and with the test keys. Adjust the switch accordingly.
Can I refund any Nets payment?
Only payments that were charged successfully can be refunded. A draft or failed payment was not charged, so there is nothing to refund. The refund is started by cancelling the original payment from Golfmanager.
How long does a refund take to reach the customer?
The refund is sent to Nets immediately, but it may take 1 to 3 business days to settle and appear in the Nets portal (it shows as "refund initiated"). Inform the customer of this timeframe.
Can I make a partial refund?
Yes, the system supports refunding part of the amount; the original transaction shows the total already refunded. Coordinate refunds so as not to exceed the charged amount.
Does the card data pass through Golfmanager?
No. The card is entered in the secure Nets form and the sensitive data does not pass through Golfmanager. This increases security and simplifies compliance.
Does it work for charging on the counter terminal/card machine?
No. This integration is for the customer's online payments (bookings and shop). It does not control a physical Nets card machine.
Where do I see the detail of a payment or a refund?
In Nets > Transactions. Each operation shows its type (charge or refund), its status (draft, successful or failed), the amount, the customer and, when opened, the Nets identifiers and the gateway response.
Is it safe to store the keys in Golfmanager?
Yes. The secret and checkout keys are stored encrypted. Even so, treat them as sensitive credentials and do not share them; if you think they have been leaked, regenerate them in the Nets portal.
Recommended best practices
Test in test mode first with the Nets test cards and 3D Secure simulator before turning on production.
Keep the production keys safe and do not share them; they are stored encrypted.
Check your currency before starting: it must be among those supported by Nets.
Inform customers that refunds may take a few days to appear.
On a failed payment, check Transactions first: the error detail usually indicates the cause.