Saved cards

A member signed in to your org can save a card and pay with it next time, without typing it again. The card is stored by Stripe on your Stripe account; Ovante keeps only its brand, last four digits and expiry.

Who can save a card

• Only people with a live membership, signed in with their member account. Everyone else pays as a guest each time.
• A card is saved with one org. It never carries over to another organizer.
• Members save a card in checkout, or add one from the payment methods on their membership page.

The default card

• A member's first saved card becomes their default.
• Checkout picks the default first, and a monthly or yearly membership renews on it.
• A member can't remove the card their membership renews on until another card is the default.
• When a member removes their default card, the most recently used card becomes the default.

The security code rule

Stripe asks for the card's security code when the member signed in more than 7 days ago, or the order is $500 or more. Adding a new card from the membership page also asks the member to confirm a sign-in code first unless they signed in recently.

What you see

• The person's page has a Saved cards card: each card's brand, last four, expiry and last use, with a Default chip. It's read-only: only the member can pay with their cards, and you can't charge them.
• The order drawer adds "Saved card" after the payment method when a card on file paid, and a transaction's page shows a "Saved card" chip.
• Refunds work as usual, even if the member has since removed the card.

Where saved cards don't work

• PayArc. Members can't save cards there. Switching to PayArc asks you to confirm when members have cards, and they type a card at checkout until you switch back.
• Requests. An order with a ticket that needs approval holds a card of its own and offers no saved cards.

For what members see, see Your saved cards.