Feat: Learn + Document How to Setup Recurring Payment Processing

[nelsonic]

Thinking of using Stripe as their APIs are decent. 🧑‍💻
(Fly.io are using Stripe and the interface is seamless!)
Buuuutttt ... from experience, many people have PayPal accounts ... 📈
And then there's Amazon Pay, Apple Pay and Google Play Store ... 🙄

So let's take a step back and consider our requirements. 💭

Requirements

• Simplest possible interface for making/collecting payments.
• Single payments (e.g. Year-in-advance) first
• Recurring payments e.g: Monthly second.
• Understand what is required to create a "Merchant Account"?
• Document everything in as much detail as possible.
• Create a basic App that connects to a Sandbox API.
• Ship the basic app to Fly.io so that we can all test it using dummy credit cards.

Story

As a person wanting to maximise their personal effectiveness,
I want to pay up-front for the service
so I know exactly what I'm getting.

Priority?

I know this might not look like the highest priority when our MVP is far from useful at this point.
But as soon as it is useful, we want to have the pricing page on dwyl.com ready and payment collection enabled
because it lends credibility to the product. i.e. if people know they can pay for it, they know it's "real".

[nelsonic]

@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. 💬 🙏

[LuchoTurtle]

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