Rotterdampas is the official annual discount pass for greater Rotterdam, issued for residents and students and covering hundreds of cultural, leisure, sport and family venues with free or discounted entry. For operators, it brings a local and domestic audience, roughly 170,000 pass holders a year who visit repeatedly and off-peak, with museums, attractions and family activities the main redemptions. Rotterdampas uses Intersolve as their primary ticketing system.
Connecting Rotterdampas to Ventrata lets you scan, validate and redeem Rotterdampas passes at your entrance, on Ventrata-powered turnstiles, kiosks, point-of-sale terminals, the mobile app or the Ventrata Dashboard, without a separate Rotterdampas app.
To learn more about Rotterdampas, visit rotterdampas.nl.
📒 NOTE
Rotterdampas runs on Intersolve. See Intersolve: Reseller Connection.
Primary website | |
Tags | Multi-Attraction Pass |
Connection type | Pass redemption: you scan Rotterdampas passes at your entrance |
Connection features | Product Mapping · Redemption Sync · Pass Walkup Scanning Sync |
Developed by | Ventrata (using Rotterdampas API) |
This connection lets you:
Scan or type a Rotterdampas card number and see the vouchers on that card that are valid at your venue.
Create a booking in Ventrata automatically for every usable voucher, so one scan can admit several vouchers.
Record the voucher use with Rotterdampas at scan time, or later when the visitor is admitted or marked as a no-show.
How It Works
Staff scan or type a Rotterdampas card number, optionally followed by #PIN.
Ventrata asks Rotterdampas (Intersolve) for the vouchers issued to that card.
Each usable voucher becomes its own redeemable code (/), so one card can return several bookings.
Vouchers with status Normal get a new booking, or the existing one is returned. Vouchers already Redeemed only return an existing Ventrata booking.
Ventrata builds an open-dated booking for each voucher using the product, option and unit you mapped to that voucher type.
Ventrata sends Redeem to Rotterdampas for each ticket, either right away or later, depending on your redemption settings.
📒 NOTE
A Rotterdampas card number, optionally followed by #PIN. Either the short 1-7 digit number (Ventrata pads it with the fixed Rotterdampas prefix to the 19-digit form) or the full prefixed number.
Creating the Rotterdampas Connection
🔐 Required Role Permissions: See Connections, Modify Connections
Before you begin:
Have your Rotterdampas API User Name and Password ready.
Create Rotterdampas as a reseller in Ventrata if you want bookings recorded under it (the Reseller field is optional in the form).
Have a real Rotterdampas card with your vouchers on it. Voucher types only appear for mapping after a card has been scanned.
Create the connection
Select your Rotterdampas reseller (optional).
Enter the Rotterdampas User Name and Password.
Choose when the redemption is sent: leave both options off to redeem at scan time, or tick Redeem on Redemption/Upgrade and/or Redeem on No-show.
Save. Ventrata validates the credentials with Rotterdampas.
The connection form has these options:
Reseller | The reseller that Rotterdampas bookings are recorded under. Optional in the form. |
Rotterdampas User Name / Password | Required. Ventrata checks them with a test call when you create the connection or change them; if they fail, both fields are flagged invalid. |
Redeem on Redemption/Upgrade | Send the redemption to the connected provider when the booking is redeemed in Ventrata. |
Redeem on No-show | Send the redemption to the connected provider when the booking is marked as a no-show in Ventrata, including automatic no-shows. |
Mapping Products
Rows are created the first time Ventrata sees a voucher type (VoucherId) on a scanned card. There is no list to load in advance.
Scan a Rotterdampas card that carries your voucher.
Open the connection and find the new row for that voucher type.
Choose the Ventrata product, option and unit to book. Option and unit are required.
Scan the card again to create the booking.
📒 NOTE
A row only counts as mapped if the product is active and the option and unit are set and not discarded.
📒 NOTE
Until a row is mapped, the voucher fails with " is not mapped in <connection>".
Redemption
Immediately: Default (both options off): at scan time Ventrata validates the order and sends Redeem to Rotterdampas for each ticket.
On redemption or no-show: With Redeem on Redemption/Upgrade and/or Redeem on No-show ticked, the booking is saved but not yet redeemed at Rotterdampas. Ventrata sends Redeem when the ticket is redeemed or upgraded in Ventrata, or marked as a no-show.
What's sent to Rotterdampas: A Redeem request for the issued voucher, with the ticket price as TransactionAmount in cents and a fixed reference per ticket so a retry doesn't redeem twice.
Connection Features Detailed
This section is for anyone who wants the detail. Click a row to see how each feature works.
Product Mapping | ✅ |
You map each Rotterdampas pass listing to a Ventrata product in the Ventrata Dashboard. Rows are created the first time Ventrata sees a voucher type (VoucherId) on a scanned card. There is no list to load in advance. A row only counts as mapped if the product is active and the option and unit are set and not discarded. Until a row is mapped, the voucher fails with " is not mapped in <connection>". |
Content Sync | ❌ |
Product content isn't synced. Rotterdampas sells its own pass. Your products and their content stay in Ventrata. |
Availability Sync | ❌ |
Your availability isn't shared with Rotterdampas. There is no availability or capacity exchange with Rotterdampas. |
Pricing Sync | ❌ |
Prices aren't synced with Rotterdampas. The booking uses your Ventrata unit price and is balanced with a voucher transaction. At redemption, Ventrata sends the ticket price to Rotterdampas as TransactionAmount in minor units (cents). |
Promotions Sync | ❌ |
Promotions don't apply to Rotterdampas passes. Your Ventrata promotions don't apply to bookings made by scanning a pass. |
Bookings Sync | ✅ / ❌ |
Limited: bookings are created only when a pass is scanned. One open-dated booking per usable voucher, so one scan can create several bookings. Voucher IDs are reused between seasons, so Ventrata only matches an earlier booking made inside the voucher's valid-from/valid-until window with the same product, option and unit. There is no cancel or un-redeem call to Rotterdampas. |
Pickups/Dropoff Sync | ❌ |
Not part of this connection. Pass redemptions don't carry pickups. |
Custom Questions Sync | ❌ |
Not part of this connection. Booking questions aren't asked or sent for pass redemptions. |
Extras Sync | ❌ |
Not part of this connection. Extras can't be added to a pass redemption. |
Redemption Sync | ✅ |
Redemptions are sent to Rotterdampas. Default (both options off): at scan time Ventrata validates the order and sends Redeem to Rotterdampas for each ticket. With Redeem on Redemption/Upgrade and/or Redeem on No-show ticked, the booking is saved but not yet redeemed at Rotterdampas. Ventrata sends Redeem when the ticket is redeemed or upgraded in Ventrata, or marked as a no-show. A Redeem request for the issued voucher, with the ticket price as TransactionAmount in cents and a fixed reference per ticket so a retry doesn't redeem twice. |
Pass Walkup Scanning Sync | ✅ |
You scan Rotterdampas passes at your entrance. Staff scan or type a Rotterdampas card number, optionally followed by #PIN. Ventrata asks Rotterdampas (Intersolve) for the vouchers issued to that card. Each usable voucher becomes its own redeemable code (/), so one card can return several bookings. |
Gift Card Sync | ❌ |
Not part of this connection. Rotterdampas passes aren't Ventrata gift cards. |
✅ supported · ✅ / ❌ limited · ❌ not supported
Good to know: limits of this connection
Good to know: limits of this connection
Voucher types appear for mapping only after a real card has been scanned, so you can't map ahead of go-live unless you know the voucher IDs.
A voucher already redeemed elsewhere is never admitted again in Ventrata.
Rotterdampas error texts are shown to staff word for word.
Requests time out after 20 seconds.
No pickups, extras, custom questions or resources.
Troubleshooting
"%{title} is not mapped in %{connection}"
"%{title} is not mapped in %{connection}"
The voucher type has no Ventrata product, option and unit mapped. Map the row on the connection, then scan again.
"Invalid card status: %{status}"
"Invalid card status: %{status}"
The voucher's status at Rotterdampas is neither Normal nor Redeemed.
"Redemption not allowed"
"Redemption not allowed"
"This Rotterdampas voucher has already been redeemed"
"This Rotterdampas voucher has already been redeemed"
The voucher was used elsewhere and has no booking in your Ventrata account.
"Invalid response from Rotterdampas"
"Invalid response from Rotterdampas"
Rotterdampas sent a response Ventrata couldn't read.
"Rotterdampas request failed (code %{code})"
"Rotterdampas request failed (code %{code})"
Rotterdampas returned an error code without a description.
FAQs
Why did one scan create several bookings?
Why did one scan create several bookings?
A Rotterdampas card can carry several vouchers. Ventrata creates one booking for each usable voucher.
How do Rotterdampas and Intersolve relate?
How do Rotterdampas and Intersolve relate?
Rotterdampas runs on Intersolve's voucher platform. Intersolve built the Rotterdampas and is its ticketing system, so this connection talks to Intersolve's API.
What happens if staff scan the card again?
What happens if staff scan the card again?
For a voucher already booked in Ventrata, the existing booking is returned instead of a new one. If retried, the Redeem request uses the same reference, so Rotterdampas isn't charged twice.
Useful Resources
📚 More about Ventrata connections
Partner Information
Gemeente Rotterdam
Rotterdampas Servicepunt, Halvemaanpassage 90 (Timmerhuis), 3011 DL Rotterdam
Netherlands
Ventrata Partner ID: 1ae100da-b3b2-4726-a71e-6185dd3f65db