The Change requests page lists proposed modifications to schedules and manifests. Use it to review what was requested, who requested it, and whether each request was approved, rejected, blocked, or is still pending.

The Change requests page lists proposed modifications to schedules and manifests. Use it to review what was requested, who requested it, and whether each request was approved, rejected, blocked, or is still pending.

A Special Service Request (SSR) allows operators to provide additional services to their passengers such as requests for accessible seating, requiring wheelchair storage, or declaring that a service animal accompany the passenger on board.

Click Save to save your changes. This method of payment will now show as enabled on the list of payment providers.

A Special Service Request (SSR) allows operators to provide additional services to their passengers such as requests for accessible seating, requiring wheelchair storage, or declaring that a service animal accompany the passenger on board.

Define non modifiable parameters when copying schedules. When this setting is enabled, you can select which schedule fields will be non-modifiable when copying an existing schedule. This helps maintain consistency and prevents accidental changes to critical schedule information.

Confirmation required for changes. If checked, modifications to schedules and manifests will require approval. Those proposals appear on the Change requests page under Operations > Change Requests.

Apply on change (per ticket)

If you have Special Service Requests fees, such as an extra large baggage fee, the are configured out on the Special Service Request page under the Admin tab.

Request endpoint: This endpoint will be used to send GET and POST requests for some actions that your application may want to do, like resetting a pwd (action='resetPwd'), self service changes (action='change'), using a gift certificate (action='useGiftCertificate'), redeeming a flexpass (action='redeemFlexpass'), logging a user using a jwtToken (action='logginUser'), etc.

Request endpoint: This endpoint will be used to send GET and POST requests for some actions that your application may want to do, like resetting a pwd (action='resetPwd'), self service changes (action='change'), using a gift certificate (action='useGiftCertificate'), redeeming a flexpass (action='redeemFlexpass'), logging a user using a jwtToken (action='logginUser'), etc.

Clicking the Associate button will associate the terminal to the computer and the button will change to a green label as below.

If you decide to do so, be aware that payment requests will be processed in the Getnet terminal in the same order as they are received.

It will prorated among all the payment types used in the ticket and in previous tickets in cases where the ticket was changed.

The rest of these settings cannot be modified from the app, they can only be changed from back office.

Note: When working in offline mode, normally the first download will consume much more data than the requests done at synchronization time.

Once a manifest is created, either by editing capacity, adding a comment, making a booking on it or adding a capacity exception, the manifest name will not be changed even you edit the name of the schedule.

On the Redeem process screen you will be asked to choose the date of intended travel. If the Flexpass is O & D specific, you will not be able to change the origin or destination.

If you had another route where the station is present enter and make the change in the Fare table.

• Usage Tracking: Promotion uses are tracked across sales, cancellations, and ticket changes, ensuring correct application and accounting.

For example, removing "paid_ins": {} prevents paid-in item documents from being added to the order PDF while leaving the other configured document types unchanged.

When moving a ticket, you can only transfer it to a different time, and it has to remain within the same Origin and Destination. Move is more of an admin function (IROPs), since there are less restrictions than with a regular change. Also, there are no fees associated with the Move function.

For AVS and online payment gateways: By also activating all the fields with the gear icon, you will be able to see the AVS code, the CVD code, and the CC response code. In this way, you can tell your customers the reason why their payment might have been rejected. This can also be useful to determine if the AVS whitelist configured for your account is correct or it should be changed to be less/more strict.

The product(s) associated with the trip. Required on Root classes. Only the One Of match type is supported, and one or more products may be selected. Only products using Journey Pricing or Market Pricing are supported. The selected products also limit which schedules can be assigned to the nesting. Child classes inherit the Root's products and cannot change them.

On every sign-in, the Betterez app may capture a browser fingerprint (when available) and send it with the login request. This fingerprint is stored in the user's login attempts (audit log) for security and support purposes. It does not change who can log in; it only adds an identifier to each login record. The optional Browser fingerprint checkbox on the trusted-machine page is separate: that option ties the trusted machine to a specific browser for non-trusted users, as described above.

Cancellable and Changeable If checked, tickets purchased with this method of payment will be Cancellable or changeable.

Cancellable and Changeable If checked, tickets purchased with this method of payment will be Cancellable or changeable.