SAS Cancellation & Refund Guide

Direct answer: SAS gives qualifying direct bookings to or from the United States a 24-hour money-back guarantee when the trip was booked more than seven days before departure. It applies regardless of ticket type, but later changes and close-in bookings follow different rules.

Before touching the SAS account or booking, identify the rule named “U.S. route condition.” SAS frames the money-back guarantee around travel to or from the United States. Next, check “More than seven days before departure,” because The standard guarantee requires the ticket to be purchased more than seven days before departure. That two-rule SAS check is more reliable than assuming every purchase follows the same cancellation path.

Table of Contents

SAS policy checkpoints that control the outcome

U.S. route condition

For SAS, confirm the booking file tied to “U.S. route condition.” SAS frames the money-back guarantee around travel to or from the United States. That SAS checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.

Use “More than seven days before departure” as the next SAS marker. The standard guarantee requires the ticket to be purchased more than seven days before departure. Compare the two SAS markers before acting; the matching SAS action here is “Confirm the itinerary is to or from the United States and was booked through SAS.” Save the resulting SAS confirmation so the later outcome can be checked against both rules.

More than seven days before departure

For SAS, map the confirmation set tied to “More than seven days before departure.” The standard guarantee requires the ticket to be purchased more than seven days before departure. That SAS checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.

Use “Direct SAS channels are specified” as the next SAS marker. The rule covers unused tickets booked through the SAS website, app, or Customer Service. Compare the two SAS markers before acting; the matching SAS action here is “Measure 24 hours from purchase and confirm the seven-day advance condition.” Save the resulting SAS confirmation so the later outcome can be checked against both rules.

Direct SAS channels are specified

For SAS, reconcile the purchase record tied to “Direct SAS channels are specified.” The rule covers unused tickets booked through the SAS website, app, or Customer Service. That SAS checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.

Use “Ticket type does not remove the guarantee” as the next SAS marker. Inside the qualifying conditions, SAS says the ticket is refundable within 24 hours regardless of ticket type. Compare the two SAS markers before acting; the matching SAS action here is “Use the confirmation-email link or My trips to cancel before the deadline.” Save the resulting SAS confirmation so the later outcome can be checked against both rules.

Ticket type does not remove the guarantee

For SAS, trace the service record tied to “Ticket type does not remove the guarantee.” Inside the qualifying conditions, SAS says the ticket is refundable within 24 hours regardless of ticket type. That SAS checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.

Use “Change costs can be treated separately” as the next SAS marker. If a ticket is changed and then canceled within 24 hours of original booking, SAS says the ticket price is refunded but not the change cost. Compare the two SAS markers before acting; the matching SAS action here is “If the booking was changed, separate the original ticket refund from any change cost.” Save the resulting SAS confirmation so the later outcome can be checked against both rules.

Change costs can be treated separately

For SAS, verify the transaction record tied to “Change costs can be treated separately.” If a ticket is changed and then canceled within 24 hours of original booking, SAS says the ticket price is refunded but not the change cost. That SAS checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.

Use “Card timing is normally three to five banking days” as the next SAS marker. For eligible cancelations, SAS says a charged card is credited and the transaction normally appears within three to five banking days. Compare the two SAS markers before acting; the matching SAS action here is “Keep the refund confirmation and monitor the original card for the published posting window.” Save the resulting SAS confirmation so the later outcome can be checked against both rules.

Card timing is normally three to five banking days

For SAS, match the timing record tied to “Card timing is normally three to five banking days.” For eligible cancelations, SAS says a charged card is credited and the transaction normally appears within three to five banking days. That SAS checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.

Use “U.S. route condition” as the next SAS marker. SAS frames the money-back guarantee around travel to or from the United States. Compare the two SAS markers before acting; the matching SAS action here is “Confirm the itinerary is to or from the United States and was booked through SAS.” Save the resulting SAS confirmation so the later outcome can be checked against both rules.

How to carry out a SAS cancellation or refund request

SAS action 1: Confirm the itinerary is to or from the United States and was booked through SAS

The SAS workflow now reaches “Confirm the itinerary is to or from the United States and was booked through SAS.” Record the issuing channel before completing it, because “U.S. route condition” controls this SAS branch.

Afterward, compare the SAS result with “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours.” The published money-back guarantee applies regardless of ticket type. A mismatch should be documented before another SAS request is sent.

SAS action 2: Measure 24 hours from purchase and confirm the seven-day advance condition

Use “Measure 24 hours from purchase and confirm the seven-day advance condition” as the next SAS action. Pair it with the SAS rule “More than seven days before departure,” especially the service status attached to that rule.

For the example “Passenger pays to change the ticket and then cancels inside 24 hours,” SAS says the ticket price can be refunded but the change cost is not included. That SAS example gives a concrete result to compare with the completed action.

SAS action 3: Use the confirmation-email link or My trips to cancel before the deadline

Before SAS action 3, write down the confirmation date. Then carry out “Use the confirmation-email link or My trips to cancel before the deadline” under this SAS checkpoint “Direct SAS channels are specified.”

Use “Booking was made five days before departure” as the post-action SAS test. The standard more-than-seven-days condition is not met; the customer should review the special close-in rule or fare conditions. Preserve the SAS evidence until the expected change is visible.

SAS action 4: If the booking was changed, separate the original ticket refund from any change cost

Action 4 for SAS is “If the booking was changed, separate the original ticket refund from any change cost.” Its supporting SAS rule is “Ticket type does not remove the guarantee,” and the key record is the deadline.

The SAS situation “Card was already charged” supplies the comparison point: SAS says the credit normally shows in three to five banking days after the qualifying cancellation. Check the completed SAS record against that result.

SAS action 5: Keep the refund confirmation and monitor the original card for the published posting window

At SAS, action 5 is “Keep the refund confirmation and monitor the original card for the published posting window.” The SAS checkpoint “Change costs can be treated separately” makes the billing owner worth recording.

Test that SAS action against “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours.” The published money-back guarantee applies regardless of ticket type. Keep the final SAS screen or email if the real result needs follow-up.

Real SAS situations that change the answer

SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours

Use “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours” as a SAS case study. The expected timing outcome is: The published money-back guarantee applies regardless of ticket type.

Now compare this SAS case with “Direct SAS channels are specified.” The rule covers unused tickets booked through the SAS website, app, or Customer Service. That comparison explains which SAS condition controls.

Passenger pays to change the ticket and then cancels inside 24 hours

In “Passenger pays to change the ticket and then cancels inside 24 hours,” SAS gives this result: SAS says the ticket price can be refunded but the change cost is not included.

The SAS rule “Ticket type does not remove the guarantee” adds the second test. Inside the qualifying conditions, SAS says the ticket is refundable within 24 hours regardless of ticket type. Save whichever SAS confirmation proves the real transaction followed it.

Booking was made five days before departure

For this SAS transaction described as “Booking was made five days before departure,” expect this post-cancel outcome: The standard more-than-seven-days condition is not met; the customer should review the special close-in rule or fare conditions.

Cross-reference the SAS point “Change costs can be treated separately.” If a ticket is changed and then canceled within 24 hours of original booking, SAS says the ticket price is refunded but not the change cost. Do not import a different provider’s rule into this SAS case.

Card was already charged

The example “Card was already charged” is useful for SAS because SAS says the credit normally shows in three to five banking days after the qualifying cancellation.

Verify it against “Card timing is normally three to five banking days” in this SAS policy. For eligible cancelations, SAS says a charged card is credited and the transaction normally appears within three to five banking days. The pair defines the SAS expectation more precisely than the word cancel alone.

SAS transaction checkpoints in one table

Before you act	How SAS treats it
U.S. route condition	SAS frames the money-back guarantee around travel to or from the United States.
More than seven days before departure	The standard guarantee requires the ticket to be purchased more than seven days before departure.
Direct SAS channels are specified	The rule covers unused tickets booked through the SAS website, app, or Customer Service.
Ticket type does not remove the guarantee	Inside the qualifying conditions, SAS says the ticket is refundable within 24 hours regardless of ticket type.

Verify the final SAS status

Use “U.S. route condition” as the first SAS closeout marker. SAS frames the money-back guarantee around travel to or from the United States.

Use “Card was already charged” as the real-case marker for SAS. SAS says the credit normally shows in three to five banking days after the qualifying cancellation.

Finish with this SAS checkpoint “Card timing is normally three to five banking days.” For eligible cancelations, SAS says a charged card is credited and the transaction normally appears within three to five banking days.

A complete SAS file keeps service status, money status, and transaction ownership visible as separate fields.

SAS transaction worksheet

SAS worksheet 1: U.S. route condition

Verify this SAS checkpoint “U.S. route condition” with this SAS case “Passenger pays to change the ticket and then cancels inside 24 hours.” The official SAS point is: SAS frames the money-back guarantee around travel to or from the United States.

For “Passenger pays to change the ticket and then cancels inside 24 hours,” SAS gives this practical result: SAS says the ticket price can be refunded but the change cost is not included. The related SAS action is “Use the confirmation-email link or My trips to cancel before the deadline.” Save this SAS confirmation that shows which result occurred.

SAS worksheet 2: More than seven days before departure

Map this SAS checkpoint “More than seven days before departure” with this SAS case “Booking was made five days before departure.” The official SAS point is: The standard guarantee requires the ticket to be purchased more than seven days before departure.

For “Booking was made five days before departure,” SAS gives this practical result: The standard more-than-seven-days condition is not met; the customer should review the special close-in rule or fare conditions. The related SAS action is “If the booking was changed, separate the original ticket refund from any change cost.” Save this SAS confirmation that shows which result occurred.

SAS worksheet 3: Direct SAS channels are specified

Pair this SAS checkpoint “Direct SAS channels are specified” with this SAS case “Card was already charged.” The official SAS point is: The rule covers unused tickets booked through the SAS website, app, or Customer Service.

For “Card was already charged,” SAS gives this practical result: SAS says the credit normally shows in three to five banking days after the qualifying cancellation. The related SAS action is “Keep the refund confirmation and monitor the original card for the published posting window.” Save this SAS confirmation that shows which result occurred.

SAS worksheet 4: Ticket type does not remove the guarantee

Match this SAS checkpoint “Ticket type does not remove the guarantee” with this SAS case “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours.” The official SAS point is: Inside the qualifying conditions, SAS says the ticket is refundable within 24 hours regardless of ticket type.

For “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours,” SAS gives this practical result: The published money-back guarantee applies regardless of ticket type. The related SAS action is “Confirm the itinerary is to or from the United States and was booked through SAS.” Save this SAS confirmation that shows which result occurred.

What to save for this SAS transaction

SAS original receipt, ticket, invoice, booking, or membership record
SAS policy checkpoint “U.S. route condition” with the date that makes it relevant
SAS billing or issuing channel tied to the transaction
SAS cancellation, downgrade, return, or booking-change confirmation
SAS effective end date or next controlling date
SAS refund, credit, fee, or equipment-return reference when the policy creates one

SAS cancellation and refund FAQ

How does “U.S. route condition” affect a SAS cancellation?

SAS publishes this rule: SAS frames the money-back guarantee around travel to or from the United States. For a concrete SAS example, “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours” means: The published money-back guarantee applies regardless of ticket type.

How does “More than seven days before departure” affect a SAS cancellation?

SAS publishes this rule: The standard guarantee requires the ticket to be purchased more than seven days before departure. The SAS scenario “Passenger pays to change the ticket and then cancels inside 24 hours” narrows the answer: SAS says the ticket price can be refunded but the change cost is not included.

How does “Direct SAS channels are specified” affect a SAS cancellation?

SAS publishes this rule: The rule covers unused tickets booked through the SAS website, app, or Customer Service. Use the SAS situation “Booking was made five days before departure” as the cross-check: The standard more-than-seven-days condition is not met; the customer should review the special close-in rule or fare conditions.

How does “Ticket type does not remove the guarantee” affect a SAS cancellation?

SAS publishes this rule: Inside the qualifying conditions, SAS says the ticket is refundable within 24 hours regardless of ticket type. In SAS practice, “Card was already charged” adds this result: SAS says the credit normally shows in three to five banking days after the qualifying cancellation.

How does “Change costs can be treated separately” affect a SAS cancellation?

SAS publishes this rule: If a ticket is changed and then canceled within 24 hours of original booking, SAS says the ticket price is refunded but not the change cost. The SAS case “SAS.com ticket to the U.S. bought 15 days before departure and canceled after eight hours” gives the practical check: The published money-back guarantee applies regardless of ticket type.

How does “Card timing is normally three to five banking days” affect a SAS cancellation?

SAS publishes this rule: For eligible cancelations, SAS says a charged card is credited and the transaction normally appears within three to five banking days. Compare that SAS rule with “Passenger pays to change the ticket and then cancels inside 24 hours,” where SAS says the ticket price can be refunded but the change cost is not included.

Which SAS records are worth keeping after the request?

Keep the original SAS transaction record, the effective change date, and the final SAS confirmation. Store any approved SAS refund, credit, fee, or return reference with the payment or booking record.

What changes when a third party controls this SAS transaction?

Use this SAS source that assigns responsibility to the app store, travel agent, property, club, or other biller. The correct SAS route is the one that reaches the party that actually issued the charge, booking, or ticket.

Official SAS sources checked on 2026-09-15

Official SAS documentation below was checked on 2026-09-15. Recheck the applicable SAS source before a later purchase or cancellation because the controlling terms can change.

📌 Also Check Out Air New Zealand Cancellation Guide: U.S. 24-Hour Cooling-Off Rule and Fare Refundability Return & Refund Guide →