A mission of financial literacy, kept narrow on purpose

Digital Card Guide exists to support a practical kind of financial literacy. We help readers understand the payment tools they already meet: the wallet on a phone, the number on a card, the prompt that asks for approval, and the line that later appears on a statement. Financial technology is crowded with product names. Our work is to explain the underlying arrangements in calm, specific language.

The mission is educational. We describe how a tool works, who typically controls it, and which questions are worth asking before you depend on it. We separate a description from a sales argument. Firms that offer payment products often explain them clearly, and sometimes they do not. Either way, an explanation from a seller serves a commercial purpose. Ours does not. We do not rank products, and we do not suggest that a reader open, close, or switch an account.

Definitions of common payment tools, written for a careful non-specialist. Comparisons of formats, such as a virtual number and a physical card, based on how the credential is exposed. Security habits that do not depend on a particular brand. Notes on where a practice differs by country or by issuer.

We write about categories. A briefing may name a kind of institution — a bank, a card network, a device maker — when that is needed to explain who holds a credential. It will not tell you which brand to prefer.

We do not provide personal advice about your finances, your taxes, or a dispute with a provider. We do not hold funds, issue cards, or process payments. We do not operate a marketplace, and we do not accept payment for favourable coverage. We do not ask readers to create an account on this site.

Nothing here is a substitute for the official terms, disclosures, or statements of your own provider. Those documents govern your account. A general description on a reference site does not.

Each briefing is prepared by the editorial desk and checked against public explanations from issuers, networks, and standards bodies where those sources are available. When a point is unsettled, we say so. When a rule is local, we do not present it as universal.

Readers should still confirm the current terms of their own provider. Product designs and network rules change faster than any reference page, and a detail that is true of one issuer may be untrue of another.

If we have a fact wrong, write to the editorial desk with the page address and the public source you would like us to consider. We would rather amend a sentence than defend it. We do not need your account number to correct a page, and we ask that you leave it out.