4 comments

  • Joe TurnerJoe Turner, 8 years ago (edited 8 years ago )

    But what if a user was to go in and change the value of that field? They could pay what they want, no?

    0 points
    • Christopher CliffChristopher Cliff, 8 years ago

      This is meant to be the simplest approach possible, allowing you to process transactions manually or collect donations.

      If you were doing 100s of transactions per day or automating fulfillment, it would be more appropriate to invest in a full-featured back end.

      0 points
      • David KavanaghDavid Kavanagh, 8 years ago

        Sorry Chris - I'm confused, exactly what value does this provide then? Why would this be better than what Stripe offers?

        My experience says that if you're comfortable spinning up Heroku, you probably aren't going to use it to "... collect payments from a static website".

        0 points
        • Christopher CliffChristopher Cliff, 8 years ago

          A few things:

          • To clarify, Stripe doesn't provide an end-to-end solution for the browser. You need your own server. This one integrates easily with the official Stripe front end.
          • I think there's a HUGE difference between using Heroku Button and developing/deploying your own web application. The goal is to bring this technology into the realm of non-experts, e.g. front end developers and designers. Heroku is that easy these days.
          • As somebody who works in this space, I don't want to develop many separate payment services. This app covers a lot of use cases.
          0 points