Close-ups of CreditCardKit’s headline and a card whose monthly fee changed, beside its card-stack icon.

Key figures

Canadian cards in the catalogue
146
issuer pages and PDFs linked as sources
509
bank connections or card numbers needed
0

From issuer page to wallet

  1. Issuer sources

    • Card pages and PDFs
  2. Watched for changes

    Monitoring

    • Change detected
    • Capture quality checked
  3. Candidate

    Human review

    • Confirmed or rejected
  4. Wallets

    • Change notice
    • Date reminders
A changed page is only a candidate. Nothing reaches a cardholder’s wallet until a person confirms it.

Operating problem

Card fees, benefits, and reward rules change quietly. Cardholders rarely notice until a fee posts or a benefit lapses, and keeping track usually means a spreadsheet or handing over bank credentials.

What changed

Each card fact links to an issuer page or PDF. Those sources are watched for changes, and every change passes human review before it reaches the wallets holding that card. No bank connection or card number is needed.

System scope

  • Issuer-sourced card catalogue with edit history
  • Source monitoring with capture-quality checks
  • Private wallets with email-link sign-in
  • Reviewed change notices, reminders, and opt-in email

Technical constraints

  • Treat a changed issuer page as a candidate for review, never as a verified fact.
  • Keep unknown or unpublished terms explicit instead of guessing fees, rates, or reset dates.
  • Keep each cardholder's wallet, notes, and export isolated from other accounts and from the shared catalogue.

Evidence

Catalogue
146 Canadian cards backed by 509 issuer pages and PDFs.

Need a delivery partner for your software project?

Share the market, constraint, current state, and budget reality in writing. If it looks like a fit, you will get a human response with the next step.

Start a project
Next case study BorderlessKit A managed U.S. setup service for founders outside the United States.