Guest purchasing / GDPR Non Compliance

  • Resolved sukalo

    (@sukalo)


    2 years, 11 months ago

    Currently your plugin offers:

    Require Login To Checkout?

    If ticked then user needs to be logged in to view or pay invoice, can only view or pay their own invoice. If unticked then anyone can view or pay the invoice.

    This means guests cannot purchase from payment forms unless signed in already to your website or if you untick the require login they can BUT ANYONE can view everyone’s invoices by changing the invoice ID in a url which shows personal data such as billing address etc. I’m pretty sure this is completely illegal and website owners risk being sued for GDPR Non Compliance unless the customer agreed for their personal information to be freely available on the Web (which nobody would).

    Some changes needed..

    1. Login to view invoices mandatory unless customers choose for guests to be able to view their invoice or some sort of share invoice option to specific people / emails.

    2. Guest checkout option which creates a new account using their email like when you create an invoice for someone.

    Sorry if this message comes on strong but it’s a brilliant plugin that I want to work and use without risk for myself and clients.

    Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Brian Mutende

    (@picocodes)

    Hi @sukalo,

    We do not use invoice IDs in the URL as this can be easily guessed. Instead, we use an invoice key that is impossible to guess. You can check any invoice’s URL to confirm this.

    The Require Login To Checkout option only prevents logged-out users from viewing or paying for existing invoices.

    It does not stop them from using the payment buttons to buy items from your store.

    Thread Starter sukalo

    (@sukalo)

    Morning Brian, apologies it seems when I tested this before I was copying the secret key in the url too which obviously would allow access.. when removing this you’re correct it doesn’t let you access.

    The guest purchasing is prevented when the login to checkout is active though.

    Here’s a payment form example with the login to checkout active on my website at the moment.

    Payment form

    Plugin Contributor Paolo

    (@paoltaia)

    @sukalo I pinged Brian, he’ll get back to you asap.

    Thanks for your patience,

    Plugin Contributor Brian Mutende

    (@picocodes)

    Seems I was mistaken. I’ve added a task to add the feature request. You can track its progress here. https://github.com/AyeCode/invoicing/issues/690

    Thread Starter sukalo

    (@sukalo)

    Thank you Paolo & Brian once again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Guest purchasing / GDPR Non Compliance’ is closed to new replies.