3 ms·
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 s
by 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]