Led end-to-end UX and UI design for the Amazon Pay integration on TicketNetwork’s eCommerce platform. As the sole product designer on the project, I partnered directly with the Amazon Pay team, product manager, and engineers to deliver a brand-compliant checkout experience across desktop and mobile.
2024
Senior Product Designer
Responsive web • iOS • Android
Checkout is where excitement either turns into a purchase… or quietly dies. To make that moment faster, easier, and a little more trustworthy, we introduced Amazon Pay as an alternative payment option on TicketNetwork. The idea was simple: if users already trust Amazon with their money, why not let them bring that confidence with them? The fun part (and the challenge) was making it feel seamless—like Amazon belonged there all along, without actually turning our checkout into Amazon.com.
Increase checkout conversion and reduce payment friction by introducing Amazon Pay as an alternative wallet option—leveraging Amazon’s trusted brand to improve speed, confidence, and purchase completion rates.
Amazon does not play when it comes to brand and UI compliance, and for good reason. Every button, color, and interaction had to meet their standards exactly. This meant I had to design within (very real) guardrails. The challenge was designing within those constraints while still making the experience feel cohesive with TicketNetwork. I worked closely with the Amazon Pay team to ensure compliance, while making thoughtful adjustments so the integration didn’t feel like a foreign object dropped into our checkout.
A huge challenge for me was fitting a new payment flow into an already busy checkout. Our checkout flow was already doing a lot, so introducing a third-party payment option wasn’t as simple as “add button, call it a day.” I mapped out the full end-to-end flow, identifying where Amazon Pay should live, how it would behave, and how it would interact with existing steps. The goal was to reduce friction—not accidentally add more of it. There were a few “wait… what happens if the user does this?” moments, especially around authentication and returning users, which required close collaboration with Engineering and connects with the AmazonPay team to get right.
Now to balance two brands without losing users' trust. This was a bit of a design tightrope: Amazon needed to feel like Amazon (for trust), but the experience still needed to feel like TicketNetwork (for continuity). I had to I focused on creating a clear visual hierarchy—letting Amazon Pay stand out where it mattered, while keeping the overall checkout experience consistent and familiar. Behind the scenes, I also worked to ensure the patterns we created could scale—so this wouldn’t be a one-off integration, but a foundation for future payment options.
Adding Amazon Pay ended up doing exactly what we hoped—it made checkout feel faster, easier, and a lot more familiar for users who already trust Amazon with their information (which is… a lot of people). We saw smoother payment completion, fewer friction points during checkout, and an overall lift in user confidence at the most critical moment of the funnel. And the numbers backed it up—we saw approximately a 15%+ increase in revenue week over week after launching the integration, which is always a nice way to validate that all the details (and debates) were worth it. On our side, we now had a clean, scalable pattern for integrating alternative payment methods—so the next time we introduce a new wallet, we’re not starting from scratch (which engineering definitely appreciated). And personally, there’s something satisfying about taking a complex, constraint-heavy integration and making it feel simple… because users should never feel the chaos behind the scenes.
Led end-to-end UX and UI design for the Amazon Pay integration on TicketNetwork’s eCommerce platform. As the sole product designer on the project, I partnered directly with the Amazon Pay team, product manager, and engineers to deliver a brand-compliant checkout experience across desktop and mobile.
2024
Senior Product Designer
Responsive web • iOS • Android
Checkout is where excitement either turns into a purchase… or quietly dies. To make that moment faster, easier, and a little more trustworthy, we introduced Amazon Pay as an alternative payment option on TicketNetwork. The idea was simple: if users already trust Amazon with their money, why not let them bring that confidence with them? The fun part (and the challenge) was making it feel seamless—like Amazon belonged there all along, without actually turning our checkout into Amazon.com.
Increase checkout conversion and reduce payment friction by introducing Amazon Pay as an alternative wallet option—leveraging Amazon’s trusted brand to improve speed, confidence, and purchase completion rates.
Amazon does not play when it comes to brand and UI compliance, and for good reason. Every button, color, and interaction had to meet their standards exactly. This meant I had to design within (very real) guardrails. The challenge was designing within those constraints while still making the experience feel cohesive with TicketNetwork. I worked closely with the Amazon Pay team to ensure compliance, while making thoughtful adjustments so the integration didn’t feel like a foreign object dropped into our checkout.
A huge challenge for me was fitting a new payment flow into an already busy checkout. Our checkout flow was already doing a lot, so introducing a third-party payment option wasn’t as simple as “add button, call it a day.” I mapped out the full end-to-end flow, identifying where Amazon Pay should live, how it would behave, and how it would interact with existing steps. The goal was to reduce friction—not accidentally add more of it. There were a few “wait… what happens if the user does this?” moments, especially around authentication and returning users, which required close collaboration with Engineering and connects with the AmazonPay team to get right.
Now to balance two brands without losing users' trust. This was a bit of a design tightrope: Amazon needed to feel like Amazon (for trust), but the experience still needed to feel like TicketNetwork (for continuity). I had to I focused on creating a clear visual hierarchy—letting Amazon Pay stand out where it mattered, while keeping the overall checkout experience consistent and familiar. Behind the scenes, I also worked to ensure the patterns we created could scale—so this wouldn’t be a one-off integration, but a foundation for future payment options.
Adding Amazon Pay ended up doing exactly what we hoped—it made checkout feel faster, easier, and a lot more familiar for users who already trust Amazon with their information (which is… a lot of people). We saw smoother payment completion, fewer friction points during checkout, and an overall lift in user confidence at the most critical moment of the funnel. And the numbers backed it up—we saw approximately a 15%+ increase in revenue week over week after launching the integration, which is always a nice way to validate that all the details (and debates) were worth it. On our side, we now had a clean, scalable pattern for integrating alternative payment methods—so the next time we introduce a new wallet, we’re not starting from scratch (which engineering definitely appreciated). And personally, there’s something satisfying about taking a complex, constraint-heavy integration and making it feel simple… because users should never feel the chaos behind the scenes.
Led end-to-end UX and UI design for the Amazon Pay integration on TicketNetwork’s eCommerce platform. As the sole product designer on the project, I partnered directly with the Amazon Pay team, product manager, and engineers to deliver a brand-compliant checkout experience across desktop and mobile.
2024
Senior Product Designer
Responsive web • iOS • Android
Checkout is where excitement either turns into a purchase… or quietly dies. To make that moment faster, easier, and a little more trustworthy, we introduced Amazon Pay as an alternative payment option on TicketNetwork. The idea was simple: if users already trust Amazon with their money, why not let them bring that confidence with them? The fun part (and the challenge) was making it feel seamless—like Amazon belonged there all along, without actually turning our checkout into Amazon.com.
Increase checkout conversion and reduce payment friction by introducing Amazon Pay as an alternative wallet option—leveraging Amazon’s trusted brand to improve speed, confidence, and purchase completion rates.
Amazon does not play when it comes to brand and UI compliance, and for good reason. Every button, color, and interaction had to meet their standards exactly. This meant I had to design within (very real) guardrails. The challenge was designing within those constraints while still making the experience feel cohesive with TicketNetwork. I worked closely with the Amazon Pay team to ensure compliance, while making thoughtful adjustments so the integration didn’t feel like a foreign object dropped into our checkout.
A huge challenge for me was fitting a new payment flow into an already busy checkout. Our checkout flow was already doing a lot, so introducing a third-party payment option wasn’t as simple as “add button, call it a day.” I mapped out the full end-to-end flow, identifying where Amazon Pay should live, how it would behave, and how it would interact with existing steps. The goal was to reduce friction—not accidentally add more of it. There were a few “wait… what happens if the user does this?” moments, especially around authentication and returning users, which required close collaboration with Engineering and connects with the AmazonPay team to get right.
Now to balance two brands without losing users' trust. This was a bit of a design tightrope: Amazon needed to feel like Amazon (for trust), but the experience still needed to feel like TicketNetwork (for continuity). I had to I focused on creating a clear visual hierarchy—letting Amazon Pay stand out where it mattered, while keeping the overall checkout experience consistent and familiar. Behind the scenes, I also worked to ensure the patterns we created could scale—so this wouldn’t be a one-off integration, but a foundation for future payment options.
Adding Amazon Pay ended up doing exactly what we hoped—it made checkout feel faster, easier, and a lot more familiar for users who already trust Amazon with their information (which is… a lot of people). We saw smoother payment completion, fewer friction points during checkout, and an overall lift in user confidence at the most critical moment of the funnel. And the numbers backed it up—we saw approximately a 15%+ increase in revenue week over week after launching the integration, which is always a nice way to validate that all the details (and debates) were worth it. On our side, we now had a clean, scalable pattern for integrating alternative payment methods—so the next time we introduce a new wallet, we’re not starting from scratch (which engineering definitely appreciated). And personally, there’s something satisfying about taking a complex, constraint-heavy integration and making it feel simple… because users should never feel the chaos behind the scenes.