I'm migrating a custom coded cart application which was launched in 2016. It uses the Charge api. So, long story short, I had to get familiar with PaymentIntent, and it definitely took some time to research and implement. Anyways, I'm glad someone finally wrote this blog lost. I think the webhook was the missing piece of the puzzle for me here. I ended up just re-implementing the Charge calls with newer libraries. Now that I know about the web hook in the last step of PaymentIntent, I'll probably go back and finish this.
If you're younger, it's hard to express how revolutionary the "cURL to charge" demo was. Prior to Stripe, accepting online credit card payments required fax machines and smoke signals (ok, only one of those is true).
To set up an Authorize.net or Chase PaymentTech account, you'd have to fax multiple documents to several different companies, pay several hundred dollars, and *hope* that you weren't rejected for some arbitrary reason.
Stripe's a lot larger now, so they have stricter KYC requirements, and they can be stressful to deal with at times (from what others have said, I've never had a bad experience with them), but the original landing page was impactful.
Fun fact: Stripe was originally named `/dev/payments` (like a mounted device on a *nix system), but some state authority couldn't accept a forward slash as the first character in the name of a company, so they went with Stripe instead.
3 Comments
ninenulls@reddit
leftnode@reddit
Crafty_Disk_7026@reddit