MobilePay Card Readers

Elaine Twaddell

We use the MobilePay Card Readers with tablets at events. In the past I had a volunteer user name and password. Now with BBID I need to create a user. The problem is that the volunteers don't have emails associated with our organization. Since there are multiple volunteers I can't ask them for the personal email addresses. I can't use my email address for the sign on as I have full access rights to merchant services and wouldn't want to give those same permissions to a volunteer. Does anyone have any suggestions? Thank you for your help!

Austen Brown

@Elaine Twaddell - Can your IT Department create an admin email for you to use? Or does your org already have one that you could use for this? Think "info@nonprofit.org" or “donate@nonprofit.org”.

Faith Murray

@Elaine Twaddell
I second @Austen Brown in her suggestion to create a generic email. We use BBMS@ for ours and use it for all events.

One consideration I would point out is with the multi-factor authentication that Blackbaud is implementing. You must now have a cellphone or other token linked to your BBMS login credentials. For our last event, our temporary user was going out of state to a conference and needed login credentials when he borrowed our Mobilepay devices. I had to switch the cellphone info over to him for the duration of the visit, and then back again to mine when he returned. Also, the recovery code changes every time you change the account cellphone data, so you have to be careful storing that. If you can use a credential app and token instead, that might make your life easier.

Angela Tuttle

@Elaine Twaddell We contacted our IT Department like Austen Brown suggests and had them create generic email addresses for each group that will be using the mobile readers.

Angela Tuttle

@Faith Murray Good point! One of our groups uses 5 iPads. I gave them 5 card readers but they will need to think about the multi-factor authentication.

Elaine Twaddell

@Faith Murray
Good to know! Thank you so much for pointing out the multi-factor authentication change when the event is off site and I will not be present at it. I would not have thought about that. Thanks for your help.

Elaine Twaddell

@Angela Tuttle
Hi Angela, For your 5 ipads, did you have to have 5 separate email addresses or could you use the same one for all 5? How about the user names, 5 different ones or could you log into all 5 ipads at the same time using the same user name? And if using the same user name for all 5, did you figure out about the multi factor authentication? I'm just wondering if you had all 5 running at once if the same verification code could be used when you log on? Sorry for all the questions. I had contacted BB directly about this but I don't think we were on the same page on what I was asking. Thanks again.

Elaine Twaddell

@Faith Murray
Hi Faith, For your off-site devices, did you have to have separate email addresses or could you use the same one for all? How about the user names, different ones or could you log into all devices at the same time using the same user name? And if using the same user name for all, could you use the same verification code for all of them when logging on? Sorry for all the questions. I tried contacting BB directly about this but I don't think we were on the same page on what I was asking. Thanks again.

Faith Murray

@Elaine Twaddell
We were able to use one username/password for all of our devices. One of the things I have noticed in my personal BB account is that I can log on simultaneously in different browsers on the same computer, and on different browsers on different computers, and it really is no problem. I can even open multiple instances of database view as long as they open from different browsers (Firefox, Chrome, etc.). The only time RE gets upset is if I try to open more than one instance of RE in the same browser with different logins.

All this to say that one email/account should work for all devices simultaneously. However, when logging into each device, each one will send a text message with its own verification code.