Web validation of tickets and credentials

With bikubo you can use a desktop or laptop to validate tickets or credentials. You can attach a barcode and/or QR code reader gun, and after reading, the data is sent to the server or validated against the internal database of the pc, displaying the validation result, and making the relevant changes in the database, regarding the ticket/credential validated. You can also validate manually by entering the localizador.

To obtain the link to the web page for validations, you must click on Menu => Events => Active => Title of the event in question => List of ticket/credential categories => ticket/credential in question (option – Advanced configuration). The screen is displayed where you can access three links: the first link allows you to validate all events and all ticket and credential categories, the second link allows you to validate the event and all ticket and credential categories for that event, and finally, the third link allows you to validate only the event and the selected category.

Once you access that link and open it in a browser, the web page with the validation options is displayed.

You can validate against the server database, or download the tickets and validate against the browser's internal database once the tickets are downloaded.

Validation against the server means that the checks to be performed regarding QR/barcode readings and/or localizadores are looked up in the bikubo server databases, so that this database is unique for all validators. Thus, if 'validator A' validates a ticket, it is set as delivered, so if you try to access again with that ticket through the same validator or through 'validator B' (if also validating online), it will already appear as delivered and the app will show the error. With validation against the server, by having to access the bikubo server, it is necessary to have a good internet connection for the process to be carried out correctly.

Validation against internal database means that the checks to be performed regarding QR / barcode readings and/or localizadores are looked up in the downloaded databases of the browser, so that there are as many databases as validators. Thus, if 'validator A' validates a ticket, it is set as delivered, so if you try to access again with that ticket through the same validator it will appear as DELIVERED, but through 'validator B' it will not appear as delivered, giving it as correct. In this type of validation, by not having to access the bikubo server for validation, it is not necessary to have an internet connection for the process to be carried out correctly. However, prior to validation, it is required to download the tickets from a place with connection, so that they are in the internal database of the browser.

The validation data against internal database remains in the validator's browser, and is not recorded on the server, so the tickets/credentials are not recorded as validated on the server (and can be delivered successively), and the statistics will not appear either. However, the web validation page has the 'Send validations to server' function, so that by clicking that button, the data of the validated tickets and the validation time are uploaded, so that the server processes those validations, and makes the relevant changes in the status of the tickets, and in the statistics.

The third validation option consists of validating against server and internal database, simultaneously, so that the checks to be performed regarding QR/barcode readings and/or localizadores are looked up in the bikubo server databases, and also in the internal database of the browser. The advantages and possibilities of this option are described in the following link for validation with the bikubo app, which can be applied to web validation: simultaneous validation app.

It is recommended that the validator selects the event and ticket category option that interests them, since when validating a ticket, if the validation is valid, it directly delivers it and the next time the ticket/credential is validated it will be shown as previously delivered.

The validation result is displayed on the right side of the web browser screen, being green for the correct result, red for a validation error result, and blue if the result is correct but is showing the attendee's exit (in validations previously configured this way), and also the corresponding information is displayed (attendee name, ID, observations or cause of error). At the top of the right part of the browser, it is displayed whether the validation has been performed against the browser database or against the server.

Finally, we must indicate that if you are not going to validate with a QR code or barcode reader, you can select the option to manually enter the localizadores, enabling the checkbox.

You can change the web validation links simply by changing the app password in menu => my data.