Feat: Learn + Document How to Setup Recurring Payment Processing about learn-payment-processing HOT 7 CLOSED

The reason I've left PayPal, ApplePay, GoogleWallet in the OP is simple: Critical Mass.
PayPal has 377 Million active people using their App/service!
There's a very good chance that a person wanting to use our app already has a PayPal account.
And since they most likely are logged into their PayPal on the computer/phone they are using,
then it's just 2 taps to checkout. 🏁 💰 🎉

from learn-payment-processing.

@LuchoTurtle how much have you looked into Payment Processing? 💳
Does understanding how this all works appeal to you? 💰
If not, don't worry; it's not everyone's cup-of-tea. 🍵
But if you're keen, please comment. 💬 🙏

from learn-payment-processing.

I've never worked with payment processing before but I guess I'll have a look 👍

from learn-payment-processing.

@nelsonic I have a few questions, as this topic seems a bit broad.

• Should I narrow this to an Elixir API? Flutter?
• Should I use Stripe? The issue implies using other gateways...?

from learn-payment-processing.

For now we just need generic research that is applicable to any programming language that can make HTTP (REST API) requests. This can be Python, JavaScript or Elixir.

When we are creating our example we can use Elixir or Rust.

As for using Stripe, yes, for now that is the appropriate gateway/provider.
I've left it open in the OP because if PayPal has a comparable UI/UX/API and pricing, we could use that.

from learn-payment-processing.

Wasteful screenshot:

Constrained (show just the info needed and minimise whitespace) screenshot:

This might not seem like such a big deal. But these add up over time.
Don't waste people's bandwidth or time scrolling through unnecessarily large images.

I've hidden the "or email" because it's not relevant to this example.

from learn-payment-processing.

from learn-payment-processing.