aromatt

[turbid apex]

I appreciate this is hardly considered being directly related to stripe itself but I am very early in the development still in the design phase and just want to consider what would be achievable and discard ideas that make no sense early

Unfortunately I don't know enough about firebase to say immediately say one way or another. Can you tell me more about what this middle step would do that you couldn't do by directly talk to the server?

[lapis owl]

The idea is that backend front end and communication layers are completely separate and independent. I dropped the name firebase here as this is specifically what is considered at the moment, but we could say it doesn't have to be that. What firebase would do in our example is just store the messages and both front end and back end would be able to submit and receive content of relevant ones

I was wondering if it is generally bad idea to have payment information stored somewhere temporarily before actually being processed

I can obviously encrypt that whilst it is stored. I read somewhere that you could in theory use serverless solutions like aws lambda mixed in as well but need to do more research on that particular solution

From stripe perspective I understand it doesn't make a difference who is initiating the payment processing as long as secret keys etc are in tact you just handle it

So it makes sense to have that on the back end

But I also know you have react components for example

[turbid apex]

Yeah, it is safe to store the info that we send you like IDs and how much you charged and whatnot. As long as you are keeping secrets off of the client you should be in good shape

[lapis owl]

Do you happen to know if it is common practice to use something like aws lambda to handle payments? That would essentially make payments completely independent of my backend app and logic

Sorry if this sounds irrelevant to stripe

[turbid apex]

Unfortunately I'm not that familiar with AWS lambdas either to really speak to that. Can you tell me what your concerns are about using that?

If I understand you correctly, from our perspective, firebase or this lambda would be another component of your backend. We just know that you have your frontend and use something to process the rest of this somewhere else

[lapis owl]

It's more about use of the react components and if those can actually pass the info wherever I want them to to handle and the processing can take place later in some intervals or does it have to be in real time

I probably make things unnecessary convoluted and not being clear apologies