Use this link to share with your colleagues:
Stored Payment Methods (November 2013): https://help.pm.leapevent.tech/a/148648
This article is old! Wouldn't you rather read something... fresher?
There may be outdated information or suggestions in this article that made sense at the time of the release, but no longer. For the most up-to-date information about this topic, use a keyword in the search bar above. If you're looking for more current release notes, you can find those here.
In our June release we gave you the option to store and reuse credit cards for automatic recurring donations. Now we're taking that feature a step further: you can now store and reuse patrons' credit cards for ticket orders!
Where is this feature available?
You can use stored credit cards via the main "Create Ticket Order" interface (which we sometimes call the "Quick Order Form" or "QOF"), and if you're using PatronPortal to let patrons log in when they buy tickets online, those patrons will be able to securely store and access saved credit cards there as well.
How does it work?
To save a card for future use, start a ticket order from a contact record, or add items to the order and then select an existing contact. You'll notice that a "Save for future use" checkbox appears in the Credit Card section as long as a contact is selected:
You can ask the patron if he'd like to save the credit card for future use, to make his purchase even faster next time. If he says yes, check the box and complete the order as usual. Once the patron has a credit card stored on file, you'll be able to access it every time you submit a Ticket Order for that patron, and if he'd like to use his "Visa ending in 3891" for the purchase.
And if you're using PatronPortal, logged-in portal users can save their card for future purchases during the checkout process:
And access that card every subsequent time they log in:
Of course, you or your patrons can always elect to submit a new credit card number instead of using one that's stored.
Is this a security issue?
No. If you're familiar with our strict security policies around personally identifiable information ("PII"), you may be wondering how we're able to store credit card information in PatronManager. The answer is that we're not actually storing any credit card information in PatronManager.
The first time you (or your patrons) input credit card information and save it, our payment processor exchanges the credit card number for an encrypted version of that credit card number and stores a non-identifiable set of electronic digits (a payment token) in return. You can think of this token as a "passcode" that grants access to a secure encrypted version of the credit card info. Every time you submit a payment with that stored credit card, PatronManager passes only that token to our credit processor, which then uses the encrypted credit card number to charge the card.
How do I enable this feature?
This feature is not automatically enabled because we recommend that you discuss general usage policies with your staff (determining the language you want to use to invite patrons to store their credit card info, for example). Once you've got some ground rules in place for how you will use this feature, you'll need to email us to activate it for you.
Note that to use this, your organization must have already transitioned over to our new and improved payment gateway. It's likely you will know if this has already happened, but if you're not sure, feel free to contact the PatronManager Client Support team by submitting a case in the Client Community, and we will confirm that you've already transitioned, or get that process going.