Pernod Ricardfeaturedimage copy

Mobile Wallet Case Study: Pernod Ricard

Pernod Ricardfeaturedimage copy

Do you want to increase customer engagement? Wondering how to innovate, and offer a new experience to your customers? Have you thought about mobile wallet and mobile payments? If you answered yes to at lest one of those, you’ll appreciate this mobile wallet case study for Pernod Ricard. It’s goes down well with the article we posted yesterday: ‘5 Apple Pay Experiences That Will Enhance Your Night Out’.
Click on the respective links if you want to learn more about mobile wallet marketing, Apple Pay or Android Pay.

PassKit Cast Study for Pernod Ricard

Want to see more mobile wallet case studies? Check these out:
Mobile Wallet Case Study: Resorts World Manila
Mobile Wallet Case Study: Heathrow Airport
Mobile Wallet Case Study: Subway
Want to easily incorporate the Physical Web into your marketing strategy? Then check out Nearme.is. A new Physical Web initiative from Passkit. To learn more about Mobile Wallet Software.

Create. Distribute. Engage.

Apple and Google ready passes at scale, quick setup and real-time updates.

Trusted by:

Related Blog Posts

Not done yet? Keep reading for additional insights on Apple & Google Wallet passes across design, integrations, campaign ideas, and success metrics.

Mobile Wallet API Solutions For Custom Loyalty Program Development

Mobile Wallet API Solutions For Custom Loyalty Program Development

Mobile Wallet Loyalty APIs let you build custom loyalty programs inside Apple Wallet and Google Wallet. Customers can join without

mobile wallet analytics

Mobile Wallet Analytics: Customer Engagement Tracking & KPIs

Mobile wallet analytics measures how people interact with content and programs delivered through a mobile wallet. It supports customer engagement

How to Choose the Best Mobile Wallet Pass Platform

How to Choose the Best Mobile Wallet Pass Platform

Mobile wallet passes sit at the intersection of UX, infrastructure, and customer engagement. They’re simple for the end user, but