December 13, 2019

The final test of Stripe/ payment flow

Göran B Svensson @JAMStack

We chose to use for payment processing. First, we tried to use Litch. But with Litch we were not able to transfer the user from the payment page all the way to the GCP function and the Firestore database. combined with Stripe works quite well. The only problem is that they seem to have made it a bit too complicated to set up subscription offers.

Why didn't we just use Stripe for subscriptions? We wanted to get something up fast so we opted to use something that could process subscriptions without developing our own node.js server that receives webhooks from Stripe. Why reinvent the wheel? So, therefore, we selected for payment processing.

It was a lot of trial and error getting the Github user and payment offer from the static Hugo site to and also configure a
subscription offer on

This is only the beginning. The next phase, marketing is also a tuff nut to crack. :-)

Loading comments...