Verified BursaPay workflow: Explains the separate hidden_location field intended for restricted venue details.
1. Overview & Purpose
Event has both location and hidden_location; hidden_location is documented in the model as information sent only to ticket purchasers for business events.
2. Requirements & Setup
Keep the hidden location accurate and avoid placing sensitive information in the public location field.
3. Step-by-Step Workflow
- Open the event configuration.
- Enter the public location normally.
- Use hidden_location only when a restricted venue detail is required.
- Confirm that downstream ticket communication uses the intended location field.
4. Rules & Troubleshooting
Do not assume every event type automatically hides its location; the field's handling depends on the downstream communication workflow.
5. Verification & Next Steps
Test a representative ticket communication before publishing the event.