Paze Not Showing at Checkout? Match Your Emails. Then Run the $25 StubHub Stack

Paze only appears at checkout when your merchant email matches the email your bank has, per Paze's own FAQ. The fix takes a minute, and it unlocks a three-layer StubHub stack: the Sapphire Reserve's $150 credit, Rakuten at 10 percent, and Paze's $10 checkout credit.

The short version: if Paze is not appearing as a payment option at a merchant that supports it, the usual cause is an email mismatch. Paze identifies you by the email on file with your bank, so the email on your merchant account has to be the same one your bank has. Fix that and the option appears. It matters right now because Paze is running a spend-$10-get-$10 offer through September 10, StubHub is on Paze's merchant list, and stacked with the Sapphire Reserve's $150 StubHub credit plus Rakuten's 10 percent, a $150 ticket finishes about $25 in your favor. Everything below was read from Paze, Chase, and Rakuten pages on August 17, 2026.

The fix, first

Paze does not work like a wallet you log into at checkout. The merchant decides whether to show you the Paze button, and it decides by recognizing your email.

Paze's own FAQ, word for word: "Paze uses the same email address and mobile number associated with your participating bank or credit union account. Be sure to enter this email or phone number if prompted at a participating merchant's checkout."

So the checklist when the button is missing:

Check which email your bank account uses. For a Chase card, that is the email on your Chase profile.
Check which email your merchant account uses. On StubHub, that is your StubHub login email.
Make them match. Either update the merchant account email or update the bank one, then try checkout again.

We hit this ourselves before the button appeared. Same card, same merchant, no Paze, until the emails lined up.

Why this is worth fixing this month

Paze is running its first big promotion: spend $10 or more in a single transaction at a participating merchant using Paze checkout, and you receive a $10 statement credit. Their offer page says you can earn it up to ten times, for up to $100 back per card, between June 15 and September 10, 2026, with no enrollment needed.

And StubHub is listed in Paze's own merchant directory, which sets up the stack. Here is our own Paze wallet showing both, the offer banner and the merchant, on the same screen:

Screenshot from our own Paze wallet, August 17, 2026.

The StubHub triple stack

If you hold the Chase Sapphire Reserve, three layers land on one ticket purchase:

Layer	What it pays	The condition
Sapphire Reserve StubHub credit	$150 for the second half of 2026	Enroll first; covers StubHub or viagogo
Rakuten portal	10 percent back today, against a usual 2	Click through Rakuten before buying
Paze checkout offer	$10 statement credit	Spend $10 or more via Paze by September 10

Run it on a $150 ticket: the Chase credit covers the ticket, Rakuten returns $15 on the price you paid, and Paze adds $10. You attended the event and finished roughly $25 ahead. The email fix above is what makes the third layer show up at all.

The order of operations

Enroll the StubHub credit on your Sapphire Reserve if you have not.
Make your StubHub email match your Chase email.
Click through Rakuten to StubHub.
Pick the ticket, and choose Paze at checkout, paying with the Sapphire Reserve.
The Chase credit and the Paze credit post as statement credits; Rakuten pays on its usual schedule.

Worth knowing

Rakuten's 10 percent is today's elevated rate. It sat at 2 percent before this, and portal rates move without notice.
The Paze offer is per card in your Paze wallet, per their FAQ, so a second eligible card has its own $100 ceiling.
Statement credits do not reduce what the portal sees. Rakuten pays on the checkout price.
Every layer has an owner: the credit is Chase's, the portal rate is Rakuten's, the checkout credit is Paze's. Each one's own page governs.

Every figure above was read from paze.com, creditcards.chase.com, and rakuten.com on August 17, 2026, and the credit amount matches our tracked card data. Treat that date as the as-of.

Verified against: