Berlin WelcomeCard is the official tourist ticket of Berlin, issued by the tourist board visitBerlin and sold more than 15 million times. It pairs unlimited public transport in zones AB or ABC with discounts at more than 170 attractions, and upgrades add Museum Island entry or free admission to 25+ attractions. For attractions, it brings first-time and repeat city visitors from Germany and abroad who buy the card online or at sales outlets and plan sightseeing around it. This connection is developed and managed by Public Ticket Solution.

Connecting Berlin WelcomeCard to Ventrata lets you scan, validate and redeem Berlin WelcomeCard passes at your entrance, on Ventrata-powered turnstiles, kiosks, point-of-sale terminals, the mobile app or the Ventrata Dashboard, without a separate Berlin WelcomeCard app.

To learn more about Berlin WelcomeCard, visit berlin-welcomecard.de.

Primary website	berlin-welcomecard.de
Tags	Destination Organization (DMO) · Multi-Attraction Pass
Connection type	Pass redemption: you scan Berlin WelcomeCard passes at your entrance
Connection features	Product Mapping · Redemption Sync · Pass Walkup Scanning Sync
Developed by	Ventrata (using visitBerlin Ticket Gateway API)

This connection lets you:

Scan or type a Berlin WelcomeCard ticket code in Ventrata and check it with Berlin WelcomeCard in real time.
Create a booking in Ventrata automatically for every valid ticket.
Record the entry with Berlin WelcomeCard at the moment you scan, so the ticket is marked as used.

How It Works

Staff scan or type a WelcomeCard ticket code in Ventrata: in Backoffice order search, on a Ventrata scanner or terminal, or through Ventrata's OCTO redemption/check-in API.
Ventrata only treats codes that start with "TE" followed by at least 12 characters as WelcomeCard tickets. Other codes are left for your other connections.
If the ticket was already booked for this reseller, Ventrata returns that existing booking.
Otherwise Ventrata sends a query-only scan to Berlin WelcomeCard to check the ticket and find its product variant.
Ventrata then records an entry scan with Berlin WelcomeCard, using your Entry Zone ID and Organization ID and the current time.
If Berlin WelcomeCard confirms success, Ventrata saves an open-dated booking for 1 unit of the product, option and unit you mapped to that variant.

📒 NOTE

Ticket codes that match "TE" followed by at least 12 letters or digits (regex ^TE\w{12,}$). Any other code is ignored by this connection.

Creating the Berlin WelcomeCard Connection

🔐 Required Role Permissions: See Connections, Modify Connections

Before you begin:

Have your Berlin WelcomeCard API credentials ready: Username, Password, Product ID, Organization ID and Entry Zone ID.
Create Berlin WelcomeCard as a reseller in Ventrata and select it on the connection. The form marks Reseller as optional, but lookups need it.

Create the connection

Select your Berlin WelcomeCard reseller.
Enter the Username, Password, Product ID, Organization ID and Entry Zone ID.
Save. Ventrata logs in, fetches the product and its variants, and creates one mapping row per variant.

The connection form has these options:

Reseller	The reseller that WelcomeCard bookings are recorded under. Optional in the form, but needed in practice for lookups.
Berlin Welcomecard Username / Password	Ventrata logs in with these when you save. If login fails, both fields are flagged invalid.
Berlin Welcomecard Product ID	The WelcomeCard product whose variants Ventrata loads for mapping. If the product isn't found, the field is flagged invalid.
Berlin Welcomecard Organization ID	Sent with every entry scan. Not checked when you save.
Berlin Welcomecard Entry Zone ID	The entry zone each scan is recorded against. Not checked when you save; a wrong value only shows up at scan time.

Mapping Products

When you save the connection, Ventrata creates one row per variant of the configured WelcomeCard product. Variants that no longer exist are removed. If a scanned ticket belongs to a variant with no row yet, Ventrata adds the row at scan time.

Open the connection and select each variant row.
Choose the Ventrata product, option and unit to book for that variant. Option and unit are required.
Re-save the connection whenever WelcomeCard variants change. Rows only refresh on save.

📒 NOTE

A ticket for an unmapped variant fails with " is not mapped in <connection>" until you map it.

Redemption

Immediately: Always. The entry scan is recorded with Berlin WelcomeCard at the moment you scan, and the booking is saved only if the provider reports success.
On redemption or no-show: Not supported. The Redeem on Redemption/Upgrade and Redeem on No-show options don't appear for this connection.
What's sent to Berlin WelcomeCard: An entry scan event (scanEventCreate, kind entry) with your entry zone, organization, the current time and device name "Ventrata".

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 Berlin WelcomeCard pass listing to a Ventrata product in the Ventrata Dashboard. When you save the connection, Ventrata creates one row per variant of the configured WelcomeCard product. Variants that no longer exist are removed. If a scanned ticket belongs to a variant with no row yet, Ventrata adds the row at scan time. A ticket for an unmapped variant fails with " is not mapped in <connection>" until you map it.
Content Sync	❌	Product content isn't synced. Berlin WelcomeCard sells its own pass. Your products and their content stay in Ventrata.
Availability Sync	❌	Your availability isn't shared with Berlin WelcomeCard. There is no availability or capacity exchange with Berlin WelcomeCard.
Pricing Sync	❌	Prices aren't synced with Berlin WelcomeCard. The booking uses your Ventrata unit price and is settled by voucher, so the order balances to zero. No price is sent to Berlin WelcomeCard.
Promotions Sync	❌	Promotions don't apply to Berlin WelcomeCard 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 ticket, with quantity 1 of the mapped unit, created when the ticket is scanned. The reseller reference is the ticket code without its "TE" prefix. Customer, question, transport and accompanied-by checks are skipped. Rescanning the same ticket returns the existing booking. There is no cancel call to Berlin WelcomeCard. A recorded scan can't be undone from Ventrata.
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 Berlin WelcomeCard. Always. The entry scan is recorded with Berlin WelcomeCard at the moment you scan, and the booking is saved only if the provider reports success. Not supported. The Redeem on Redemption/Upgrade and Redeem on No-show options don't appear for this connection. An entry scan event (scanEventCreate, kind entry) with your entry zone, organization, the current time and device name "Ventrata".
Pass Walkup Scanning Sync	✅	You scan Berlin WelcomeCard passes at your entrance. Staff scan or type a WelcomeCard ticket code in Ventrata: in Backoffice order search, on a Ventrata scanner or terminal, or through Ventrata's OCTO redemption/check-in API. Ventrata only treats codes that start with "TE" followed by at least 12 characters as WelcomeCard tickets. Other codes are left for your other connections. If the ticket was already booked for this reseller, Ventrata returns that existing booking.
Gift Card Sync	❌	Not part of this connection. Berlin WelcomeCard passes aren't Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits of this connection

One WelcomeCard Product ID per connection. To accept several WelcomeCard products, you likely need one connection per product.
Mappings refresh only when you re-save the connection.
Redemption can't be deferred to admission or no-show.
No pickups, extras, custom questions or resources.
Lookup results are cached for 5 minutes. If Berlin WelcomeCard doesn't respond within about 12 seconds, the code is treated as not found.

Troubleshooting

"%{title} is not mapped in %{connection}"

The ticket's variant has no Ventrata product, option and unit mapped. Map the variant row on the connection, then scan again.

"Redemption not allowed"