Editorial Policy
Use the instructions for your card
Card programs, issuers, distribution methods and country-specific terms can differ. The agreement and instructions supplied with your particular card take precedence over a general article. A legacy agreement is identified as historical and is not treated as a universal current rule.
Verify operational claims
The source register records a title, URL, verification date when available and a scope note. Specific destination or program claims are linked to that evidence. If a portal cannot be read or a workflow cannot be verified, the limitation is stated. We do not invent phone numbers, settlement deadlines or account procedures.
Label uncertainty
Error records distinguish officially documented, observed, unverified and unknown information. A code listed as a search topic is not proof it is currently displayed by the service. An official definition requires a relevant primary source. General troubleshooting suggestions are not guaranteed fixes.
Dates and authorship
Content modules record publication, review and modification dates separately. A visible “Last reviewed” date records an editorial review of the article and its evidence, not verification of a reader’s card or every current portal workflow. Source checks are recorded separately. We do not invent authors, credentials or publication dates.
Corrections
Use the editorial email on the contact page for corrections. Identify the page, explain the correction and include a relevant public source if possible. Never send card credentials, billing information or account screenshots. Card-specific problems belong with the support service printed on your card.