1 Sapphire Preferred perk now offsets its $95 annual fee


The Chase Sapphire Preferred® Card (see rates and fees) has long been one of the easiest travel rewards cards to recommend.

It earns valuable Chase Ultimate Rewards points, offers solid travel protections and carries a reasonable $95 annual fee — a rarity as more travel cards push well beyond the $100 mark.

Now, one of the card’s most useful perks has gotten significantly better.

As part of the Sapphire Preferred refresh, Chase doubled the card’s annual Chase Travel℠ hotel credit from $50 to $100 while keeping the annual fee at $95.

That may not sound revolutionary, but that one change dramatically improves the card’s value proposition.

The annual fee now easily pays for itself

Before this update, the Sapphire Preferred‘s annual fee was easy enough to justify, but it still required some effort.

Under the old setup, cardholders received a $50 annual hotel credit and paid a $95 annual fee. That left another $45 to make up through the card’s bonus categories, travel protections, redemption options or other perks.

That remaining $45 wasn’t particularly difficult to offset, especially for travelers who regularly redeem Chase Ultimate Rewards points. Still, you needed to use multiple card benefits to feel like you were truly coming out ahead.

pool and reclining chairs with palm trees and blue skies
CARLY HELFAND/THE POINTS GUY

Now, the math looks very different:

Reward your inbox with the TPG Daily newsletter

Join over 700,000 readers for breaking news, in-depth guides and exclusive deals from TPG’s experts

  • $95 annual fee
  • $100 annual Chase Travel hotel credit
  • $5 ahead

Of course, you still need to use the credit to get the value.

But one hotel booking per year can now effectively offset the card’s entire annual fee before you even consider the points you earn, the travel protections you receive or the flexibility of Chase Ultimate Rewards.

Everything else becomes icing on the cake.

Related: Best ways to redeem Chase Ultimate Rewards points for hotel stays

The refreshed Sapphire Preferred hotel credit now feels more useful

As a Sapphire Preferred cardholder, I appreciate the extra $50 in value. What stands out even more, though, is how much more useful the credit feels now.

When the benefit was worth $50, I always viewed it as a nice discount rather than a reason to book through Chase Travel. Saving $50 is great, but it wasn’t always enough to change my behavior.

Consider a one-night hotel stay that costs $129. Under the old setup, the $50 credit would bring your out-of-pocket cost down to about $79. That’s certainly better than paying full price, but it may not have been enough savings to make the credit feel especially valuable.

With the new $100 credit, that same stay would cost just $29.

IHG

While the old credit felt like a discount, the new one can cover a significant portion of a stay.

This can be especially useful for one-night stays, such as an airport hotel before an early-morning flight, a roadside motel during a road trip or a budget-friendly weekend getaway. In many cases, $100 could cover a substantial portion of the total cost.

Even better, Chase didn’t make the benefit any harder to use. There is no minimum stay requirement, no complicated enrollment process and no need to track multiple credits throughout the year. You simply book and prepay a hotel through Chase Travel and receive the credit.

As always, it’s worth comparing Chase Travel pricing against booking directly with the hotel before using the credit, since rates can sometimes differ.

Eligible hotel bookings made through Chase Travel also earn points. However, cardholders won’t earn points on the portion of the purchase covered by the up-to-$100 statement credit

That’s refreshingly simple compared to many card benefits today.

Who benefits most from the Sapphire Preferred card changes?

This update is especially useful if you like the idea of a travel rewards card but don’t want to spend a lot of time optimizing every benefit.

If you already transfer Chase Ultimate Rewards points to airline and hotel partners for maximum value, the Sapphire Preferred likely made sense for you before this change.

Budget travel
JULPO/GETTY IMAGES

But if you’re a more occasional traveler, the new $100 hotel credit is much easier to appreciate. You don’t need to learn transfer sweet spots, hunt for award availability or track a long list of credits to come out ahead.

You just need to book a hotel through Chase Travel once a year.

The Sapphire Preferred still costs less than $100 per year, and its biggest annual credit remains simple enough for many travelers to use without changing their habits.

Bottom line

The Sapphire Preferred® Card was already one of the best travel rewards cards available, even with its $95 annual fee.

Now, Chase has doubled the card’s annual hotel credit to $100 without raising the fee.

You still need to book a hotel through Chase Travel to use the benefit, but one stay per year can now effectively offset the cost of keeping the card. Everything else the card offers — the points, travel protections and redemption flexibility — comes on top of that.

The Sapphire Preferred has always been easy to recommend. This change makes that recommendation even easier.

Related: Who should (and shouldn’t) get the Chase Sapphire Preferred?



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


What are the controllers and their types?

Salesforce controllers, also known as Visualforce controllers, are used to execute a set of instructions. Controllers specify what happens when a user interacts with the Visualforce Markup components such as Visualforce tags, HTML, fields, etc. When a user clicks on a button or link on a Visualforce page, the associated controllers will display the data related to the user action or component. The controllers have the ability to modify component behavior. They work on an MVC(Model-View-Controller) approach. Salesforce provides the below types of controllers.

  • Standard controllers
  • Standard List Controllers 
  • Custom Controllers

Wish to make a career in the world of salesforce? Start with HKR’S  salesforce online training !

1.Standard controllers

The standard controllers are the default controllers provided by Salesforce. They contain the same logic and functionality that are used for standard Salesforce pages. Every Salesforce object contains a standard controller that can be queried using the Salesforce Lightning Platform API. When a user interacts with a component on the page, the controller interacts with the database, fetches the relevant data, and displays it on the page. To display the relevant data on the Visualforce page, we need a record ID. So, we need to send an ID as a query string parameter in the page URL. The standard controller has a getter method that returns the record related to the query ID. If a user doesn’t have access to a certain object (or component) on the page, which is associated with a standard controller, it will display an insufficient privileges error message to the user. 

Associating a standard controller with a Visualforce page

To associate a standard controller to a Visualforce page, we have to use the “standardController” attribute on the tag. We should specify the name of any Salesforce object, which can be queried using the Lightning Platform API. Here is the syntax to associate a standard controller to a standard object on a page,

Salesforce Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

2.Standard List Controllers

Standard list controllers are used for displaying or act on a set of records on the Visualforce pages. Related lists, list pages, and mass action pages are some of the examples of Salesforce pages that work with a set of records. The following are the objects that can be used with standard list controllers.

  • Account
  • Contract
  • Idea
  • Order
  • Product2
  • Solution
  • User
  • Lead
  • Opportunity
  • Asset
  • Campaign
  • Case
  • Contact
  • Custom objects

Associating a standard list controller with a Visualforce page

Associating a standard list controller is very much similar to associating a standard controller. In the standard list controller, we can set an object through the “standardController” attribute on the tag and then set the recordSetVar attribute on the same component. Here is the syntax to associate a standard list controller with an object on a page,

Once the standard list controller is associated, we can act on a set of records using expression language syntax. We can use a standard list controller to add pagination to a page with the help of the next and previous actions.

Cloud Technologies, salesforce-controllers-description-0, Cloud Technologies, salesforce-controllers-description-1

Subscribe to our YouTube channel to get new updates..!

3.Custom Controllers

Custom controllers are used to implementing custom logic and data manipulation for a Visualforce page. If we want to perform things like calling an external web service, validate and insert data, we can use a custom controller. The custom controllers override the existing functionality and implement customized navigation through an application. They execute entirely in system mode and users will have full control over the app’s logic. 

Create a Visualforce page that uses a custom controller

To add a custom controller to a Visualforce page, we have to set the “controller” attribute in the tag. When we use a custom controller, we cannot use a standard controller. Here is the syntax to associate a custom controller to a Visualforce page,

Controller Extensions

A controller extension overrides behavior in a standard or custom controller. Any Apex class with a constructor that takes a single argument of type “ApexPages” is referred to as a controller extension. We can implement the functionality of another controller to an apex tag while adding custom logic. Here is an example class for controller extension.


public class myControllerExtension {

//custom code

}

We can extend this controller extension on a Visualforce page like below.
Both the controller extension and custom controller use the action, getter, and setter methods. The custom controllers and controller extension classes ignore user permissions and field-level security as they execute in system mode. So, the custom controllers and controller extensions are mainly used to set organization-wide defaults. Based on the user profile, we can even define whether a user can execute methods in a custom controller or controller extension class. 

Salesforce Training

Weekday / Weekend Batches

Conclusion

Apex is a complete programming language that we can use to implement effective Visualforce pages. We can use Apex properties, which are a combination of a variable with getter and setter methods. We can implement anything on a Visualforce page with the help of controllers in Apex code. Using controllers, we can implement features like dropdown on a Visual page. They allow you to filter the records displayed on the page. While working with controllers, you should have an eye out for validation rules. You should be able to handle the validation rule exceptions. 

Related Articles:



Source link