Generate Member Cards to Apple Wallet / Android

Agreed. My customers are now asking what other solutions that are available that have this feature.

Hello

So I looked at this today and might give it a try. Since I am not familiar with the concept, it would help if you all could give me more information :

1. What data you want to be able to pass to the Card/Pass/Wallet ?

2. How a member card should look like ?

Regards,

Tuan

And in case subscribers subscribe for multiple plans, there would be multiple member cards generated?

I believe we would need to show expired date in the card. Then how users would get the updated date when they renew their subscription ?

Regards,

Tuan

Hi Tuan,
First of all thanks for looking at this. To answer your questions:
1) What should show on the card in the wallet?
Main bits of information

• Site Name (name of organisation/club etc) to which the membership pertains normally this would be the Site Name (in Joomla)
• Logo of the organisation/club
• Full name of member
• Organisation (Optional)
• Photo (optional)
• Membership Type
• Expiry Date
• QR Code for membership details so that it can be scanned and checked

2) Re Multiple membership types. This is an interesting one as we do not use them, but I am sure you have other customers who do? However, what we do have is a default membership type which people get when they sign up for and account. There is no expiry date on this default membership. This default membership is also assigned to the user when their membership expires. If the user renews or buys a new membership, then this is replaced with new membership type and expiry date. For us it should only show current membership with expiry date. Other users may want to see more than one if they have multiple memberships types for the same user?

3) Renewal process: When a membership expires and is renewed, we will need a facility to inform the member to download the new version of their membership to their wallet

4) Pricing: I know this might sound strange coming from a customer, but I think you should charge a separate licence/fee for this feature. Why do I say that? Having the ability to let our customers store their membership on their phones, will save us a lot of money printing physical cards and distributing them, which will more than cover the cost of the software. I would respectfully suggest charging something similar to the additional payment plugins, where there is a one-off charge for the software which can be used without an expiry date.
I have attached some cards I have in my wallet to give you an idea
Kind regards
David

Honestly, I would like to see community effort on this development because there are not many customers need it (I guess only few of you need it). What I have in mind is that :

- You, the people need it will sponsor me for this development
- I read documentation, write the code and then you help me with the testing and feedback

As I mentioned, I do not have experience on this concept. I also do not have an Iphone here for testing, so better we work together on this plugin

Regards,

Tuan

Hi Tuan,
Fully understand that you need sponsorship and help with testing, as this is a departure from your usual development. With  regard to sponsorship, can you give us some idea of the amount you are looking for?
I don't agree that only a few customers would need this feature, Certainly in Europe membership cards, whether they are membership or loyalty (shopping) cards, many are now available to store in the wallet on your phone. People don't want to be carrying around lots of plastic/paper cards in their wallets.  I also think the same applies to event tickets. Many ticket agencies, including Event tickets, travel tickets are being delivered on-line directly to people's wallets on their phones, this is the norm now, again I can only speak for Europe. So if you can develop the technology for Membership Pro, you could apply the same/similar technology to Event Booking Tickets.
Kind regards
David
 

Just a follow-up for anyone interested in this kind of feature. Even though Tuan may be able to develop the code, there are a number of things that we as users will have to do as well. The following only refers to Google Wallet, but I am sure Apple will have a similar set of thing we would have to do
For Membership, it seems that using a Google 'Generic' pass would meet Membership Pro needs. See the following links for further information, developers.google.com/wallet#get-started
developers.google.com/wallet/generic
To use Google Wallet on your site you would need to sign up for a Google Issuer account see developers.google.com/wallet/generic/get...ed/issuer-onboarding
and also if you do not have one, register for a Google Cloud account  console.cloud.google.com/
Kind regards
David


 

David Unwin wrote:

Hi Tuan,
First of all thanks for looking at this. To answer your questions:
1) What should show on the card in the wallet?
Main bits of information

• Site Name (name of organisation/club etc) to which the membership pertains normally this would be the Site Name (in Joomla)
• Logo of the organisation/club
• Full name of member
• Organisation (Optional)
• Photo (optional)
• Membership Type
• Expiry Date
• QR Code for membership details so that it can be scanned and checked

2) Re Multiple membership types. This is an interesting one as we do not use them, but I am sure you have other customers who do? However, what we do have is a default membership type which people get when they sign up for and account. There is no expiry date on this default membership. This default membership is also assigned to the user when their membership expires. If the user renews or buys a new membership, then this is replaced with new membership type and expiry date. For us it should only show current membership with expiry date. Other users may want to see more than one if they have multiple memberships types for the same user?

3) Renewal process: When a membership expires and is renewed, we will need a facility to inform the member to download the new version of their membership to their wallet

4) Pricing: I know this might sound strange coming from a customer, but I think you should charge a separate licence/fee for this feature. Why do I say that? Having the ability to let our customers store their membership on their phones, will save us a lot of money printing physical cards and distributing them, which will more than cover the cost of the software. I also found this article  www.cogniteq.com/react-native-app-development  useful for anyone looking to improve their business. I would respectfully suggest charging something similar to the additional payment plugins, where there is a one-off charge for the software which can be used without an expiry date.
I have attached some cards I have in my wallet to give you an idea
Kind regards
David

Thank you for sharing the details!

1. For the card, displaying essentials like the Site Name, Logo, Member's Full Name, Membership Type, Expiry Date, and a QR Code for verification sounds ideal. Including optional fields like Organization and Photo would add flexibility for different needs.
2. Multiple membership types could indeed be valuable for some users, and it makes sense to only show the current membership with an expiry date for simplicity, while allowing flexibility for others who may have overlapping memberships.
3. For renewals, an automated notification to download the updated card would streamline the process.
4. Regarding pricing, a separate license/fee does seem reasonable for this feature, given the cost savings on physical cards. An affordable one-time fee, similar to payment plugin charges, would make it an attractive addition.

I also have a customer that wanted this so will chat to them - What would it cost to help out ?

Also - does this help?  I was looking for a flowchart that outlines all the processes and steps..
passkit.com/blog/design-membership-cards/

So I decided to start with Apple Wallet. I read documentation, understood the concept and would like to give it a go. Unfortunately, when I reach this step developer.apple.com/documentation/wallet...Pass-Type-Identifier , it requires a Apple developer account which costs 99$/year which I do not have and do not want to apply for one.

Any of you have an existing developer account which could help ?

Regards,

Tuan