Short answer: When you share hotel proof alongside a dummy ticket, send a genuine reservation confirmation that shows the property, guest, reference, status and stay dates—but not a self-check-in door code. Prefer the issuer’s code-free copy. If a later PDF contains access details, use proper redaction and test the saved file; never change the booking facts. Match the accommodation dates to the separate flight itinerary.
This is a document-sharing and physical-access guide, not a promise that any hotel proof will satisfy a visa checklist. It is distinct from the separate Booking.com confirmation-number and PIN guide: here the secret can open the accommodation itself.
Key facts
- Door, lockbox and backup codes are access secrets, not reservation-verification fields.
- Airbnb normally shares ordinary self-check-in instructions near arrival; connected smart-lock codes may be sent after booking.
- Keep genuine booking details readable and ask the issuer for a code-free confirmation first.
- A black rectangle or flattened PDF alone may not remove hidden text or metadata; verify the redaction.
- Hotel nights, guest names and dates should be consistent with the separately verified flight itinerary.
In This Guide
- What Goes Wrong When a Door Code Travels With Your Booking Proof?
- How Do a Booking-Time Confirmation and a Code-Bearing Record Differ?
- Which Reservation Fields Stay Visible and Which Must Be Covered?
- What Does a Redacted Self-Check-In Confirmation Look Like in Practice?
- How Do You Cover a Code Without Making the File Look Edited?
- What Is the Safe Next Verification Step Before You Send Anything?
- Share the Booking and Keep the Key
Official-source check: Airbnb’s check-in guide explains ordinary access instructions; its connected-lock guidance explains active and backup codes. Adobe’s redaction guide explains removal of visible and hidden PDF data. Review the actual platform and recipient instructions for your booking.
Reviewed for: separation of accommodation proof from entry credentials, platform-specific timing, secure redaction and truthful matching with flight evidence.
A self-check-in confirmation may combine the reservation facts a reviewer needs with an entry code that should stay private. Share the issuer’s code-free booking confirmation when possible. If a later file contains the code, remove only that secret with a proper redaction tool while leaving the genuine property, guest, reference, status and dates readable.
Covering a code protects the people inside the stay. It does not make a record verifiable, and no hotel document guarantees visa approval. This guide shows which fields to hide, which to leave alone, and how to check the result with the property before it reaches anyone else.
When the route also needs flight evidence, you can add a dummy ticket separately.
What Goes Wrong When a Door Code Travels With Your Booking Proof?

A self-check-in confirmation does two jobs on one page. For a reviewer, it is accommodation proof: property, dates, guest, and status. For the property, it is a key. Nothing on the page separates the two, so whoever receives the page receives both.
Airbnb says self-check-in details, including a door or lockbox code, can appear in the Trips page and are normally messaged and emailed 48 hours before arrival. For a connected smart lock, a code can be sent after booking but activates at check-in. Check the actual document before sharing; timing varies by setup.
Why One Shared Copy Becomes Many
Picture an applicant who needs a hotel booking for visa purposes and sends one copy to a travel agent, one to a relative, and one to a visa center upload page. Three recipients now hold a working entry code, and each can forward it.
Airbnb says invited guests can access check-in and checkout instructions. Count everyone who can view the reservation details before forwarding a page that contains an access code.
An entry code is a physical-access secret, whether the accommodation is a private home, shared apartment or hotel room. Sending it to unnecessary recipients creates avoidable security risk; the presence or absence of a front desk varies by property.
The same page may also show personal data. Minimize what you share for the recipient’s purpose, preserve the fields needed to identify the booking, and use the application channel specified by the receiving authority.
The Two Opposite Mistakes
The first mistake is sharing everything, code included. The second is over-correcting: blanking the reference or the hotel name until nobody can find the reservation, or editing the file until it no longer matches what the issuer holds.
A fabricated or materially altered confirmation can undermine an application. Redacting a genuine access secret is different from changing a booking fact, but a recipient may have its own document rules. Prefer a fresh code-free confirmation from the issuer and retain the original privately.
Which Kinds of Stay This Covers
A temporary hotel booking should be described as the actual reservation the property or platform holds. If your visa file also contains a dummy flight reservation, match the accommodation dates to the real itinerary; neither document should imply a paid or guaranteed stay when the status says otherwise.
What a particular mission asks for sits outside this guide, so use the visa office's own instructions for that. The task here is narrower: sharing proof of accommodation without sharing the key.
How Do a Booking-Time Confirmation and a Code-Bearing Record Differ?
One reservation produces two documents at different moments, and they carry very different risk. Compare them before deciding which one to share.
State One: The Confirmation Issued at Booking
For ordinary self-check-in, Airbnb says detailed instructions and codes are shared around 48 hours before arrival. A booking-time confirmation may therefore be the cleaner file. Always inspect it: connected smart-lock codes may be shared after the booking is confirmed.
For eligible Airbnb connected smart locks, a unique code can be sent after booking and activated at check-in. Airbnb describes a default expiry 30 minutes after checkout that the host can adjust to 15 minutes–2 hours. The integration is generally for US and Canadian listings, with a possible property-management-system exception elsewhere.
State Two: The Record That Carries the Code
Detailed instructions typically include the exact address and directions, how to get in through codes, keys, or meeting details, parking, the Wi-Fi password, house rules, and the host's contact information. That is a handover note, not proof of a stay, and it is the version most likely to be screenshotted on arrival day.
Messages about early check-in sit in the same thread as those instructions. A thread screenshot can therefore expose the code even when the confirmation itself is clean.
Side by Side
Booking-time confirmation | Code-bearing record | |
|---|---|---|
Typical contents | Status, property, dates, guests, reference | Address and directions, entry method, Wi-Fi password, house rules, host contact |
Code exposure | None, unless a connected smart lock issued a code at booking | Live code, plus a possible backup code |
Timing on Airbnb | Often absent; inspect the actual file, especially with connected smart locks | May include a live or future-active code and sometimes a backup code |
Booking status and payment status | Usually shown | Usually near arrival; connected smart-lock codes may be sent after booking |
Value as shared proof | High | Low, and only after covering |
For a file prepared weeks ahead, the booking-time confirmation is usually the better document and the cleaner piece of accommodation evidence, and it needs no covering at all. Choose the code-bearing record only when it is the sole place a needed field appears, and cover it first.
Why a Code Can Outlive Its Stay
Airbnb documents pending or offline lock states and backup codes. A backup code can remain active until removed or the lock reconnects, so do not assume every code is harmless merely because the stay ended. Ask the host or platform to resolve a code you think has been exposed.
After check-in, the guest's code stays valid for the whole stay even if the host adds another way in.
A reused static code could let previous recipients retain access. Prefer property-managed unique codes, and ask the host how the particular lock handles changes and expiry. Do not assume all providers or locks behave like Airbnb’s connected integration.
A connected lock may log use or device status according to its product and platform terms. That data question is separate from the document-sharing problem here: a recipient of your visa proof should not receive a working door code.
Which Reservation Fields Stay Visible and Which Must Be Covered?
The task is subtraction without damage. Every field below either helps someone verify the stay or opens a door, and a few do both. The table sorts them, and the Basis column names the platform page behind each row or says plainly when the call is our judgment.
Field | Action | Reason | Basis |
|---|---|---|---|
Door, keypad, or lockbox code | Cover fully | It opens the property for anyone who holds the page | Airbnb Help Center, how to check in |
Backup door code | Cover fully | Backup codes stay active until removed, or the lock reconnects | Airbnb Help Center, managing smart lock codes |
Wi-Fi password and detailed arrival directions | Cover | They sit in the same instructions block as the code | Airbnb Help Center, how to check in |
Host's private phone or email | Keep if needed; cover a private personal contact that the reviewer does not need | Platforms route contact through anonymous aliases | Booking.com Partner Hub, contacting guests |
Property name and property address | Keep | They sit beside the code in the trip guide, so crop around the code only | Airbnb Help Center, sharing smart lock codes |
Guest names and number of guests | Keep | A reviewer may need the lead guest’s name and occupancy details to compare the accommodation with the application. Whether additional ID is required at check-in depends on the property and local rules. | Airbnb Help Center, how to check in |
Check-in and checkout dates and times | Keep | They appear next to the code and drive its active window | Airbnb Help Center, sharing smart lock codes |
Reservation reference | Keep | Verification starts from it | Editorial judgment |
Status, price, and cancellation terms | Keep | They show whether the stay is live and what it costs | Editorial judgment |
Passport details | Cover if present | The name must match the passport; the number is not needed | Editorial judgment |
What Must Stay Readable
Reviewers compare a small set of fields, and each must survive your edit. The hotel confirmation must show the property name and location, so leave the hotel address and property details intact, along with the destination city. A booking reference number is essential for verification. Some records call it a confirmation number, so keep whichever label the issuer prints.
Keep the guest names and occupancy information exactly as issued if they are relevant to the application. Do not shorten or rewrite names just to make the copy look tidy; check the receiving authority’s actual accommodation-proof instructions.
Reservations should cover all nights of the intended stay, and hotel dates must align with flight arrival and departure dates. Keep the check-in date, the check-out date, and the hotel checkout time readable. A mismatch between hotel and flight dates can raise suspicion, and an unexplained accommodation gap invites questions that a covered code never will.
If the first hotel night does not match your arrival, check time zones and overnight travel before editing anything. The separate arrival-date guide explains this; a flight reservation and accommodation booking should tell one coherent, truthful trip story.
What Must Not Appear at All
Passport numbers and document scans should not be forwarded casually with accommodation proof. If a receiving authority explicitly requires them, follow that requirement through its official channel. Treat any QR code, app invitation or link that grants property access as a secret.
Keep payment, cancellation and status details visible when they help identify the true reservation. Do not hide a real cancellation cutoff or imply payment has been made when the booking says pay at property.
Contact Lines
Keep the platform or property contact route needed to verify the booking. Consider covering a host’s private mobile number if it is not required. Booking.com may use anonymous email aliases, but an alias is not a universal security guarantee; check the actual confirmation and recipient needs.
What Does a Redacted Self-Check-In Confirmation Look Like in Practice?

The record below is clearly fictional. The property, address, traveler, and reference do not exist, and no real code appears anywhere in this guide, as these are just for your understanding.
Emily Carter lives in Delhi and plans an international trip to Lisbon in March 2027. She holds a keypad apartment booked on a platform with free cancellation. Her visa appointment is two weeks away, so she saves the confirmation now. The property messaged its arrival instructions soon after she booked, so her saved copy already carries them.
Field | As received (fictional) | As shared |
|---|---|---|
Property | Example Harbour Apartments, 14 Rua Exemplo, Lisbon | Unchanged |
Guest | Emily Carter, 2 guests | Unchanged |
Dates | Check-in 14 March 2027 from 15:00; check-out 19 March 2027 by 11:00 | Unchanged |
Reference | SAMPLE-0000 | Unchanged |
Status | Confirmed; pay at property; cancellable until 11 March 2027 | Unchanged |
Room | Studio, one double bed | Unchanged |
Entry code | A four-digit keypad code is printed here | Solid block labelled "access code covered" |
Wi-Fi password | Printed here | Solid block |
Host phone | A personal mobile number is printed here | Solid block; platform message thread kept |
What Changed and What Did Not
Three of nine fields are redacted in this fictional illustration: the entry code, Wi-Fi password and private mobile number. A note says “Access code redacted by guest; original retained.” The six booking fields remain as issued, so the property can still match the reservation.
Emily's booking is a genuine temporary reservation in the plain sense that she can cancel free of charge until 11 March 2027. She invented nothing and altered no fact. She covered only what opens the door.
How the Record Lines Up With the Rest of the File
Her overnight journey from Delhi lands in Lisbon on the morning of 14 March, so the hotel night matches the landing date. Her cover letter says five nights. Her visa form lists arrival on 14 March and departure on 19 March, and her insurance dates run across the same window.
The record agrees with all three, so the only visible difference from the issued page is the covered code. If her proposed trip later added Porto, the second city would need its own record. A multi-city trip is a different task from this one.
A cleaner-looking page built from scratch would have been tempting. It would also have been a page the property never issued, with fields only Emily believed were right. A solid block over three fields is easy to explain. A rebuilt confirmation is not.
How Do You Cover a Code Without Making the File Look Edited?
Work down this list and stop at the first option that fits your booking. The earlier options leave you less to defend.
Use the Booking-Time Copy
Where the platform has not yet released arrival instructions, a genuine booking-time confirmation may contain no entry code. Save and review that original file; do not assume every platform or smart-lock integration follows the same release timing.
Ask the Issuer for a Copy Without Arrival Instructions
Ask the issuer or property, through the established platform channel, for a code-free booking confirmation if available. That is preferable to modifying the issued document. Delivery channels and property policies vary, so do not assume the request must be fulfilled.
Avoid forwarding an entry code by any channel unless the recipient needs it for access. For accommodation proof, send the code-free confirmation through the receiving authority’s required channel; use the platform’s messaging route to ask the property for corrections.
Cover and Flatten It Yourself
Use a genuine PDF redaction tool that removes underlying text, image content and hidden data. A dark rectangle placed over selectable text is not a secure redaction. Keep an unchanged original privately.
Apply the redaction and sanitize the output, then reopen the saved file. Try selecting, copying and searching the former code; inspect embedded links, QR images, layers and metadata. Merely flattening a PDF is not a substitute for verifying that the secret was removed.
Add a short plain label under the block, such as "Access code covered by guest."
Keep the original private and unchanged, and never send it.
Touch nothing else on the page.
A temporary booking should come from a real issuer or property. If a factual field is wrong, ask that issuer to correct and reissue it. Redact access credentials only when needed; do not rebuild the reservation from guessed fields.
If the Code Has Already Gone Out
If a code appears compromised, immediate change requests should be made. On Airbnb, a guest's code cannot be customized, and a manual change in the lock app reverts when it syncs.
For a safety or security issue, the host contacts Airbnb Community Support to remove or change a code during a stay. On other platforms, message the property at once and ask for a new code.
If you suspect unauthorized access or a compromised code, notify the property or platform promptly and follow its safety instructions. This article does not diagnose lock hardware or network security from the booking document.
What Is the Safe Next Verification Step Before You Send Anything?
Verify from the source before you share. A copy that looks right can still be stale, cancelled, or mismatched with the live record.
Check the Live Booking First
Open the booking in the account that made it and compare the shared copy with your planned accommodation as the issuer holds it, line by line: names, dates, reference, and status.
Confirm the reservation’s current status before sharing. A previously saved confirmation can become stale after a cancellation or change; the PDF does not update itself.
There is no universal validity period for temporary hotel bookings. The relevant dates, cancellation deadline and active status depend on the actual reservation. Check these in the issuer’s live record before submission and again if the application is delayed.
Ask the Property One Specific Question
Some reviewing authorities may check accommodation evidence, but their verification methods vary. Ask the property whether it can retrieve the booking using the lead guest name, reference and dates; a door code should not be needed for that check.
A dummy booking should match the travel itinerary exactly, and a dummy hotel booking must match the travel itinerary for credibility. Check the hotel dates against your flight itinerary once more before sending, and leave route planning to its own guide.
What Acceptance Does and Does Not Mean
Do not rely on a blanket claim about embassy acceptance. Use the current official checklist for your visa type and application location, and make sure the accommodation evidence is genuine, current and consistent with the wider file.
A Schengen visa office, for example, decides against its own list. Covering a code neither helps nor hurts that decision.
A cancellable rate limits financial risk only until its cutoff. Write that date beside your recheck reminder, because a booking cancelled in error is the fastest way to lose an active reservation.
A Short Pre-Send Routine
Open the live booking and confirm the reservation is active.
Compare names, dates, reference, and status with the copy you plan to send.
Confirm the copy shows no code, link, QR image, or password.
Try to select the covered text, and fix the file if you can.
Send it only through the channel the recipient requires, never a public group, and keep the original private.
Set a reminder to recheck the booking if processing runs long.
Share the Booking and Keep the Key
For Emily’s fictional Lisbon stay, the safest shared proof is the original code-free confirmation or a properly redacted copy. Keep names, property, status, reference and dates as issued. Align the five hotel nights with the separate flight itinerary and application dates.
Your next step is the live booking: open it, compare it with the copy, and ask the property whether it can find the reservation from the name, reference, and dates. When the file also needs flight proof, a dummy ticket is available as a separate record.
Keep the trip file consistent. Verify the hotel booking from its issuer, protect entry details, and align the dates with your actual flight reservation.
Review flight reservation optionsFrequently Asked Questions
Is a Screenshot of the Airbnb Trips Page Safe to Share?
Not as it stands. That page shows the code beside the address and times. Crop to the property, dates, and reference, or share the booking-time confirmation instead.
Is a Blacked-Out PDF Safe to Send?
Only if the sensitive content has actually been removed. Use a proper redaction tool, sanitize the saved PDF and test the result; a visible black bar or flattening alone may leave recoverable data.
Does the Check-In Time Need Covering?
No. Check-in and checkout times help match the stay to your dates, and they are not secret. The code is the secret.
What if the Host Already Messaged the Code in the Thread?
Do not screenshot the thread. Share the confirmation instead, and if the code reached people outside your party, ask the property to reset it.
Will a Covered Code Make the Booking Look Fake?
A plain label and untouched details read as careful. A changed date or name is what looks forged, so leave those alone.
Does a Property Have to Reissue the Confirmation Without a Code?
Terms and practice differ by property and platform. Ask for a code-free confirmation first; if you must redact your own copy, remove the secret securely, label the redaction and keep the issued original privately.
Friendly reminder: Accommodation, visa and platform rules vary. Redacting a code does not establish reservation authenticity or guarantee visa approval. Use the receiving authority’s current instructions and keep the original booking privately.