Begin with the file you already have, because the OurBus confirmation usually answers more than a generic search consequence. The OurBus question in this guide is summarized this way: OurBus allows cancellation more than 60 minutes before departure, with original-payment refunds generally available earlier than 24 hours and wallet credit closer to departure. Build a ticket timeline from the official OurBus pages reviewed on 2026-09-13; if the live OurBus transaction terms differ later, those transaction terms should be checked before acting.
The first entry in the ticket timeline is not “refund yes or no.” It is the stated OurBus product plus the OurBus date that controls the submission. One live OurBus condition says: OurBus says tickets can be canceled more than 60 minutes before scheduled departure. Put your real date beside that OurBus condition, then open the original OurBus confirmation or your OurBus account and check the departure time. This makes the timing decision presented instead of assumed.
A completed OurBus cancellation and a completed financial resolution are separate milestones. The ticket consequence could be an original-payment refund, retained access, a voucher, an account credit, a final OurBus invoice adjustment, or no returned value depending on the published OurBus terms. hold the ticket archive until the OurBus account and the expected financial consequence agree.
| Decision point | What to recheck |
|---|---|
| Service or booking | bus ticket |
| Search intent | OurBus cancel ticket for credit |
| First action | Open the original OurBus confirmation or your OurBus account and check the departure time. |
| Controlling checkpoint | OurBus says tickets can be canceled more than 60 minutes before scheduled departure. |
| Evidence file | ticket archive |
live OurBus policy map
Rate, plan or channel
OurBus checkpoint: OurBus says tickets can be canceled more than 60 minutes before scheduled departure. To test that OurBus condition, write the applicable date, plan, fare, ticket, service address or billing channel into your ticket timeline. Then open the original OurBus confirmation or your OurBus account and check the departure time. A OurBus condition becomes relevant only when it is connected to the stated transaction that will be changed.
Next, archive the OurBus screen or message that shows this checkpoint in your ticket archive. If the presented OurBus consequence is different from what the OurBus condition appears to predict, do not submit a second change just to experiment. Instead, use the Cancel Ticket control before the 60-minute cutoff. Ask OurBus help team to identify the rate, plan or transaction term that produced the presented ticket consequence.
What follows the submission
OurBus checkpoint: For a OurBus customer cancellation more than 24 hours before departure, the ticket price can be refunded to the original payment source for eligible direct card bookings. To measure that OurBus condition, write the applicable date, plan, fare, ticket, service address or billing channel into your ticket timeline. Then determine whether the cancellation is more than 24 hours out or inside the 24-hour window. A OurBus condition becomes relevant only when it is connected to the stated transaction that will be changed.
Next, hold the OurBus screen or message that shows this checkpoint in your ticket archive. If the presented OurBus consequence is different from what the OurBus condition appears to predict, do not submit a second change just to experiment. Instead, review whether the consequence is original-payment refund or OurBus Wallet credit. Ask OurBus help team to identify the rate, plan or transaction term that produced the presented ticket consequence.
Timing and eligibility
OurBus checkpoint: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. To check that OurBus condition, write the applicable date, plan, fare, ticket, service address or billing channel into your ticket timeline. Then use the Cancel Ticket control before the 60-minute cutoff. A OurBus condition becomes relevant only when it is connected to the stated transaction that will be changed.
Next, file the OurBus screen or message that shows this checkpoint in your ticket archive. If the presented OurBus consequence is different from what the OurBus condition appears to predict, do not submit a second change just to experiment. Instead, capture the cancellation email and wallet/refund file. Ask OurBus help team to identify the rate, plan or transaction term that produced the presented ticket consequence.
Value after cancellation
OurBus checkpoint: Booking and facility fees are described as nonrefundable, and tickets bought with wallet credit or certain third-party channels can return to wallet credit instead of the original source. To contrast that OurBus condition, write the applicable date, plan, fare, ticket, service address or billing channel into your ticket timeline. Then review whether the consequence is original-payment refund or OurBus Wallet credit. A OurBus condition becomes relevant only when it is connected to the stated transaction that will be changed.
Next, hold the OurBus screen or message that shows this checkpoint in your ticket archive. If the presented OurBus consequence is different from what the OurBus condition appears to predict, do not submit a second change just to experiment. Instead, if the ticket came through an OTA or a partner operator, read the booking-specific condition before assuming the direct OurBus outcome. Ask OurBus help team to identify the rate, plan or transaction term that produced the presented ticket consequence.
How to act now
Step 1: Capture the OurBus confirmation
Open the original OurBus confirmation or your OurBus account and check the departure time. In the ticket timeline, pair that action with this OurBus policy point: For a OurBus customer cancellation more than 24 hours before departure, the ticket price can be refunded to the original payment source for eligible direct card bookings. Before moving on, confirm that the OurBus page shows the correct customer, reservation, membership, ticket or service location. That single check prevents a correct procedure from being applied to the wrong OurBus transaction.
Archive one dated OurBus artifact for this step in the ticket archive. The relevant artifact is whichever item proves what actually happened: a confirmation email, status screen, cancellation number, carrier receipt, invoice, voucher entry, or final statement. To recheck the ticket consequence, later contrast that artifact with the live OurBus account. If they diverge, review whether the consequence is original-payment refund or OurBus Wallet credit.
Step 2: recheck the final state
Determine whether the cancellation is more than 24 hours out or inside the 24-hour window. In the ticket timeline, pair that action with this OurBus policy point: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. Before moving on, confirm that the OurBus page shows the correct customer, reservation, membership, ticket or service location. That single check prevents a correct procedure from being applied to the wrong OurBus transaction.
hold one dated OurBus artifact for this step in the ticket archive. The relevant artifact is whichever item proves what actually happened: a confirmation email, status screen, cancellation number, carrier receipt, invoice, voucher entry, or final statement. To resolve the ticket consequence, later contrast that artifact with the live OurBus account. If they diverge, capture the cancellation email and wallet/refund file.
Step 3: Identify the OurBus transaction
Use the Cancel Ticket control before the 60-minute cutoff. In the ticket timeline, pair that action with this OurBus policy point: Booking and facility fees are described as nonrefundable, and tickets bought with wallet credit or certain third-party channels can return to wallet credit instead of the original source. Before moving on, confirm that the OurBus page shows the correct customer, reservation, membership, ticket or service location. That single check prevents a correct procedure from being applied to the wrong OurBus transaction.
File one dated OurBus artifact for this step in the ticket archive. The relevant artifact is whichever item proves what actually happened: a confirmation email, status screen, cancellation number, carrier receipt, invoice, voucher entry, or final statement. To complete the ticket consequence, later contrast that artifact with the live OurBus account. If they diverge, if the ticket came through an OTA or a partner operator, read the booking-specific condition before assuming the direct OurBus outcome.
Step 4: Fix the controlling OurBus date
Review whether the consequence is original-payment refund or OurBus Wallet credit. In the ticket timeline, pair that action with this OurBus policy point: OurBus says tickets can be canceled more than 60 minutes before scheduled departure. Before moving on, confirm that the OurBus page shows the correct customer, reservation, membership, ticket or service location. That single check prevents a correct procedure from being applied to the wrong OurBus transaction.
Hold one dated OurBus artifact for this step in the ticket archive. The relevant artifact is whichever item proves what actually happened: a confirmation email, status screen, cancellation number, carrier receipt, invoice, voucher entry, or final statement. To establish the ticket consequence, later contrast that artifact with the live OurBus account. If they diverge, open the original OurBus confirmation or your OurBus account and check the departure time.
Step 5: Preview the consequence
capture the cancellation email and wallet/refund file. In the ticket timeline, pair that action with this OurBus policy point: For a OurBus customer cancellation more than 24 hours before departure, the ticket price can be refunded to the original payment source for eligible direct card bookings. Before moving on, confirm that the OurBus page shows the correct customer, reservation, membership, ticket or service location. That single check prevents a correct procedure from being applied to the wrong OurBus transaction.
Archive one dated OurBus artifact for this step in the ticket archive. The relevant artifact is whichever item proves what actually happened: a confirmation email, status screen, cancellation number, carrier receipt, invoice, voucher entry, or final statement. To recheck the ticket consequence, later contrast that artifact with the live OurBus account. If they diverge, determine whether the cancellation is more than 24 hours out or inside the 24-hour window.
Step 6: Submit the submission
If the ticket came through an OTA or a partner operator, read the booking-specific condition before assuming the direct OurBus outcome. In the ticket timeline, pair that action with this OurBus policy point: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. Before moving on, confirm that the OurBus page shows the correct customer, reservation, membership, ticket or service location. That single check prevents a correct procedure from being applied to the wrong OurBus transaction.
hold one dated OurBus artifact for this step in the ticket archive. The relevant artifact is whichever item proves what actually happened: a confirmation email, status screen, cancellation number, carrier receipt, invoice, voucher entry, or final statement. To resolve the ticket consequence, later contrast that artifact with the live OurBus account. If they diverge, use the Cancel Ticket control before the 60-minute cutoff.
Post-cancellation review
After the OurBus submission, reopen the ticket timeline and check this published point again: For a OurBus customer cancellation more than 24 hours before departure, the ticket price can be refunded to the original payment source for eligible direct card bookings. Now capture the cancellation email and wallet/refund file. Add the resulting date, amount or status to the ticket archive. This post-submission check is significant because the OurBus service can stop at one moment while the corresponding ticket consequence appears later.
For review item 1, contrast the newest OurBus account screen with the earlier OurBus confirmation. If the two records agree, mark that part of the ticket timeline complete. If they conflict, contact OurBus about the specific mismatch—date, amount, renewal state, equipment status, ticket value or settlement balance—rather than asking help team to restart the whole process.
After the OurBus submission, reopen the ticket timeline and check this published point again: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. Now if the ticket came through an OTA or a partner operator, read the booking-specific condition before assuming the direct OurBus outcome. Add the resulting date, amount or status to the ticket archive. This post-submission check is significant because the OurBus service can stop at one moment while the corresponding ticket consequence appears later.
For review item 2, contrast the newest OurBus account screen with the earlier OurBus confirmation. If the two records agree, mark that part of the ticket timeline complete. If they conflict, contact OurBus about the specific mismatch—date, amount, renewal state, equipment status, ticket value or settlement balance—rather than asking help team to restart the whole process.
After the OurBus submission, reopen the ticket timeline and check this published point again: Booking and facility fees are described as nonrefundable, and tickets bought with wallet credit or certain third-party channels can return to wallet credit instead of the original source. Now open the original OurBus confirmation or your OurBus account and check the departure time. Add the resulting date, amount or status to the ticket archive. This post-submission check is significant because the OurBus service can stop at one moment while the corresponding ticket consequence appears later.
For review item 3, contrast the newest OurBus account screen with the earlier OurBus confirmation. If the two records agree, mark that part of the ticket timeline complete. If they conflict, contact OurBus about the specific mismatch—date, amount, renewal state, equipment status, ticket value or settlement balance—rather than asking help team to restart the whole process.
The case is finished only when the OurBus account OurBus status and the financial consequence agree. For OurBus, a clean closeout means the ticket archive, the live OurBus account and the expected ticket consequence tell the same story. Until those three OurBus records align, hold the ticket timeline available for follow-up.
OurBus details that deserve a second look
Ticket validity, cancellation and rescheduling are separate concepts for OurBus. A ticket that cannot be refunded may still retain some travel utility under its own provisions. Relate that point to the ticket timeline by checking Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. Then place the corresponding OurBus evidence in the ticket archive. This keeps the advice tied to the provider’s published requirements instead of turning a general industry habit into an unsupported OurBus promise.
For OurBus, check whether a voucher is tied to the original passenger, route or expiration date before treating it like cash. Relate that point to the ticket timeline by checking Booking and facility fees are described as nonrefundable, and tickets bought with wallet credit or certain third-party channels can return to wallet credit instead of the original source. Then place the corresponding OurBus evidence in the ticket archive. This keeps the advice tied to the provider’s published requirements instead of turning a general industry habit into an unsupported OurBus promise.
If OurBus cancels a departure, document that event before changing the ticket yourself; an operator-caused problem can follow a different help team path. Relate that point to the ticket timeline by checking OurBus says tickets can be canceled more than 60 minutes before scheduled departure. Then place the corresponding OurBus evidence in the ticket archive. This keeps the advice tied to the provider’s published requirements instead of turning a general industry habit into an unsupported OurBus promise.
Decision cases
Customer is close to a deadline
A OurBus customer in this situation starts with two entries from the ticket timeline. First: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. Second: OurBus says tickets can be canceled more than 60 minutes before scheduled departure. The OurBus customer should place both statements next to the actual OurBus transaction dates, then if the ticket came through an OTA or a partner operator, read the booking-specific condition before assuming the direct OurBus outcome. That sequence gives OurBus help team a concrete reason for the requested ticket consequence.
If OurBus shows the expected OurBus outcome, put that OurBus screen in the ticket archive and note the verification OurBus date. If the OurBus outcome differs, leave the original OurBus confirmation untouched and ask which transaction-specific term changed the consequence. A duplicate cancellation, new booking, extra account edit or repeated payment action can obscure the ticket timeline and make the first submission harder to trace.
Cancellation is done but the OurBus outcome is pending
A OurBus customer in this situation starts with two entries from the ticket timeline. First: Booking and facility fees are described as nonrefundable, and tickets bought with wallet credit or certain third-party channels can return to wallet credit instead of the original source. Second: For a OurBus customer cancellation more than 24 hours before departure, the ticket price can be refunded to the original payment source for eligible direct card bookings. The OurBus customer should place both statements next to the actual OurBus transaction dates, then open the original OurBus confirmation or your OurBus account and check the departure time. That sequence gives OurBus help team a concrete reason for the requested ticket consequence.
If OurBus shows the expected OurBus outcome, put that OurBus screen in the ticket archive and note the verification OurBus date. If the OurBus outcome differs, leave the original OurBus confirmation untouched and ask which transaction-specific term changed the consequence. A duplicate cancellation, new booking, extra account edit or repeated payment action can obscure the ticket timeline and make the first submission harder to trace.
submission made before the key OurBus cutoff
A OurBus customer in this situation starts with two entries from the ticket timeline. First: OurBus says tickets can be canceled more than 60 minutes before scheduled departure. Second: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. The OurBus customer should place both statements next to the actual OurBus transaction dates, then determine whether the cancellation is more than 24 hours out or inside the 24-hour window. That sequence gives OurBus help team a concrete reason for the requested ticket consequence.
If OurBus shows the expected OurBus outcome, put that OurBus screen in the ticket archive and note the verification OurBus date. If the OurBus outcome differs, leave the original OurBus confirmation untouched and ask which transaction-specific term changed the consequence. A duplicate cancellation, new booking, extra account edit or repeated payment action can obscure the ticket timeline and make the first submission harder to trace.
Related RefundGuides resources
These RefundGuides pages cover nearby situations and terminology. Use them as process comparisons only; the official OurBus sources in this article control the OurBus policy details in the ticket timeline.
- Alaska Airlines Cancellation & Refund Guide: Saver Fares, Credits and Disrupted Flights
- Agoda Cancellation & Refund Guide: Booking requirements, Due Dates, No-Shows and Refund Timing
- Hopper Hotel Cancellation & Refund Guide: Fully Refundable, Partial and Nonrefundable Rates
Quick answers
Which OurBus date should I recheck first?
Use the event named in the live OurBus condition, not an approximate date. The key OurBus checkpoint for this guide is: OurBus says tickets can be canceled more than 60 minutes before scheduled departure. Write your own date in the ticket timeline, and then follow this action: Open the original OurBus confirmation or your OurBus account and check the departure time.
Does OurBus cancellation automatically mean a refund?
No. The OurBus cancellation status and the financial consequence are separate. Another relevant OurBus condition is: For a OurBus customer cancellation more than 24 hours before departure, the ticket price can be refunded to the original payment source for eligible direct card bookings. hold the ticket archive until the stated ticket consequence can actually be established.
What proof should I retain for OurBus?
Retain the OurBus transaction identifier plus the dated evidence that shows the change. For this OurBus case, one especially relevant action is: capture the cancellation email and wallet/refund file. Store that item with the ticket archive so the provider can match the submission to the right account or booking.
How do I handle an unexpected OurBus consequence?
Pause before repeating the change. contrast the live OurBus status with this OurBus condition: Inside 24 hours but still outside the 60-minute cutoff, the ticket price is generally moved to the OurBus Wallet rather than refunded to the original payment method. Then if the ticket came through an OTA or a partner operator, read the booking-specific condition before assuming the direct OurBus outcome. If the mismatch remains, ask OurBus to identify the stated term behind the presented ticket consequence.
Official sources reviewed
The following official OurBus pages were reviewed on 2026-09-13. Before submitting a new OurBus submission, reopen the live source and contrast it with the OurBus transaction terms stored in your ticket archive because fees, deadlines and account procedures can change.