Can’t add my wife as an additional cardholder on my credit card, because she once used her phone number on a Barclays account of her own.

  • Australis13@fedia.io
    link
    fedilink
    arrow-up
    7
    arrow-down
    3
    ·
    7 days ago

    Unfortunately this somewhat makes sense… Now, if her account has been closed, then this is a design flaw. But if it’s still there - just hasn’t been used in ages - then this sanity-check makes sense to prevent fraud.

      • Australis13@fedia.io
        link
        fedilink
        arrow-up
        3
        ·
        7 days ago

        True. I guess given that the way I’ve always done it here (one contacts the bank directly to open a new joint account) rather than trying to add a second person to an existing account, I hadn’t considered that approach. Still, I can somewhat understand the rationale behind this design.

        • dave@feddit.ukOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          7 days ago

          You can’t have a joint credit card account. It has to be in one person’s name.

        • funkless_eck@sh.itjust.works
          link
          fedilink
          arrow-up
          11
          ·
          7 days ago

          also mobile numbers are a bad identity vector. Some keep theirs for decades, others may change them several times a year every year.

        • lad@programming.dev
          link
          fedilink
          English
          arrow-up
          7
          ·
          7 days ago

          Having a rationale is good, contradicting real use-cases is not so much. I met validations that are constructed without a lot of cases in mind lots of times. My favourite one was assuming the zip code is always 5–6 numbers, which is not always the case in length and in some countries it’s not numbers at all, and that was a logistical company that was supposed to know things well