This article explains how to set up and configure the Windcave Payment Gateway in RMS, including eCommerce (online) and EFTPOS (in-person) payment processing, supported functions, and credential requirements.
Â
Overview
Windcave is a Payment Gateway available in RMS to provide PCI-compliant credit card storage and payment processing.
Payment Gateways are eCommerce applications provided by merchant services to authorise and process credit card payments in a PCI-compliant manner. Connecting a Windcave account with RMS provides:
- Secure credit card tokenisation and storage
- Payment processing (receipts)
- Refunds directly from within RMS for supported transaction types
Credit Card Tokens created using Windcave will only display the last two digits of the credit card. Completing the Windcave EFTPOS setup in this article will enable the Receipt Type "EFTPOS (Pymt Gateway)" in RMS.
Â
Â
Windcave Credentials
The following credentials are created and managed in your Windcave merchant account. RMS does not issue these details. You will need to obtain them from your Windcave merchant portal or directly from Windcave Support.
| Credential | Description | Used For |
|---|---|---|
| PXPost Username / PXPost Password | Credentials for PXPost, Windcave's server-to-server transaction service. | RMS uses these to process card payments and refunds securely without exposing card details. |
| PXPay User ID / PXPay Key | Credentials for PXPay, Windcave's hosted payment page service. | RMS uses these to redirect guests to a secure Windcave page for online payments (for example, Booking Engine, Guest Portal). |
| MOTO Rest User ID / MOTO Rest Key (optional) | Credentials for MOTO (Mail Order / Telephone Order) REST API access. | Used when processing card-not-present transactions via REST rather than PXPost. |
| HIT UserID / HITKey | Credentials for HIT (Host Integration Terminal), Windcave's EFTPOS terminal service. | RMS uses these to communicate with Windcave EFTPOS devices for in-person card payments. |
Â
Validation Behaviour (Token Creation)
When creating a Credit Card Token in RMS via Windcave:
- RMS will use a $0 validation request to verify the card details where possible.
- If the cardholder's bank does not support the $0 validation method, Windcave automatically falls back to a $1 authorisation to create the token.
- In both cases, this is a temporary authorisation used solely to validate the card. It is not a charge processed as a payment.
Â
Bendigo Bank Customers
Bendigo Bank customers must have an "auth/complete" process enabled on their merchant account to use Windcave in RMS.
The auth/complete process (also known as authorise and complete) allows an authorisation (holding funds on the card) and a later completion (capturing the funds) to be processed correctly through Windcave and RMS.
Â
Non-Credit Card Payments (Apple Pay, Google Pay, PayPal)
While Windcave technically supports a range of non-credit card digital payment methods, including Apple Pay, Google Pay, and PayPal, these payment types are not enabled or supported within the RMS-Windcave integration. This means:
- Even if these methods are enabled in your Windcave account, RMS will not send or receive transaction details for them.
- Transactions processed using these methods will not integrate cleanly into RMS for refunds, reconciliation, or reporting.
Â
Why Disable Non-Credit Card Methods?
Using alternative digital wallets or non-credit card payment methods through Windcave can create several operational issues when processed outside the RMS integration:
- Refund Limitations: Refunds processed via non-credit card payment methods may not correctly integrate with RMS, leading to manual handling or failed refund attempts.
- Reconciliation Challenges: Transactions from digital wallets often cannot be accurately matched between RMS and Windcave, creating inconsistencies in financial records.
- Reporting Gaps: Downstream reporting can become incomplete or inaccurate when using unsupported payment methods, affecting both operational and financial data quality.
RMS only accepts and supports standard credit card transactions through the Windcave integration. This ensures reliable refunds, clean reconciliation, and accurate reporting across all systems.
Â
Supported Functions
The table below shows which functions are supported for EFTPOS (in-person card-present) and eCommerce (online card-not-present) when using Windcave in RMS.
| Category | Function | EFTPOS | eCommerce |
|---|---|---|---|
| Tokens | CC Token - Reservation | Supported | Supported |
| CC Token - Guest Profile | Supported | Supported | |
| CC Token - Company | Supported | Supported | |
| CC Token - Travel Agent | Supported | Supported | |
| Pre-Auth Token - Reservation | Supported | Supported | |
| Payments | Receipt - CC Token | Not Supported | Supported |
| Receipt - Card Details | Supported | Supported | |
| Consume Pre-Auth Token | Not Supported | Supported | |
| Reverse a Receipt | Not Supported | Supported | |
| Refunds | Refund - Card Details | Supported | Supported |
| Blind Refund | Not Supported | Not Supported | |
| Reverse a Refund | Not Supported | Not Supported |
Â
Function Definitions
| Term | Definition |
|---|---|
| EFTPOS | Electronic Funds Transfer at Point of Sale. Payments processed with the card physically present using a connected EFTPOS device at the time of sale. |
| eCommerce | All card transactions processed electronically via the Internet. This includes payments processed in RMS with a Credit Card Token or Card Details, as well as payments processed via the RMS Booking Engine and Guest Portal. |
Â
Setup Guide
Payment Gateway (eCommerce)
In the side menu of RMS, go to Setup > Property Options > Property Information.
- Select Edit on an existing Property.
 - Navigate to the Payment Gateway tab.
- Select the Toggle Ecommerce Online.
- Select Windcave as the Payment Gateway.
- Enter the PXPost Username (obtained from your Windcave merchant portal or Windcave Support).
- Enter the PXPost Password.
- Enter the PXPay User ID.
- Enter the PXPay Key.
(Optional) Enter the MOTO Rest User ID & MOTO Rest Key (only required if processing MOTO transactions
via REST).
(Optional) Select the checkbox Use Credit Card Fee from Windcave. - Select the Pre Authorisation Calculation and Amount if applicable.
(Optional) Select the checkbox Warn if no Pre-Authorisation exists on Check-in. - Select Save/Exit.
Â
EFTPOS
In the side menu of RMS, go to Setup > Property Options > Property Information.
- Select Edit on an existing Property.
 - Navigate to the Payment Gateway tab.
- Select the toggle EFTPOS Terminal Payment Gateway.
- Select Windcave.
- Enter the HIT UserID (obtained from your Windcave merchant portal or Windcave Support).
- Enter the HITKey.
(Optional) Select the checkbox Use Credit Card Fee from Windcave. - Select Save/Exit.
Â
EFTPOS Terminal
After enabling the EFTPOS gateway on the Property, you must add each physical EFTPOS terminal in RMS.
In the side menu of RMS, go to Setup > Lookup Tables > EFTPOS (Pymt Gateway).
- Select Add.
 - Select a Property.
- Enter a Description.
- Enter the Station Number.
- Select Save/Exit.
Â
Processing a Payment
When processing a receipt via the Windcave gateway (either in RMS or online), a Windcave payment form will be displayed.
- Complete all mandatory fields on the Windcave payment form.
- Select Submit to finalise the transaction.
RMS will pre-populate information where possible. This can be overridden if needed.
Â
Â
Comments
0 comments
Please sign in to leave a comment.