#garymoon

1 messages ยท Page 1 of 1 (latest)

runic pagodaBOT
weary edge
#

Nothing specific, no, that's a fairly complete (if high level) list.

I'd say the most difficult part is likely "edge case" which depend on your integration (various kinds of payment failure, authentication, etc).

wooden magnet
#

"High level" was exactly how I described it to the boss man lol.

#

I've raised questions before about testing after going live, and I feel the absence of such guidance here is quite conspicuous. Is there really nothing Stripe are willing to suggest? There's no way any customer who's just spent however long integrating the platform into their product is pushing it to production and just watching their logs waiting for a customer to attempt a purchase.

weary edge
#

We have test mode to mimic live mode as close as possible for exactly this kind of testing. When you switch to your live keys, yes it should work the same way but with real payment.

#

And yes I would expect during your initial payments (possibly a real self-purchase smoke test) you'd be watching your own logs an your Stripe account logs for anything unexpected

#

Note that "testing" in live mode is prohibited, but you can make real purchases from your own business

wooden magnet
#

At this point Stripe could put a โ„ข after everywhere I see the word "should" ๐Ÿ˜ฆ

#

Is there a different place things like this are supposed to be discussed? Like is it a taboo topic in public or something?

weary edge
#

No not really, I'm happy to help you address any issues, but I'm not sure what exactly you're looking for. If you've tested thoroughly in test mode, I would expect your live mode payments to work the same way. There can be new edge cases you didn't handle, of course, but there's no way to prepare for unknown unknowns aside from good logging and general error handling.

wooden magnet
#

Like I said above, no one is tossing a payments integration into prod and crossing their fingers, but every interaction I have with Stripe seems to indicate that's exactly what we're expected to do ๐Ÿคทโ€โ™‚๏ธ

What I'm looking for is advice/learnings that address the realities of deploying an integration that literally involves dollars exchanging hands from a practical perspective. If I'm not going to get it then I suppose that's that, but it's...let's say uncool...the way this question is treated.

weary edge
#

More specific testing depend on exactly what features you're using

reef dune
#

Hello ๐Ÿ‘‹
Taking over as synthrider needs to step away soon, let us know if the above link helps or if you have any follow up questions ๐Ÿ™‚

wooden magnet
#

To be clear, I love the work you guys do, and this Discord has been an invaluable resource for us during development. It's the response to this question only that is causing frustration.

Is there any chance that opening a ticket or any other action on our behalf will lead to some answers? We're basically at the point of having to just do what we think is best without any guidance from Stripe after a month of dev work.

#

Thanks hanzo. I've had the same response every time I've asked about this topic, so I guess that's that.

reef dune
#

To be honest (from a developer perspective and not as a Stripe employee), there are a lot of variables when it comes to going to production. There's really no way for Stripe to have a single document or a resource to list all of them in one place.

Even if you were to talk to another engineer from Stripe, they would say the same thing as my colleague mentioned above. If you do have a specific concern such as let's say "you create a subscription but are not sure if the renewal invoices are going to succeed or not" then there are ways we can help but at this point the question is very open ended.

wooden magnet
#

To be frank, it's open ended to cast as wide a net as possible, because thus far all responses on this topic are totally unsatisfactory, to the point one wonders if they're being gaslit.

reef dune
#

I totally understand your frustration. Its just that without understanding how your integration is built and works, there's no way for us to anticipate what could go wrong. If you have specific concerns, yes our team can help for sure!