- rfahaitiAsked on October 27, 2012 at 01:03 PM
There seems to be an issue with the input area for the Stripe live secret and publishable keys. My keys are 100% accurate yet I receive the message that they aren't.
- Chief Technology OfficereeeAnswered on October 27, 2012 at 02:31 PM
Could you please send a screenshot of the error ?
- rfahaitiAnswered on October 27, 2012 at 06:36 PM
Hi, I'm in email correspondance with Kade -- curently I'm waiting for your response (firstname.lastname@example.org). Seems like it's definitely an issue on your end.
- JotForm SupportjonathanAnswered on October 27, 2012 at 07:19 PM
Hi, Thank you for the updated response. You will be informed when there is new in progress.
- Chief Technology OfficereeeAnswered on October 28, 2012 at 05:15 AM
I have checked out your form and saw that you're entering a wrong secret key (Secret keys start with prefix "sk_" and publishable keys with "pk_")
I have sent an email to Stripe to learn if it's a case of usage (without sk_ prefix) or not.
- rfahaitiAnswered on October 28, 2012 at 12:03 PM
I can assure you my secret key does not start with sk_ and works just fine for other applications.
- rfahaitiAnswered on October 28, 2012 at 12:26 PM
UPDATE: I have confirmation from Stripe employee that the sk_ in the key is purely cosemtic.
- JotForm SupportjonathanAnswered on October 28, 2012 at 12:36 PM
Will you be able also to provide some more details? A screen capture of some details like the key would help a lot in figuring out the issue. You can also send the attached screen in the email (in your email exchange with Kade)
- rfahaitiAnswered on October 28, 2012 at 12:39 PM
Hi Jonathan, sending screen captures exposes potentially sensitive information. The secret keys are secret for a reason. I can ensure you that what I have provided in the form is 100% accurate as it's currently working with another application. Earlier Ertugrul said that he "saw that I am entering a wrong secret key" so you must already see what the key is. Hopefully this isn't a breach in privacy.
- JotForm SupportDeygusAnswered on October 28, 2012 at 12:51 PM
Hello, I'm Kade, the one that you spoke with in your emails. I apologize for not getting back to you sooner on this issue as well as to the fact of what my colleague has questioned you with a screenshot for. That is something that is meant to be kept secret so you certainly have that right as it is understandable. It was also not intended to be an invasive manuver just a way for us to help try to figure out what the problem is so that we can justify it.
I've gone ahead and marked this thread as Private so that this conversation is not shown to anyone else outside of you, me, or the rest of the Support Team to protect your privacy and information incase you change your mind though.
What I was refering to was when I originally talking to you was that I tested this integration it didn't work at first but then when I regenerated the API Key as I had told you the integration finally worked.
I'm not quite sure why it is doing this other then a possible data mismatch and server communication error and that was not too long ago that I tested this but I'm going to do some more testing again and I will get back to you shortly with my results and hopefully with a solution to your problem.
- rfahaitiAnswered on October 28, 2012 at 12:57 PM
Hi Kade, Could you please keep this thread public? I'm not sharing sensitive informaiton so there's no reason to make it private.
- JotForm SupportDeygusAnswered on October 28, 2012 at 01:04 PM
Alright no problem I will respect your wishes for that.
I am wondering something though, when you're doing your testing with the integration are you using the Test Keys or are you using the Live Keys?
- rfahaitiAnswered on October 28, 2012 at 01:06 PM
To test, one uses the Test Keys -- because that data can be erased via the dashboard. However, when I attempted to setup via JotForms I inputted my live keys. I'm talking with Stripe about the issue as well. I'm not happy that you guys actually have access to the secret keys I inputted. I would have hoped that you guys not have access to sensitive information.
- JotForm SupportDeygusAnswered on October 28, 2012 at 01:47 PM
I've tested the integration and could not find any further problems so therefore I am going to let eee handle the rest of this problem because he is one of our developers and will be more helpful to you for this problem instead me.
- Chief Technology OfficereeeAnswered on October 28, 2012 at 02:00 PM
I had a confirmation from John at Stripe.com, old Secret keys may have or not "sk_" prefix.
I have committed an update on Stripe wizard to solve the problem,
Sorry for the delay,
Thank you for your time and patience,
Sorry for the confusion. Publishable keys have always been prefixed
with pk_, but the sk_ prefix was only rolled out a while ago. Secret
keys created before that don't have any prefix. I hope this hasn't
caused undue confusion.
John - Stripe.com