Guest booking with no OTP cannot upload manual payment receipt

[nanoharsha]

When Allow Guest Booking is enabled and the verification method is set to None, the guest can proceed with registration, but is unable to upload payment evidence/receipt for a manual payment method.

PR #137 states that a user is silently created so that the booking has a real owner. However, it appears that the browser session remains as Guest, and the file upload is therefore either blocked or cannot be associated with the guest’s booking/payment record.

Steps to reproduce

• Enable guest booking for an event.
• Set guest verification method to None.
• Add/select a manual payment method requiring payment evidence.
• Proceed without logging in.
• Attempt to upload a receipt.

Expected behaviour

The receipt should be uploaded securely and attached to the relevant pending booking/payment record.

Actual behaviour

The receipt cannot be uploaded/attached while continuing as a guest.

It may require either a guest-safe upload endpoint, temporary booking token, or creation of the booking before receipt upload.

Additional observation

In the same browser session, if the user logs in and then refreshes the payment page, the receipt upload works correctly. After submitting the payment evidence, the booking is created and shown with the status “Awaiting Payment Verification.”

This suggests that:

• The manual payment and receipt-upload workflow itself is functioning.
• The failure occurs only when the visitor continues as an unauthenticated guest with verification method set to None.
• The booking/user may be created internally, but the active browser session still appears to remain as Guest, preventing the file upload or association.
• Once the session becomes authenticated and the page is refreshed, Buzz can associate the uploaded file and proceed normally.

Expected behaviour

Guest booking with verification method None should either:

1. Allow secure receipt upload within the guest flow and attach it to the pending booking/payment record; or
2. Create the booking first and provide a secure token/link for uploading payment evidence without requiring a normal login.

Current workaround

The user must log in and refresh the page before uploading the receipt. This is not practical for participants using the guest-booking flow.