I have an app that uses stripe payments and I am trying to allow users' cards to be charged. I have successfully changed the pk_test to pk_live but I am having issues changing sk_test to sk_live. I had paid someone to install stripe for me, and the only reference I can see to sk is inside of node.js as
const stripe = require('stripe')(functionConfig().stripesecretkeys.key);
This leads me to believe that the individual used terminal to reference the sk_test. My question is, how can I change this to be live instead of test.
I see this on firebase Doc,
firebase functions:config:set stripe.secret=<YOUR STRIPE LIVE SECRET KEY>
EDIT:
I have managed to add the secret key in through terminal, but when I create a new customer they are still being created under test mode on stripe? am I missing something?
Related
I implemented a Stripe payment system on a product selling Rails app; in development, everything works fine, even the webhook's to conclude the purchase.
But when after deployed to heroku, when i try to make the purchase process, it gets stuck after clicking the "Buy" button.... On Heroku logs it displays the following Fatal message:
" Stripe::AuthenticationError (No API key provided. Set your API key using "Stripe.api_key = ". You can generate API keys from the Stripe web interface."
But everything was pushed and migrated.
Any hints?
Thank you
Assuming you used a gem like "dotenv" for the API keys and other keys in development, you need to pass the keys to heroku like so:
heroku config:set STRIPE_KEY=abcdefg...
Issue: I created a new Stripe account and connected it to my application, did all the new test publishing and secret api keys... Added to my credentials and config.
All of my keys are successfully called with :
Rails.application.credentials.dig(:stripe, :publishable_key),
...in both config and stripe.js file
I update my keys in credentials and make a test payment and get
No such token: tok_1EKxxxxxxxxxxxhQKy
I then manually put in the new publishable key in the stripe.js file, and it works...
To test, I tried entering the old test key, and i get the same errors. So i am assuming the credentials dig is getting my old keys because its the same error?
Is it possible the credentials is somehow not updating?
Now, one issue i can think of is, in the past i used atom to update my credentials, and it never worked. I recently came across a post hat atom doesn't work with credentials but nano does. So i implemented this and it worked (up until i entered new keys in). So i am wondering if my old inputs into the old atom credentials could be interfering? I doubt it but might be worth mentioning
What could be done to fix this as i want to implement using credentials?
All of the keys are test keys and in their right places.
I'm assuming, in the stripe.js file, the credentials or the dig is only fetching the old key?
Because when i manually put in the old test key, it doesn't work with same error as the credentials dig.
This was all working fine until i updated the credentials for the new keys...
Spring cached credentials file.
Run this command:
spring stop
I am using stripe component in my application,when I tested with sk_test_1XXXXXX all payments were success,now I changed that key to another sk_test_2XXX,when iam trying to pay through this,getting an error "No such custome -cus_xxxxxxxxxxx".How to resolve this.
You created that customer with your 1st test key. These customers will be invisible (as well as any cards, subscriptions, etc) to your second test key.
Once you changed / moved key you'll need to recreate these test customers, they are not shared between test keys and accounts.
Your customer does not exist. Try login into the stripe dashboard and seeing if that customer exists.
I'm developing an iOS Project using a Braintree Payment roll for transaction processing. I'm using the API at SCViewController.m line 86 from the Braintree iOS Library and that code was working perfectly.
I created a new Braintree Sandbox accout and put its encryption key into our project, but now I get this error:
Problem acquiring reference to the public key, OSStatus == 0
What do I need to do to make the new encryption key work in my project?
The SampleProject is creating a VTClient object here. When that object is created, you pass in your Braintree client-side encryption key and your merchant ID.
That error is happening because you're passing in an incorrect Braintree client-side encryption key. Please make sure that you're using the correct sandbox client-side encryption key and sandbox merchant ID, which can be found logging in to the sandbox Braintree site.
Also, keep in mind that there are different client-side encryption keys and merchant IDs for sandbox vs production environments. When you create the VTClient, you can specify which environment you're working in - and ensure that you're passing in the appropriate credentials for that environment.
Braintree dev here - as a result of some recent internal upgrades, a small number of CSE keys in our sandbox were generated incorrectly. From your error message, it looks like you may have been bit by this issue.
We've regenerated keys for the affected users. If you go back to the Sandbox and copy your new CSE key, it should now work. If it doesn't, please reach out to our support (support#braintreepayments.com) directly and we'll be in touch.
Thanks,
-SP
I am new to both paypal and substruct. I trying to integrate paypal with 'Substruct'. The problem I am facing is that the payment status codes are not being updated in the admin panel.
All of them are on Hold even when paypal sandbox successfully confirmed the orders. From the web somebody suggested that the 'notify_url' needs to be set in the confirm order form
Paypal documention says the same as well.
https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=developer/e_howto_html_Appx_websitestandard_htmlvariables
What value should I provide to the notify_url so that the webserver on my machine is notified. BTW my webserver is behind a LAN.
check the substruct documentation # http://code.google.com/p/substruct/wiki/PayPal