What is Saving Card on File and why is it the most important feature for your silent auction?
Saving a Card on File is the process of having guests pre-register a credit card at registration so they can avoid having to line up to pay at the end of the event. It is done with the Bidstation app, which integrates Square for card payments.
Bidstation tracks all winning bids, purchases and donations by bidder number. Square processes the payments when it is optimal for organizers (typically after the event ends, when final amounts owing have been confirmed).
Silent auctions are unique events in that they involve both an event end time, when most attendees are ready to leave, as well as auction purchases that require payment. When both these situations happen at once, it leads to exceptionally long checkout lines.
Lining up is a negative way to end an evening or special event, and it is not uncommon for some guests to leave without collecting and paying for their auction items.
The process of Saving Cards on File eliminates this issue. It involves swiping card magstrips or using the Square chip reader for chip insert at check-in/registration to securely vault a card payment token that can be charged at a later time. The credit card information is linked to the bidder number so that any winning bids or purchases made with that number are added to the attendee’s invoice. When a card is Saved on File, a card icon will be displayed in the Attendee’s profile in the app.
*When saving a card on file, you may only do so using Square hardware to swipe the magstrip, inserting the chip or manually inputting the card details. Cards cannot be saved on file from digital wallets or taps.
When processing a payment in the app, all methods are supported, including tap for cards and digital wallets. Typically payments are being processed for attendees that do not have a card on file but need to pay at checkout. The app will offer options to either save the card on file or process the payment, when an attendee has a balance owing.
With this Express Checkout function, the card is not charged if no balance is owing.
Important notes for saving card on file and processing payments.
- When saving a card on file (COF), the app performs a $1.00 pre-authorization. This is not a charge and will not incur any fees. It only validates the card with this small amount, then it cancels the $1.00. (see how this works in the video above)
- Hardware: when connecting the Bluetooth reader, you have the option to tap and insert chip. But Square can only save a card on file with the chip, magstripe swipe or manual card entry. The app will alert you to this as well and show an error message if you try to save a card with a tap.
- Payments with tap: When an attendee has a balance owing, you have the option to save the card on file OR take a live payment. If you take a payment, you may use any method to do so (tap, chip, swipe, manual) from cards and digital wallets (phone wallets). You may instead save the card on file first, then process the payment against the card on file via the app, if you wanted to have the card on file for any potential add-on purchases/donations following the event. But if you don’t need the card to be saved, you can just do the live payment.
- Testing: Square’s terms are specific about limiting test transactions. We advise that you limit your card on file and payment testing to up to 2 actions, and keep the amount set at 1.00 only, not less or more. Square’s risk systems may flag your account if you go outside of this.
- Account hygiene: It is common for many organizations to have new Square accounts that they’ve opened for Bidstation use or accounts that they might only use once a year for their event. Processing a large batch of payments once a year, or on a new account, can trigger risk flags on Square’s automated systems. We suggest contacting Square support account services department ahead of your event so you can let them know and give them an opportunity to request any additional information at that time and they can make a note on your file to expect the activity.