RCM Connect brings the Rental Car Manager (RCM) booking engine into your WordPress site. Your customers search, choose a vehicle, add insurance and extras, and pay without ever leaving your website. Bookings go straight into RCM, and payments are processed by VostroPay (Till Payments, a Nuvei company), by Windcave through your RCM account, or by Stripe.
This guide walks you through installing the plugin, configuring it, adding the booking form to your pages and tracking bookings in Google Analytics.
Before you start
You’ll need:
- WordPress 6.0 or later (6.7+ recommended)
- PHP 8.1 or later
- Your Autobridge licence key
- RCM API credentials (a key and secret), available from RCM
- A payment gateway: a VostroPay / Till Payments merchant account (public integration key, API key, username and password), Windcave set up in your RCM account, or a Stripe account connected to RCM (publishable and secret keys)
- Your payment gateway’s supplier ID in RCM, from RCM support
- An HTTPS site with the WordPress REST API (
/wp-json/) publicly reachable
Quick start
- Install the plugin from the zip file supplied with your purchase: in WordPress, go to Plugins → Add New Plugin, click Upload Plugin, choose the zip file and click Install Now, then Activate Plugin. Upload the zip as it is; there’s no need to unzip it first.
- Go to Settings → Autobridge – RCM Connect.
- On the General tab, enter your licence key and save.
- On the RCM & Payments tab, enter your RCM key and secret, choose a Payment Gateway and Transaction Type, enter that gateway’s settings, then save.
- Create a page for search results (e.g. Book a car), add the RCM Connect Search Results block and publish it.
- Back on the General tab, set Search Page to that page and save.
- Add the RCM Connect Search Form block wherever you want customers to start a search, such as your home page.
- Optional: sync your vehicles and insurance options so you can customise their names, descriptions and images.
- Turn on Use Sandbox and run a test booking before going live. It switches your payment gateway to its test environment too.
Updating: to install a new version, upload its zip file the same way. WordPress will tell you the plugin is already installed; click Replace current with uploaded. Your settings, synced vehicles and insurance options are kept. If your host blocks plugin uploads, unzip the file and copy its folder into wp-content/plugins/ instead, replacing the old one.
Settings
All settings live under Settings → Autobridge – RCM Connect, split across five tabs. Save Settings saves every tab at once.
General
| Setting | What it does |
|---|---|
| Autobridge Licence Key | The key supplied with your RCM Connect purchase. It’s checked once a day; saving your settings re-checks it straight away. |
| Search Page | The page that shows search results and runs the booking steps. It should contain the RCM Connect Search Results block. The Search Form block sends customers here when they search. |
| Terms & Conditions URL | When set, customers must tick “I agree to the Terms and Conditions” (linked to this URL) before they can continue to checkout. |
Without a valid licence, the booking form still loads but every vehicle shows as Unavailable. A notice in the WordPress admin explains what needs fixing.
RCM & Payments
Rental Car Manager
| Setting | What it does |
|---|---|
| Key / Secret | Your live RCM API credentials. |
| Key (sandbox) / Secret (sandbox) | Your RCM sandbox credentials, for testing. |
| Use Sandbox | Switches the booking form to your sandbox credentials, and your payment gateway to its test environment. |
The booking form won’t work until the credentials for the mode you’re using are filled in. The settings page shows a warning until they are.
Payments
| Setting | What it does |
|---|---|
| Payment Gateway | VostroPay (the default), Windcave (via RCM) or Stripe. Only the chosen gateway’s settings are shown. |
| Transaction Type | What happens to the customer’s card at checkout (see below). |
| Deposit Amount | Only shown for Validate card and take a deposit. The fixed amount charged at checkout. |
VostroPay via Till Payments
| Setting | What it does |
|---|---|
| Public Integration Key | Powers the card fields on the payment step. |
| API Key, Username, Password | Used to process transactions. |
| Shared Secret | Optional. From the connector in the VostroPay portal. When set, Till’s payment updates are checked against it before they’re trusted. |
| (test) versions of the above | Your Till test-gateway credentials, used with Till’s test gateway while Use Sandbox is on. |
Windcave (via RCM)
Your Windcave account is set up in RCM, so there are no Windcave credentials in the plugin. Use Sandbox decides which RCM account takes the payment, so ask RCM to confirm their sandbox is linked to a Windcave test account before you run test bookings.
On the payment step, Continue to payment creates the booking in RCM and shows Windcave’s secure card form on the page. When the customer submits it, Windcave sends the result to /wp-json/autobridge/v1/windcave-return, which checks it with RCM and records the payment against the booking. Make sure security plugins, firewalls and maintenance-mode plugins don’t block that address. A declined card can be retried on the same booking.
Customers who leave at the card form leave an unpaid booking in RCM. If a customer closes the page after paying but before Windcave sends them back, the payment shows in Windcave but not in RCM, so reconcile these by hand.
Stripe
| Setting | What it does |
|---|---|
| Publishable Key, Secret Key | From Developers → API keys in the Stripe account connected to RCM. |
| (test) versions of the above | Your Stripe test-mode keys, used while Use Sandbox is on. |
On the payment step, the customer enters their name and card in Stripe’s secure card form. Pay now creates the booking in RCM, then Stripe confirms the card, showing its own 3D Secure check if the customer’s bank asks for one. The plugin checks the payment with Stripe and records it against the booking in RCM, saving the card to a Stripe customer so RCM can charge it later. With Validate card only, the card is saved without being charged. A declined card can be retried on the same booking.
If a customer closes the page after Stripe takes the payment but before it’s recorded, the payment shows in Stripe but not in RCM, so reconcile these by hand.
Supplier IDs
| Setting | What it does |
|---|---|
| Supplier ID | Required. The chosen gateway’s supplier ID in your RCM account; ask RCM support for it. Until it’s set, customers can’t pay online and a notice in the WordPress admin says so. |
| Supplier Account ID | Only if RCM support has given you one. Sent to RCM with each payment. |
Each gateway has its own pair, shown with that gateway’s settings.
Transaction types
| Option | What happens |
|---|---|
| Validate card only (no charge) | The default. The card is checked and stored against the booking, but nothing is charged. You collect payment later. |
| Charge card in full | The full booking total is charged at checkout. |
| Validate card and take a deposit | The card is validated and the Deposit Amount is charged. Checkout shows the deposit and the balance due at pickup, which you collect yourself. |
With VostroPay, Till sends payment updates back to your site at /wp-json/autobridge/v1/transaction-callback. There’s nothing to set up, but make sure security plugins, firewalls and maintenance-mode plugins don’t block that address.
If a payment fails, your site’s admin email address (Settings → General → Administration Email Address) receives an email with the booking reference and error details.
Payments & security: card numbers are entered into Till’s secure hosted card fields, Windcave’s secure card form or Stripe’s secure card form and go straight to the payment gateway, so they never touch your server. Your RCM secret stays on your server and is never exposed to the browser.
Locations
Controls how your RCM pickup and drop-off locations appear in the search form. Each row has:
| Column | What it does |
|---|---|
| Location RCM ID | The location’s ID in RCM. |
| Label override | A name to show instead of RCM’s. Leave empty to keep RCM’s name. |
| Hidden | Removes the location from the form. |
Drag rows by the handle to change their order. Locations you haven’t listed still appear, in RCM’s order, after the listed ones. Use + Add Location to add a row and × to remove one.
To find a location’s RCM ID, run a search on your site and look for the p_loc value in the results page address, or check the location in RCM.
Vehicles & Insurance
This tab has two buttons that import data from RCM so you can customise how it’s displayed:
- Sync Vehicles from RCM creates a draft under Vehicles for each vehicle category in RCM.
- Sync Insurance Options from RCM creates a draft under Insurance Options for each insurance option.
Anything already synced is skipped, so syncing again never overwrites your edits.
Vehicles are synced based on availability at your first location, one week from today. If a vehicle is booked out or seasonal it may not come through. Sync again later, or create the vehicle yourself with the right RCM Vehicle ID.
Appearance
| Setting | What it does |
|---|---|
| Primary Color | The colour of buttons and calls to action throughout the booking flow. Leave empty for the default (black). |
Everything else, such as fonts and text colours, comes from your theme.
Adding the booking form to your site
The plugin adds two blocks, found under Widgets in the block inserter. Each can be used once per page.
| Block | Use it for |
|---|---|
| RCM Connect Search Form | A compact search form (locations, dates, times, driver age and promo code). Submitting it takes the customer to your Search Page. Great for your home page, landing pages or a sidebar. |
| RCM Connect Search Results | The full booking experience: search form, results, vehicle options, checkout and confirmation. Put it on the page you’ve chosen as your Search Page. |
Set up your search results page
- Go to Pages → Add New and give it a title (e.g. Book a car).
- Click +, search for RCM Connect Search Results and add it.
- Add any other content you like around it, then Publish.
- Go to Settings → Autobridge – RCM Connect → General, set Search Page to this page and save.
Add a search form
- Edit the page where you want customers to start their search.
- Click +, search for RCM Connect Search Form and add it.
- Optional: in the block’s Styles panel, under Color → Button, choose button colours for this block.
- Update or Publish the page.
The Search Form block needs a Search Page set, otherwise it has nowhere to send customers. You don’t need a Search Form on the results page itself, as the Search Results block already includes one.
Customising vehicles and insurance
Once synced, you can change how vehicles and insurance options are presented. Only published items are used, so you can sync everything and publish just the ones you’ve edited.
Vehicles
| Field | What it changes |
|---|---|
| Title | The vehicle’s display name. |
| Content | The vehicle description. |
| RCM Vehicle ID | Links the item to the vehicle category in RCM. Set by the sync, so only change it to fix a mismatch. |
| Features | Ticked features are listed on the vehicle card with their icons. |
| Image Override | Replaces RCM’s vehicle image. |
Insurance options
| Field | What it changes |
|---|---|
| Title | The insurance option’s name. |
| Content | Its description. |
| RCM Insurance ID | Links the item to the insurance option in RCM. |
Vehicle features
Reusable features such as Air conditioning or Bluetooth that you tick on each vehicle. Each has a title, an optional description and an icon. A starter set is created for you when the plugin is installed. Edit, delete or add to it as you like.
How the booking flow works
- Search: the customer picks pickup and drop-off locations, dates, times and driver age, plus an optional promo code. Drop-off defaults to the pickup location.
- Results: available vehicles with their total price, filterable by vehicle type.
- Options and details: insurance, mileage allowance, optional extras and the driver’s details. The price is double-checked with RCM before continuing, so customers never see a wrong total.
- Payment: a booking summary and the card form. Clicking Pay now (VostroPay or Stripe) or Continue to payment (Windcave) creates the booking in RCM and processes the card according to your Transaction Type.
- Confirmation: the booking reference and summary.
Promo codes are applied instantly, so customers see discounted prices straight away.
Linking straight to search results
Your search page can read a search from its address, so you can link customers directly to results, for example from a “Book this location” button or an ad:
https://your-site.com/book-a-car/?p_loc=1&p_date=2026-12-20&p_time=10:00&d_date=2026-12-27&d_time=10:00&a_id=7
| Parameter | Meaning | Example |
|---|---|---|
p_loc | Pickup location RCM ID | 1 |
d_loc | Drop-off location RCM ID (defaults to pickup) | 2 |
p_date / d_date | Pickup / drop-off date, YYYY-MM-DD | 2026-12-20 |
p_time / d_time | Pickup / drop-off time, 24-hour HH:MM | 10:00 |
a_id | Driver age option ID from RCM | 7 |
v_type | Vehicle type filter ID | 2 |
p_code | Promo code | SUMMER |
v_id | Vehicle category RCM ID to jump straight to | 1 |
When enough details are included, results load automatically. Anything missing falls back to the form’s defaults.
Adding v_id takes the customer straight to that vehicle’s options, skipping the results list. It’s ideal for “Book this car” buttons on vehicle pages. If the vehicle isn’t available for those dates, the customer is told and shown the other available vehicles instead.
Analytics and tracking
The booking form reports each step of the booking journey to Google Analytics 4 using GA4’s standard ecommerce events. That means GA4’s Monetization reports, purchase journey and item reports fill in without any custom report building.
The plugin doesn’t add a Google tag itself. Your site needs one already, either a Google Tag Manager container (added by your theme or a plugin like GTM4WP) or gtag.js.
- Tag Manager sites: events are pushed to the
dataLayerfor your tags to pick up. - gtag.js sites: events are sent straight to every GA4 property on the page.
Events
| Event | Sent when |
|---|---|
view_item_list | Search results load |
select_item | The customer clicks Select on a vehicle |
view_item | The options page loads for the chosen vehicle |
begin_checkout | The customer continues to the payment page |
add_payment_info | The booking is created in RCM, as the customer clicks Pay |
purchase | The payment is confirmed |
purchase is sent for every Transaction Type, and its value is always the full booking value, including fees and tax. So with Validate card only, the full booking price is reported as revenue even though nothing was charged at checkout. The payment_type parameter shows which Transaction Type applied.
What’s included
Every event includes the trip details: pickup_date, pickup_location_id, dropoff_date, dropoff_location_id and booking_length (in days). Search results also include lead_date (days until pickup), lead_group (e.g. 3 - 7 days), vehicle_type_id, vehicle_availables (number of vehicles shown) and coupon.
Each booking is broken into items:
| Item category | Price | Quantity |
|---|---|---|
Vehicle Rental | Effective daily rate | Rental days |
Insurance | Total insurance for the rental | 1 |
Mileage Allowance | Total for the chosen tier (left out when free) | 1 |
Optional Extra | Price per unit | Units selected |
Mandatory fees, location fees and tax aren’t items, but they’re included in the event’s total value, so item totals won’t add up to the booking value.
No personal details are sent as event parameters. On add_payment_info and purchase, the customer’s email and phone number are sent as user_data for Google Ads enhanced conversions.
Example: a purchase event
{
event: 'purchase',
pickup_date: '2026-10-17',
pickup_location_id: 1,
dropoff_date: '2026-10-22',
dropoff_location_id: 1,
booking_length: 5,
vehicle_type_id: 1,
ecommerce: {
transaction_id: '19680', // RCM booking number
currency: 'AUD',
value: 273.44, // full booking value
tax: 24.86,
coupon: '',
payment_type: 'register',
items: [
{ item_id: '1', item_name: 'Small Car', item_category: 'Vehicle Rental', price: 30, quantity: 5 },
{ item_id: '5', item_name: 'Liability reduction', item_category: 'Insurance', price: 100, quantity: 1 },
{ item_id: '13', item_name: 'Additional Driver', item_category: 'Optional Extra', price: 15, quantity: 1 },
],
},
user_data: {
email: 'customer@example.com',
phone_number: '+61412345678',
},
}
Setting up Google Tag Manager
- Variables: create Data Layer Variables (version 2) for the details you want to report, e.g.
pickup_date,pickup_location_id,booking_length,lead_group,vehicle_type_id. For enhanced conversions, adduser_data.emailanduser_data.phone_number. - Trigger: create a Custom Event trigger with the event name
view_item_list|select_item|view_item|begin_checkout|add_payment_info|purchaseand tick Use regex matching. - Tag: create a Google Analytics: GA4 Event tag using that trigger. Set Event Name to
{{Event}}, turn on More Settings → Ecommerce → Send Ecommerce data with Data Layer as the source, and add your variables as Event Parameters. - Google Ads (optional): use
purchaseas your conversion trigger and turn on user-provided data using theuser_datavariables. - Preview in Tag Manager, run a test booking and check each event in GA4 DebugView.
Setting up gtag.js
There’s nothing to configure. Run a test booking and check the events in GA4 DebugView. Don’t send the same GA4 property through both Tag Manager and gtag.js, or you’ll see duplicates.
GA4 custom dimensions
Custom parameters only appear in GA4 reports once they’re registered. In GA4, go to Admin → Custom definitions and create:
- Event-scoped custom dimensions for
pickup_location_id,dropoff_location_id,lead_group,vehicle_type_idandpayment_type - Custom metrics for
booking_length,lead_dateandvehicle_availablesif you’d like to see averages
Troubleshooting
| Problem | Likely cause |
|---|---|
| Every vehicle shows Unavailable | Your licence key is missing, invalid or expired. Check the admin notice and the General tab. |
| “RCM configuration is required” warning | The RCM key or secret is missing for the mode you’re using (live or sandbox). |
| The search form submits but nothing happens | Search Page isn’t set. |
| No vehicles are returned | There’s no availability in RCM for those dates and locations, or the credentials don’t match the mode you’re using. |
| “There was a problem calculating the total price” | Prices or fees changed in RCM while the customer was booking. Ask them to search again. If it keeps happening, check your fee setup in RCM. |
| “Online payment is unavailable” on the payment step | The payment gateway’s credentials or Supplier ID are missing for the mode you’re using (live or sandbox). The admin notice says which gateway. |
| Confirmation says the payment is pending (VostroPay) | Till hasn’t confirmed the payment yet. Make sure nothing blocks /wp-json/autobridge/v1/transaction-callback, and check the transaction in your Till dashboard. |
| “Payment could not be started” (Windcave) | The Supplier ID is wrong, or RCM couldn’t start the payment. Confirm the supplier ID with RCM support. |
| “Payment could not be started” (Stripe) | Stripe turned the request down, usually because the keys are wrong or are for the other mode (test vs live). Check them against your Stripe dashboard. |
| Some vehicles are missing after a sync | They weren’t available when you synced. Sync again later or add them yourself. |
Upgrading to version 1.4
Version 1.4 adds Stripe as a payment gateway and changes a few payment settings:
- VostroPay’s Test Mode setting is gone. Use Sandbox now switches VostroPay to Till’s test gateway too, so a site on live RCM always takes real payments. If your site was on live RCM with Test Mode on, it will start charging real cards after updating.
- Each gateway now has a required Supplier ID. Existing VostroPay sites are given 15, the value earlier versions always sent. Check it with RCM support if you’re unsure.
- If you’d set an RCM Supplier Account ID, it moves to VostroPay’s Supplier Account ID.
Upgrading from version 1.0
Version 1.1 switched to GA4’s standard ecommerce events. Earlier versions sent custom events called rentalSearch, bookingDetails and bookingPayment. If you have Tag Manager triggers, GA4 reports or audiences built on those names, update them to use the events listed in Analytics and tracking.