Stripe card component and API

Hi @jclutterbuck,

No worries, Stripe has made this way too complex in my opinion as I was doing some more testing and it seems like you are correct in that it is not inherently clear how the newly created token should be passed in with the Stripe Query :sweat_smile:

I was imaging you could add it to the body, but none of the predefined options include stripeToken but it appears that Retool's Stripe query is outdated and is still pull in body options from the outdated PaymentMethod API.

It looks like we have an internal ticket to fix that, I can add a +1 to that ticket but it seems to be far down the teams roadmap :sweat:

In terms of current options:

  1. I found this other forum post here about some creative work arounds that a forum power user built out to accept payments in Retool with Stripe.

The gist is that you could use a REST API Resource instead to build your own query, that will pass the token from the component in the query's body as outlined in Stripe's docs here.

The user also builds their own custom component to handle all the logic which is definitely some heavy lifting, but could be a viable option if fully built out.

  1. Another potentially easier option would be to have a button in a Retool app redirect users to a Stripe hosted checkout page at another URL, as I describe in another post with a user here. This way the Stripe hosted page handles all the code logic and card processing and you don't need to built out a REST API query/resource in Retool to accomplish the same thing.

My guess is that opening this in a new tab would allow the Retool app to stay open and not require a redirect URL.

To be frank, since Retool is made for internal tools, the majority of our Stripe integrations are for getting information and data about a user's Stripe accounts to be used as an internal tool for viewing and monitoring customer payments and Stripe events(such as a dashboard or using a table).

Retool was not created to be an externally facing app that accepts payments. If the above work arounds are not configurable or working as needed and payment intake is a critical part of your app, I would likely recommend another tool which has Stripe Payment accepting integrations as a major feature, such as Wix or Square.