search

regen-network / rnd-dev-team

RND Dev Team issue management (DEPRECATED)
0 stars 0 forks source link

Research/design clickwrap agreement functionality in buyer checkout flow #181

Closed erikalogie closed 2 years ago

erikalogie commented 4 years ago

Design options:

1) Version 1 with button to agree only. This one also shows the error message if the user does not scroll to the end of the agreement before clicking "agree". We could have the same error state in the Version 2 and 3 popups too: https://www.figma.com/file/FvdeKSEOhiZAOFfN6KauAR/Project-and-Projects-Registry-Current?node-id=3753%3A2 2) Version 2 where user types their name: https://www.figma.com/file/FvdeKSEOhiZAOFfN6KauAR/Project-and-Projects-Registry-Current?node-id=3753%3A172 3) Version 3 where user types name and provides a signature: https://www.figma.com/file/FvdeKSEOhiZAOFfN6KauAR/Project-and-Projects-Registry-Current?node-id=3754%3A1

NOTE: I didn't make a "print" button because that can be accomplished with the "email a copy" functionality after they receive the email. Also note that I am recommending putting this as a popup that appears on top of the payment page after they hit "pay now" (you can see the payment page just to the left in Figma).

Additional Artifacts:

Are you sure you want to decline? popup: https://www.figma.com/file/FvdeKSEOhiZAOFfN6KauAR/Project-and-Projects-Registry-Current?node-id=3753%3A216

Task description:

As a product manager, I want to make the purchase of a credit include a legally enforceable contract.

Implementation - tbd whether to use Docusign (https://www.docusign.com/products/click) or implement in-house.

Acceptance criteria:

  1. Agreement needs to be prominent (i.e. link available) , ideally they can print it if they want ; mobile-friendly
  2. User must show intention - typing their name, checking the box and having the option to cancel ; some require scrolling down through the agreement (aka scrollwrap)
  3. Buyer (and seller) accepts doing business electronically
  4. Attribution - the signature, name, IP address timestamp and doc signed are all clearly recorded
  5. Legal agreement has to be valid and appropriate in terms of governing rules for instance
  6. Provide easy access to document afterwards - we can place this in project page documentation tab The exact legal language to include in the ERPA and show in the checkout flow is ideally something a lawyer with e-commerce experience provides us so we have our bases covered (but it seems the above requirements are the general requirements).

More information: https://support.docusign.com/en/guides/click-user-guide

Legal clickwrap interaction https://docs.google.com/document/d/1ixLoQ273agGLLyY8nh2rnPDGkoz7qW83Huh0wa2FY_k/edit#heading=h.e8pd5bjx4dns

erikalogie commented 4 years ago

Blocked by clarity from legal

rsteinhe commented 3 years ago

@rsteinhe Send reminder to lawyer

erikalogie commented 3 years ago

@rsteinhe This is ready to review.

rsteinhe commented 3 years ago

@erikalogie this is good, do you want to create a prototype link that I can share with the lawyer? He's not super responsive but regardless it'll be good to share with whomever we work with.

erikalogie commented 3 years ago

@rsteinhe I've created some screencasts of version 1 and version 2 of the clickwraps only, since you said that version 3 where they would create a signature image was unnecessary. I have Figma prototypes for these too, but I think those might be too confusing for the lawyer, so these .mov files are likely better to share with him: https://drive.google.com/drive/u/2/folders/10IexPP8s2zXl_J7XSLEeMl-3oZwrDGM6

rsteinhe commented 3 years ago

@erikalogie see comments on thread with Andrew. We might need to do a preview to approve payment.

erikalogie commented 3 years ago

Ok, maybe let's discuss during our longer meeting tomorrow?

On Thu, Dec 17, 2020 at 2:57 PM Ron S notifications@github.com wrote:

@erikalogie https://github.com/erikalogie see comments on thread with Andrew. We might need to do a preview to approve payment.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/regen-network/regen-registry/issues/181#issuecomment-747633257, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACARPTJ3F43L3J4F7HXMZX3SVJIDFANCNFSM4TEVH2RA .

rsteinhe commented 3 years ago

Pending comments from Andrew (lawyer) which needs to be hired formally. Moving back to product backlog until then.