Topic guideOfficial guideUpdated Apr 29, 2026 · 9 min read

Cards

Conceptual playbook for freezes, geography rules, replacements, without sensitive card artefacts.

  • Card face uses masked dots instead of PAN segments — illustrative only.
  • Freeze/spend tiers reflect control patterns; live card data never renders here.

Overview

Cards combine spending convenience with rich controls—freezes, merchant categories, travel toggles, and replacement flows. Community can describe what those controls feel like; Support tracks shipment timelines and dispute envelopes tied to your account.

Controls worth knowing upfront

  • Digital freezes propagate quickly—explain what you toggled verbally, never via photos of embossed numbers.
  • Merchant category quirks (fuel, lodging, groceries) behave predictably—but exact MCC labels stay in dashboards.
  • Replacement timelines depend on courier region; peers can speculate on averages, Support pins tracking.
  • Never photograph chips, holograms, or mag stripes—even obfuscation leaks metadata.

Triage politely after a decline

  1. Freeze the card immediately if charges look unfamiliar—then gather context inside authenticated history.
  2. Retry using smaller pre-auth expectations at fuel pumps or rental counters before assuming rail failure.
  3. If phishing is plausible, rotate unrelated passwords and report via Support fraud queues—not group chats.
  4. Download receipt PDFs through official portals when Support requests evidence—skip forwarding via DMs.

Decline patterns peers recognize

StatusWhat it usually means
Geography blockTravel toggles or region rules fired—discuss toggles abstractly, not itineraries with amounts.
Velocity / limitCard-level caps differ from bank transfer limits; cross-read Fees & Limits for vocabulary.
Issuer maintenanceNetworks occasionally pause BIN ranges—Support confirms if it is widespread vs just you.