Index
What is this integration?
The Worldpay integration connects Golfmanager with the Access Worldpay payment gateway. It lets you charge cards online, save the customer's card for future payments, charge in person with a card terminal at the POS, make recurring charges (fees/memberships) and process refunds from within the system.
A payment gateway is the service that connects your business with the banks to charge cards securely. Worldpay is one of the most widespread gateways, very common in the United Kingdom.
What problem does it solve?
Charge through every channel with a single gateway: online, in-person POS and with a saved card.
Speeds up the regular customer: they can pay with their saved card without typing it again.
Greater security: the card data is handled by Worldpay; it is not stored in Golfmanager.
Refunds from Golfmanager, without entering the Worldpay panel.
Payment modes it offers
Mode | What it is for |
Online payment | The customer pays by card when booking or buying online (consumer zone) |
Saved card | Charge with a card the customer previously saved |
In-person payment (terminal) | Charge at the POS with the Worldpay terminal |
Recurring charge | Automatically charge fees/memberships with the saved card |
Refund | Refund (full or partial) a sale charged with Worldpay |
Which systems does it connect and in which direction does the data travel?
It connects Golfmanager's checkout and POS with Worldpay, in real time:
In the online payment, the customer enters the card on Worldpay's secure form (the data does not pass through Golfmanager).
In the in-person payment, Golfmanager sends the charge to the terminal and receives the result live.
If approved, the sale is marked as paid. To refund, Golfmanager asks Worldpay for the refund.
🔒 Security: the card data is handled by Worldpay. If you save the customer's card, Golfmanager stores a secure reference (encrypted token) and the last digits, never the full number. If an online charge is approved but something fails afterwards in the system, Golfmanager refunds the customer automatically.
Prerequisites (before enabling the integration)
Have a Worldpay account (Access Worldpay). If you don't have one, you can request a free test (sandbox) account; the credentials are always provided by the Worldpay team.
Have the Worldpay module installed, together with the invoicing and POS modules.
Your Worldpay account data (user, password, Checkout ID, Entity ID).
For the in-person charge, a terminal compatible with Worldpay and its activation data.
Invoicing permissions to configure it.
How to install it
Option 1 — App Market: go to the App Market, search for Worldpay and install the module.
Option 2 — Manual installation: your implementation team can install it from the terminal. If in doubt, write to us through the blue bubble.
How to set it up (step by step)
Step 1 — Worldpay account data
Main Menu > Worldpay > Worldpay Settings
Go to Worldpay > Worldpay Settings.
Enter the User and Password of your account (they are stored encrypted).
Enter the Checkout ID and the Entity ID.
Indicate the Currency (for example,
GBPorEUR) and the Trade name (your company name the customer will see).Select the accepted card brands (Visa, Mastercard, Amex, etc.).
Leave Production Mode disabled to run tests and save the changes.
Step 2 — Terminal (only for in-person charging)
Main Menu > Worldpay > Payment Devices
Create a new device and give it a recognizable name (e.g. "Reception terminal").
Enter the terminal data Worldpay provides you (identifiers and activation code).
Click "Create POS LicenseKey" to activate it (it obtains its access key).
If it later expires, use "Update POS LicenseKey" to renew it. Save the changes.
⚠️ Recommendation: start with Production Mode disabled, make a test payment (online and, if applicable, with the terminal) and enable it only when everything works.
The configuration fields in detail
Below is an explanation of the Worldpay configuration fields.
1) User
• Field name: User
• Description: The API username that Worldpay provides you.
• Impact on the system: Identifies your account to Worldpay; it is stored encrypted.
• Usage example: you copy it from the sign-up Worldpay sends you.
What happens when it is used: it authenticates each charge or refund.
System behavior: if it is wrong, payments are not processed.
2) Password
• Field name: Password
• Description: The API password of your account. It is sensitive information.
• Impact on the system: Together with the user, it authenticates the connection; it is stored encrypted.
• Usage example: you enter it when configuring the account.
What happens when it is used: it allows communication with Worldpay.
System behavior: if it is wrong, authentication fails.
3) Checkout ID
• Field name: Checkout ID
• Description: Identifier of Worldpay's payment (checkout) form.
• Impact on the system: It is what loads the secure form where the customer types the card online.
• Usage example: you copy it from the Worldpay panel.
What happens when it is used: the payment form appears in the consumer zone.
System behavior: without it, the online payment cannot be shown.
4) Entity ID
• Field name: Entity ID
• Description: Identifier of the entity/merchant in Worldpay.
• Impact on the system: It indicates under which entity the charges are processed.
• Usage example: Worldpay provides it with your account.
What happens when it is used: payments are associated with your entity.
System behavior: if it is wrong, Worldpay rejects the operations.
5) Currency
• Field name: Currency
• Description: The currency in which payments are charged (e.g. GBP, EUR).
• Impact on the system: It determines the currency of each charge.
• Usage example: you put EUR if you charge in euros.
What happens when it is used: amounts are sent to Worldpay in that currency.
System behavior: it must match the currency of your Worldpay account.
6) Trade name
• Field name: Trade name
• Description: Your company name that the cardholder sees.
• Impact on the system: It is what appears associated with the charge for the customer.
• Usage example: you put your club's trade name.
What happens when it is used: the customer recognizes the charge by that name.
System behavior: it is informational for the cardholder.
7) Production Mode
• Field name: Production Mode
• Description: Switches between the test (sandbox) environment and the real charges one.
• Impact on the system: Enabled it charges for real; disabled it only simulates (sandbox).
• Usage example: you leave it disabled during setup and enable it once validated.
What happens when it is used: in production, cards are really charged.
System behavior: it uses the test or the real credentials/environment depending on the mode.
8) Accepted card brands
• Field name: Accepted card brands
• Description: Which card types you accept (Visa, Mastercard, Amex, Diners, Discover, JCB, Maestro).
• Impact on the system: Only the marked brands are accepted.
• Usage example: you enable Visa and Mastercard if those are the ones you accept.
What happens when it is used: the customer can pay with those brands.
System behavior: an unmarked brand is rejected.
9) Payment device (terminal)
• Field name: Payment device (Worldpay > Payment Devices)
• Description: Each Worldpay terminal registered, with its name and its identifiers/activation code.
• Impact on the system: It is needed to charge in person at the POS.
• Usage example: you create the terminal, fill in its data and click "Create POS LicenseKey".
What happens when it is used: the POS can send charges to that terminal.
System behavior: the access key is renewed with "Update POS LicenseKey" when it is about to expire.
ℹ️ Note: the names and exact location of some settings may vary depending on your version. Your implementation team and Worldpay provide you with the specific values.
How it is used day to day
Online payment and saved card
The customer chooses Worldpay when paying and enters their card in the Worldpay form.
If they tick "save card", it will be available for future payments and appear among their saved cards.
If they already have a saved card, they select it without typing it again.
Upon approval, the sale is marked as paid.
In-person payment at the POS
At the POS, select the charge with Worldpay in-person and choose the terminal.
The amount appears on the terminal; the customer inserts or taps the card.
Upon approval, the sale is paid and the receipt can be printed.
Refunds
To refund an online payment, open the sale/booking (for example, in Bookings > Occupancy) and cancel the payment: Golfmanager asks Worldpay for the refund (full or partial) and records it.
For an in-person refund, do it from the POS with the terminal; the customer presents the card and the receipt is printed.
Recurring payments and 3D Secure
Recurring charges (fees/memberships): if the customer saved their card for subscriptions, Golfmanager can charge automatically without the customer having to be present, as an alternative or complement to direct debit.
3D Secure: it is the bank's security verification. In some online payments, the customer must confirm with a code (OTP) or password on their bank's page before completing the payment.
Transactions, cards and devices
Main Menu > Worldpay
Worldpay Transactions: the record of all payments and refunds, with their result (correct or the error). It is the first screen to review when a charge does not complete; the most recent ones appear at the top.
Saved cards (Worldpay cards): the cards the customer has saved (brand and last digits), available for quick payments. They can be deleted, but not created manually.
Payment Devices: the registered terminals and their status.
Limitations to keep in mind
You need a Worldpay account and its data (the credentials are given by Worldpay).
The in-person charge requires a Worldpay terminal that is registered.
Saving cards depends on the customer accepting it.
Only the card brands you have configured are accepted.
Some payments require 3D Secure (bank confirmation).
It depends on Worldpay: if the service is unavailable, payments cannot be processed at that moment.
Frequently asked questions
Does Worldpay work for charging online and also at the counter?
Yes. It covers online payment in the consumer zone, in-person payment with a terminal at the POS, charging with a saved card and recurring charges.
Where do I get the user, password and Checkout ID?
They are provided by the Worldpay team when they set you up. If you don't have an account, you can request a free test (sandbox) one.
Is the card data stored in Golfmanager?
No. The sensitive data is handled by Worldpay. If the customer saves their card, Golfmanager only stores a secure reference (token) and the last digits.
Worldpay does not appear when paying. Why?
Usually some account data is missing or the method is not active. Check the user, password, Checkout ID and Entity ID of the active environment (test or production).
The payment is rejected.
It may be a declined, expired, no-funds card or a brand not accepted. Review the detail in Worldpay Transactions and the accepted brands; the customer will see an explanatory message.
The in-person payment does not complete.
Check that the terminal is registered and active, and that its access key has not expired (use "Update POS LicenseKey" to renew it).
It charges for real in a test (or does not charge in real).
The Production Mode is set wrong. Enable it for real charges or disable it for tests.
Can I do refunds from Golfmanager?
Yes, full or partial, without entering the Worldpay panel. The refund is recorded as a transaction of type "Refund".
What is 3D Secure and why is it asked of me?
It is the bank's security verification. In some online payments the customer confirms with a code (OTP) or password. It is normal and adds security.
Can I charge fees automatically with the saved card?
Yes. If the customer saved the card for subscriptions, automatic recurring charges (fees/memberships) can be made.
What happens if the customer is charged but something fails afterwards?
Golfmanager refunds the amount automatically so the customer is not left charged without their service, and it records the error.
Where do I see all the payments?
In Worldpay > Worldpay Transactions: payments, refunds and their result, with the most recent at the top.
Recommended best practices
Test first in sandbox mode before operating live.
Keep your Worldpay account data safe and do not share it; it is stored encrypted.
Enable "save cards" if you want to offer quick payments and recurring charges to regular customers.
Renew the terminal key in time ("Update POS LicenseKey") to avoid interruptions in the in-person charge.
For a failed payment, review Transactions first: the error detail usually indicates the cause.
Need help?
For the installation, the account configuration, registering the terminal or any question about the charges, write to us through the blue bubble in your management software. The account and terminal credentials are provided by the Worldpay team.