Payment methods

Norcube uses Stripe for card storage and charging. Card data is collected by Stripe's hosted Payment Element — the numbers never touch Norcube's servers; we hold only an opaque reference.

Add a card

1. Billing → Payment Methods → Add payment method — "Cards saved for off-session billing of your monthly invoices."
2. Fill in the Stripe Payment Element (rendered by Stripe, styled to match the dashboard).
3. Add card. If your bank requires Strong Customer Authentication (3-D Secure), you authenticate inline right there — that's what authorises future off-session monthly charges.

If it's your first card, it becomes the default automatically.

Defaults and removal

The saved-cards list — "The default card is used for monthly invoices. Set a different default or remove cards you no longer use." — shows each card's brand, last four digits, country, funding type, and expiry, with a Default badge on the active one.

• Set default on any other card takes effect immediately; the next charge uses it.
• Remove (with confirmation) detaches the card. Keep a working default on file — an org with usage but no chargeable card gets reminder emails and, at invoice time, enters dunning territory.

Handy behaviours you don't have to think about:

• Re-adding the same physical card replaces the old entry instead of duplicating it (and inherits default status if the old one had it).
• Expiry warnings: you're emailed about 30 days before a saved card expires.

SCA re-authentication

European cards sometimes demand fresh SCA for an off-session charge. When that happens the charge can't complete silently:

1. You receive a dunning email — "confirm with your bank" — with a link.
2. The link opens a page in the dashboard that re-runs the payment on-session; you complete the 3-D Secure challenge inline.
3. The invoice is marked paid and everything continues normally.

The link stays valid throughout the 14-day grace window.

Behaviour and edge cases

• Per-organization wallets. Each org has its own Stripe customer and its own cards; nothing is shared between your orgs.
• Charging requires more than a card — complete billing preferences are also required before any charge is attempted.
• Card data never touches Norcube servers — tokenisation happens inside Stripe's element.

Related

• Invoices — what the default card gets charged for.
• Dunning — the recovery path when a charge fails.