3 ms·

> Their docs are typically good, but the SCA / Payment Intents docs are not really at the same standards as the rest of their documentation yet. Stripe PM on t

> Their docs are typically good, but the SCA / Payment Intents docs are not really at the same standards as the rest of their documentation yet. Stripe PM on the Payment Intents API here. You're right that there were some rough edges when we started rolling out this new API last year. SCA is complex and we want to help make it easy to navigate this regulation: we designed the new APIs to abstract away as much of the complexity as we can. In addition, thanks to a lot of feedback from users, we made important changes to our docs architecture, guides, API reference, and Dashboard in November 2019, and are continuing to iterate on it. I would love feedback on how we can further improve our documentation. I’m olivier@stripe.com.

Silhouette 7y ago
FWIW, one thing you could usefully do is have someone double-check the code snippets in the online guides. They looked very helpful (and much needed) when I was reading them recently, but I remember almost immediately running into examples where something just didn't make sense. Then if I followed through to the corresponding code in the samples repo, it really was slightly different to what was shown in the guide on your docs site. The guide to setting up a new subscription using the new API definitely had some instances of that problem. The more recent guides would also benefit from more explanation of why the sequence of actions shown was what it was and what each API or webhook used was actually for. Either that or some concise, big picture overview would be good (or ideally both).
chrischen 7y ago
One of the main tough things with the SCA / Payment Intents is that we have to keep our payment state in sync with Stripe's (updating the amount to charge and syncing with the cart total), and then syncing with a webhook. The transaction apparently happens in a separate process from the customer's browser session. With PayPal you simply send a request for a certain amount, and when it gets approved the customer's client comes back with a token and you choose to execute it or not. If you don't execute, the charge just isn't completed. Stripe's docs says to not depend on the client because the client can close the browser window. In the PayPal case, if that happens, the transaction is simply canceled (since the client closed before finishing). EDIT: It looks like Stripe's docs do support the PayPal style integration, but recommends against it because it doesn't work with longer-delay asynchronous methods. It's funny because PayPal's old API was done in this way (with instant payment notification webhooks) and their new API is closer to Stripe's old API.
- deleted 7y ago
  [deleted]

Silhouette 7y ago

FWIW, one thing you could usefully do is have someone double-check the code snippets in the online guides. They looked very helpful (and much needed) when I was reading them recently, but I remember almost immediately running into examples where something just didn't make sense. Then if I followed through to the corresponding code in the samples repo, it really was slightly different to what was shown in the guide on your docs site. The guide to setting up a new subscription using the new API definitely had some instances of that problem. The more recent guides would also benefit from more explanation of why the sequence of actions shown was what it was and what each API or webhook used was actually for. Either that or some concise, big picture overview would be good (or ideally both).

chrischen 7y ago

One of the main tough things with the SCA / Payment Intents is that we have to keep our payment state in sync with Stripe's (updating the amount to charge and syncing with the cart total), and then syncing with a webhook. The transaction apparently happens in a separate process from the customer's browser session. With PayPal you simply send a request for a certain amount, and when it gets approved the customer's client comes back with a token and you choose to execute it or not. If you don't execute, the charge just isn't completed. Stripe's docs says to not depend on the client because the client can close the browser window. In the PayPal case, if that happens, the transaction is simply canceled (since the client closed before finishing). EDIT: It looks like Stripe's docs do support the PayPal style integration, but recommends against it because it doesn't work with longer-delay asynchronous methods. It's funny because PayPal's old API was done in this way (with instant payment notification webhooks) and their new API is closer to Stripe's old API.

deleted 7y ago
[deleted]