- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've found a few threads that skimmed this question, but no direct question and answer.
Is there a way to develop and test an Accept.js integration on my local machine with the sandbox without an SSL certificate?
Solved! Go to Solution.
โ02-09-2017 10:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sadly, it is still true! I have been seeing this error "E_WC_02" when I am on http.
โ07-03-2019 12:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do think you could make your life easier by testing your server side code on localhost. The client side tokenization cannot be worked around from what it sounds. The tokenized data can be replaced with a dummy credit card number in an API call. I would build my transaction request exactly as I wanted it served side, set my sandbox to be as lax as possible so that I could avoid duplicate transactions kick backs and fraud triggers as much as possible. Once your server side code is executing exactly like you want, you would have a baseline to start with and could be sure that any subsequent issues were coming from the client side.
Then you would take out the cc info and put in the data descriptor and payment nonce in its place and start testing from either a live server or a TLS enabled localhost. Live server is just as easy for client side testing in my experience. You get error logging in the console. As a side note Iโm biting my tongue pretty hard right now. The amount of unnecessary bashing and complaining by developers on this freely provided forum is something else. Iโll just say that the grass isnโt greener anywhere else, as I just googled the https issue and Stripe has required TLS 1.2 connections for all API library initiated calls since July of 2018, and was https only before then. Itโs frustrating but I suppose thatโs why we donโt do it for free (except me, sometimes). Best of luck to you and hope to hear of some great progress.
โ07-03-2019 01:58 AM - edited โ07-03-2019 02:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still an Issue.. 9/3/19
Requiring SSL for local testing is absolutely ridiculous. WTF ANet?
โ09-03-2019 05:35 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still true on 9/3/19. What the actual F Anet? This is absolutely ridiculous. I know of no other payment processor that requires SSL when testing localling in a development environment. What at horrible waste of our time. Thanks a lot .. now I know what the A in Anet stands for.
โ09-03-2019 05:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Folks, I went through this thread, and saw that it is still not solved.
We're using this in a rails environment, and had success using NGROK to port localhost to an HTTPS URL, by setting `config.hosts` in your rails environment settings (\config\environments\<whatever you use, we use development>.rb to the HTTPS URL given when you start `ngrok https 3000` on your command line.
โ12-04-2020 10:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here in 2023, This is 5 years after someone said this was gonna get fixed.
Im using React. When I port my app through ngrok with and https connection, Im having issues. Any way you guys can fix the sandbox to use http instead of https?
โ02-16-2023 10:34 PM
- ยซ Previous
- Next ยป