141–149 of 149 posts
Earlier quoted context omitted.
Enable charges of more than $1mil please.
Curious what your use case is.
You could certainly pay less than ~$20,000 in Stripe/CC fees to move $1M if your motives were on the up and up. Especially if you were doing it regularly.
Earlier quoted context omitted.
Add eBay to the second list. We are still uploading XML documents.
eBay is an absolute nightmare. They have a demo instance to test on and it's about 4 years out of date and half of it doesn't work anymore.
Stripe is by far the best developer experience I’ve had in my career working with third party APIs/services. The attention to detail is just second to none, and documentation is a big part of this.
I felt that way until I needed to prepare for the new EU credit card regulation that came into effect a few months back and implement Stripe's update for it. There's a bunch of gotchas in the transition - e.g. you can't apply coupons when creating subscriptions with the new checkout flow (needed to handle 2FA), "sources" and "payment methods" show up in the same list in Stripe's UI, but are not fetched by the same AP…
Earlier quoted context omitted.
eBay is an absolute nightmare. They have a demo instance to test on and it's about 4 years out of date and half of it doesn't work anymore.
Okay, it's not just me (demo instance). Ebay's APIs and their SDK documentation (or lack thereof) are making me re-think my app's monetization model. Docs are shockingly bad, full of screenshots that look like ebay from the early 2000s.
Earlier quoted context omitted.
Top APIs I've enjoyed working with: 1. Stripe (Best) 2. Twilio 3. Twitter (Does what it needs to do quickly) 4. Puppeteer (Amazing. Was super helpful.) 5. Google (mostly ok but could be better) APIs I've hated working with: 1. Paypal (the worst - docs are horrible and UI is not consistent with most of the help material out there because it changes all the time. Have you tried their support? That's a beauty) 2. Facebo…
Just be thankful you haven't worked in healthcare.
Earlier quoted context omitted.
eBay is an absolute nightmare. They have a demo instance to test on and it's about 4 years out of date and half of it doesn't work anymore.
For those interested, the demo instance is at https://sandbox.ebay.com/ The message at the top says "eBay and PayPal will be separate companies soon", even though they became seperate companies 4 years ago.
Mousing over the links there to see where they go, the first interesting-looking one was the supported/unsupported features list, over at https://ebaydts.com/eBayKBDetails?KBid=684. Ah, I see - a wall of text reminscent of "system requirements", except it's a list of things you don't get instead.
But then going up to https://ebaydts.com, I met with... a blank page. But it has a title, so something's blown up. I hit F12 half expecting to be met with some kind of implosion, and even then I was cynically amused: the page has ``, with no closing quote, and while Chrome parses it properly the devtools don't, so the CSS editor leaks bits of HTML.
On the one hand my infosec-sense says there's probably some awesome stuff hiding in here... but on the other hand, between the 1000 feet of bureaucracy I'd have to all but drown to report _anything_ I found, and the tenterhooks I'd be on while poking around establishing there's anything there beyond plausible deniability... not worth it?
Earlier quoted context omitted.
This is a free equivalent to ngrok and it only uses SSH - https://serveo.net/ - and it accepts custom subdomains. I spin it up for each project like this with $DOMAIN and $PORT being defined/fixed for each project and the connection kept open permanently using autossh: ssh -R $DOMAIN:80:localhost:$PORT serveo.net There are API endpoints for creating, listing and deleting webhooks in Stripe now too - my test suites an…
I've started using `serveo.net` to monitor my internet uptime (Raspberry Pi with a simple webserver, [updown.io]( https://updown.io ) to request it via [serveo.net]( https://serveo.net) ) but they were unavailable/offline for ~4 days within the last 10 days.
Serveo is temporarily disabled due to phishing.
Serveo will return in a few days with a few new
restrictions to help dissuade abuse. Thanks for your patience!Earlier quoted context omitted.
I've started using `serveo.net` to monitor my internet uptime (Raspberry Pi with a simple webserver, [updown.io]( https://updown.io ) to request it via [serveo.net]( https://serveo.net) ) but they were unavailable/offline for ~4 days within the last 10 days.
Currently offline due to phishing. Serveo is temporarily disabled due to phishing. Serveo will return in a few days with a few new restrictions to help dissuade abuse. Thanks for your patience!