BUG MAJOR - New users can't open doors after adding credit card info

[hightechhostel]

This bug has been reported by two users now (second user reports using Android phone). The new user logins in (via Twilio) and then enters their credit card information. The app shows a message like "Valid Credit Card Info Entered", however the button on that page that says "Check-In and Open Doors" does not work.

However, if the user goes back to the home page at door.nomadawhat.com, and logs in again (via Twilio) the "Check-In and Open Doors" will work this time.

[siruguri]

what if they just stay on the page for a few seconds, and hit refresh? I suspect this is a delay in Stripe as it accepts their CC information that we can't get around ... maybe add some text that says to refresh if the button's not working just yet? Or add a Refresh button that page?

[hightechhostel]

If the page is refreshed it looks like it will work. However, I'm still a little confused why stripe would cause the delay. When you have the alert that says, "Valid Credit Card Info Entered", that's only being shown once Stripe has validated the card info, right? And the button that says, ""Check-In and Open Doors", that posts to your app (not Stripe) right?

In any case, I think the solution would ideally be transparent to the user, rather than having them refresh the page again. In my (non-programmer) mind we could do something like:

1. Delay the load of this page (with a loader gif) until the required resources for the button are available.
2. Load the page immediately but only have the button appear by ajax once the required resources for the button are available.
3. Have the button post you your application (which I thought it did) that starts a process that will push the button virtually. Because once the page has loaded, the resources should be available (shouldn't they?).

Thanks.

[siruguri]

A loader gif would be nice, but it's a lot of work ... Stripe first says
the CC # looks okay, and then it has to process the credit card into a
customer ID who can be charged later, which takes a little time... So by
the time the door app server renders the dashboard, that customer ID may
not be available.

I'd rather just have a link in there that lets the user hit refresh until
Stripe is ready to start charging their card.

On Fri, Dec 18, 2015 at 10:20 PM, hightechhostel [email protected]
wrote:

If the page is refreshed it looks like it will work. However, I'm still a
little confused why stripe would cause the delay. When you have the alert
that says, "Valid Credit Card Info Entered", that's only being shown once
Stripe has validated the card info, right? And the button that says,
""Check-In and Open Doors", that posts to your app (not Stripe) right?

In any case, I think the solution would ideally be transparent to the
user, rather than having them refresh the page again. In my
(non-programmer) mind we could do something like:

Delay the load of this page (with a loader gif) until the required
resources for the button are available.
2.

Load the page immediately but only have the button appear by ajax once
the required resources for the button are available.
3.

Have the button post you your application (which I thought it did)
that starts a process that will push the button virtually. Because once the
page has loaded, the resources should be available (shouldn't they?).

Thanks.

—
Reply to this email directly or view it on GitHub
#46 (comment).

[hightechhostel]

I don't fully understand what you are saying in the context of what I'm seeing on the page. When I say the button doesn't do anything, it like the button has no action assigned to it and it's not even attempting to make a call to the server. I think you would test this before you do any changes.

In any case, rather than have a "reload" button that makes it seem like something doesn't work and we are hacking our way around it. I think it would be better if we have an intermediate step for the user to "Activate Account". This would essentially reload to the page and by this time Stripe has provided the resources you need to make the button clickable.

See attached.