Index
What is this integration?
The Redsys integration connects Golfmanager with the Redsys payment gateway, the most widely used in Spain (used by most banks). It lets you charge online by card, save the customer's card for future payments, charge in person with a card terminal at the POS, and process refunds.
A payment gateway is the service that connects your business with the banks to charge cards securely. Redsys is the standard gateway in Spain; your bank provides you with a "merchant" (virtual POS) and a set of keys to use it.
What problem does it solve?
Charge across all channels 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: card data is handled by Redsys; it is not stored in Golfmanager.
Refunds from Golfmanager, without entering the Redsys panel.
Payment methods it offers
Method | What it is for |
Online payment | The customer pays by card when booking or buying online |
Saved card | Charge a card the customer saved previously |
In-person payment (card terminal) | Charge at the POS with the Redsys card terminal |
Refund | Refund a sale charged with Redsys |
Which systems does it connect and in which direction does the data travel?
It connects the Golfmanager checkout and POS with Redsys, in real time:
In the online payment, the customer enters the card in the secure Redsys environment; Redsys authorizes and reports the result.
In the in-person payment, Golfmanager sends the charge to the card terminal and receives the result.
If approved, the sale is marked as paid. To refund, Golfmanager asks Redsys for the refund.
🔒 Security: card data is handled in Redsys. If you save the customer's card, Golfmanager stores a secure reference (token) and the last digits, never the full number.
Prerequisites (before enabling the integration)
Have a Redsys merchant (virtual POS) contracted with your bank.
Have the Redsys module installed, together with the invoicing module.
The Redsys keys (test and production) provided by your bank.
For in-person charging, the merchant code and the signing key, and a Redsys card terminal.
Invoicing permissions to configure it.
Signing up with your bank (prior process)
Before configuring Golfmanager, you must contract the Redsys gateway with your bank. The usual process is:
Contact your bank and request a Redsys payment gateway to receive online payments.
Provide the merchant details they ask for:
Name: your company's name.
Merchant URL: the address of your booking site (consumer), for example
https://eu.golfmanager.com/yourtenant(replace with your tenant name).Merchant email and Status: Active.
Indicate these gateway parameters: Online notification: HTTP, Synchronization: Synchronous SOAP, Send parameters in URLs: No.
You will receive an email with access in Test Mode to the Redsys private banking portal, with the data you will need: Merchant Code (FUC), Terminal, Currency (€ = 978), test URL (usually
https://sis-t.redsys.es:25443/sis/realizarPago) and the test password.After testing, email Redsys again stating you want to switch to Real Mode. You will receive a second email with the production data.
ℹ️ The Merchant Code (FUC) is your merchant number and the Terminal identifies the virtual POS within that merchant. Both are provided by Redsys/your bank.
How to set it up (step by step)
Location: Settings Menu > Invoicing > Redsys Settings
Step 1 — Online payment
Go to Settings Menu > Invoicing > Redsys Settings.
Enable Synchronous SOAP notification.
Enter the Currency (978 for euros) and the Terminal (usually 1).
Enter the test keys (public test key and private test key) to validate first in test mode.
Enter the production keys (public production key and production secret key, both mandatory).
Decide whether to enable Tokenize cards (do not enable it until Redsys confirms it).
Optional: enable Prevent the user from deleting their cards.
When everything is validated, enable Production Mode.
Save the changes.
Step 2 — In-person payment (card terminal)
In the Redsys in-person section, enter the merchant code and the signing key.
Set a notification email.
Start with production mode disabled, make a test payment, and enable it only when it works.
Save the changes.
⚠️ Recommendation: always start with production mode disabled and make a test payment; enable it only when everything works. Secret keys are stored encrypted.
The configuration fields in detail
Below is an explanation of each field in the Redsys configuration.
1) Production Mode
• Field name: Production Mode
• Description: Determines whether charges are made in the real (production) environment or the test one.
• Impact on the system: When enabled, the production keys are used and charges are real; when disabled, the test keys are used and no real charge is made.
• Usage example: you leave it disabled until validated, and enable it when going live.
What happens when it is used: once enabled, the next payments charge real money to cards.
System behavior: if set wrong, you will charge for real in a test or fail to charge in production.
2) Terminal
• Field name: Terminal
• Description: Terminal number of the virtual POS within your Redsys merchant (usually 1).
• Impact on the system: It must match the terminal Redsys assigned you.
• Usage example: you enter 1 (the one indicated in your Redsys email).
What happens when it is used: payments are processed against that terminal.
System behavior: a wrong terminal causes payments to be rejected.
3) Currency
• Field name: Currency
• Description: Numeric currency code. The euro is 978.
• Impact on the system: Defines the currency in which charges are sent to Redsys.
• Usage example: you enter 978 for euros.
What happens when it is used: amounts are charged in that currency.
System behavior: a wrong currency may cause rejections.
4) Public production key
• Field name: Public production key (mandatory)
• Description: Public identifier of your merchant in the real environment, provided by Redsys.
• Impact on the system: Required to operate in production.
• Usage example: you copy it from Redsys's second email (Real Mode).
What happens when it is used: it identifies your merchant in real charges.
System behavior: without it, you cannot charge in production.
5) Production secret key
• Field name: Production secret key (mandatory)
• Description: Secret signing key (SHA-256) for the real environment. It is sensitive information and is stored encrypted.
• Impact on the system: It signs and validates every operation with Redsys in production.
• Usage example: you paste it from the Redsys private banking portal.
What happens when it is used: it guarantees that the communication with Redsys is authentic.
System behavior: a wrong key makes Redsys reject operations due to an invalid signature.
6) Public test key and Private test key
• Field name: Public test key / Private test key
• Description: The equivalents of the production keys, but for the test environment.
• Impact on the system: They let you validate the integration without charging real money.
• Usage example: you use them with Production Mode disabled.
What happens when it is used: payments are simulated in the Redsys test environment.
System behavior: they are only used when Production Mode is disabled.
7) Synchronous SOAP notification
• Field name: Synchronous SOAP notification
• Description: Enables immediate confirmation of the payment with Redsys.
• Impact on the system: It allows rejecting payments directly if the confirmation fails (for example, paying a booking that has already expired).
• Usage example: you enable it to avoid payments on invalid bookings.
What happens when it is used: if the sale is no longer valid at the moment of confirmation, the payment is rejected.
System behavior: it adds a real-time check before accepting the payment as valid.
8) Tokenize cards
• Field name: Tokenize cards (also "Pay with tokens")
• Description: Allows saving the customer's card as a secure reference (token) for future charges.
• Impact on the system: It enables saved "Redsys cards" and charging with a saved card. Do not enable it until Redsys confirms the service is enabled.
• Usage example: you enable it when Redsys confirms payment by reference.
What happens when it is used: the customer can choose to save their card and reuse it.
System behavior: Golfmanager stores only the token and the last digits, never the full number.
9) Save card automatically
• Field name: Save card automatically ("Save credit card automatically")
• Description: Saves the card after an online payment (when the customer consents) with no extra steps.
• Impact on the system: Makes it easier to have saved cards to charge later at the POS.
• Usage example: you enable it together with tokenization for regular customers.
What happens when it is used: the customer's card becomes available for later charges.
System behavior: it requires tokenization to be active and Redsys to allow it.
10) Prevent the user from deleting their cards
• Field name: Prevent the user from deleting their cards
• Description: Stops the customer from deleting saved cards on their own.
• Impact on the system: Useful when the club wants to ensure the collection of recurring services.
• Usage example: you enable it if you rely on the saved card for fees or no-shows.
What happens when it is used: the customer does not see the option to delete their cards.
System behavior: saved cards remain available for the club.
11) Redsys in-person: Merchant code and Signing key
• Field name: Merchant code / Signing key (Redsys in-person section)
• Description: Merchant data for charging with the card terminal at the POS.
• Impact on the system: They allow charges to be sent to the terminal and validate the in-person operations.
• Usage example: they are provided by your bank for the physical POS.
What happens when it is used: when charging at the POS, the amount is sent to the terminal.
System behavior: incorrect data prevents completing the in-person charge.
ℹ️ Note: the exact names may vary slightly depending on your version and language. The function of each field is as described.
Enabling the tokenized card to charge at the POS
If you want to be able to charge at the POS with a card the customer saved online (payment by reference):
Ask Redsys Customer Service to enable in your merchant: payment by reference, returning the last 4 digits of the card, and non-secure payment.
When they confirm they are enabled, go to Settings Menu > Redsys > General.
Enable Pay with tokens.
Enable Save credit card automatically.
Run the relevant tests to check it works.
🔒 Important: Golfmanager does not store any card data; the payment gateway stores it for security. The system only shows the last 4 digits so it can be used in tokenization, and only when the customer, during the online purchase, confirms they want to save it for future purchases.
How it is used day to day
Online payment and saved card
The customer chooses Redsys when paying and enters their card in the secure Redsys environment.
If allowed, they can save the card for future payments.
When approved, the sale is marked as paid.
In-person payment at the POS
At the POS, select "Redsys in-person"; the charge is sent to the card terminal and the customer presents the card.
Refunds
To refund a Redsys payment, cancel the payment from Golfmanager: the system requests the refund from Redsys and records it.
Transactions and saved cards
Redsys transactions: the record of all payments and refunds, with their result. It is the first screen to check when a charge has not been completed.
Redsys cards: the saved cards. In each customer's record there is a "Redsys cards" tab with their cards (last digits and which is the main one).
Limitations to keep in mind
You need a Redsys merchant contracted with your bank and its keys.
In-person charging requires a Redsys card terminal and its configuration (merchant code and signing key).
Saving cards depends on the configuration and on the customer accepting it; in addition, Redsys must have the payment-by-reference services enabled.
Test and production keys are different: remember to enable production mode to charge for real.
It depends on Redsys: if the service is unavailable, payments cannot be processed at that moment.
Frequently asked questions
Does Golfmanager store card data?
No. The full card data is kept by Redsys for security. Golfmanager only stores a secure reference (token) and the last 4 digits, and only if the customer agrees to save the card.
Redsys does not appear when paying. Why?
The usual cause is that the keys are missing for the active environment or the method is not active. Check the keys of the relevant environment (test or production) and that the module is configured.
The payment is rejected. What do I do?
The card may be declined or the (3DS) verification may not complete. Check the detail in Redsys transactions; the customer can try another card.
I get the error "0180 - Card out of service". What does it mean?
It is not a Golfmanager or gateway failure: it is a standard Redsys code returned by the issuing bank of the customer's card. It indicates the card is marked as "out of service".
What are the causes of error 0180?
The most common: card cancelled (expired, replaced or blocked), temporary block by the issuer due to suspected fraud, card not yet activated, card not enabled for e-commerce, or issuer restrictions for online/international payments the customer has not activated.
How is error 0180 resolved?
It is a matter between the customer and their bank, not the club. It is recommended that the customer contact their bank, try another card and verify their card allows online payments with 3DS. The club does not need to do anything technical. Only if many different customers get the same error is it worth reviewing the tenant's Redsys configuration (FUC, terminal, production mode).
The in-person payment does not complete.
It is usually due to incorrect terminal data or the card not being presented. Check the merchant code and the signing key and try again.
It charges for real in a test (or does not charge in production).
The Production Mode is set incorrectly. Enable it for real charges and disable it for tests.
What is the "Synchronous SOAP notification" and why enable it?
It is an immediate confirmation that allows rejecting the payment if the sale is no longer valid at that moment (for example, an expired booking). It avoids charging for something that no longer applies.
Can I charge a customer with their saved card?
Yes, if you have tokenization enabled and Redsys has enabled payment by reference. The saved card appears in the "Redsys cards" tab of the customer's record.
Where do I see whether a charge completed?
In Redsys transactions. Each operation shows its result and the error detail if there was one.
Can I make refunds from Golfmanager?
Yes. When cancelling a Redsys payment, Golfmanager requests the refund from Redsys and records it, without having to enter the Redsys panel.
Recommended best practices
Test first in test mode with the Redsys test card before operating live.
Keep the production keys safe and do not share them; they are stored encrypted.
Enable "tokenize cards" only when Redsys confirms payment by reference.
For a failed payment, check Transactions first: the error detail usually indicates the cause.
Verify the production mode before you start charging for real.
Need help?
If you have questions about the keys, the configuration or a charge that does not complete, our support team is available to help you. Write to us through the blue bubble in your management software. For the merchant sign-up, production keys, enabling payment by reference or bank-side incidents (such as error 0180), also contact Redsys or your bank.