Conversation
✅ Deploy Preview for incomparable-tiramisu-91a96a ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
racene-swan
left a comment
There was a problem hiding this comment.
Nice work with this - some minor formatting errors and a point about permissions. Good work pulling this together.
| Call the Stripe SDK's `confirmPaymentIntent` method to finalize the payment. | ||
| The payment is captured automatically. | ||
| :::tip Retrying a failed capture | ||
| If capture fails and you want to offer a retry (for example, with a different card), reuse the same payment intent. |
There was a problem hiding this comment.
| If capture fails and you want to offer a retry (for example, with a different card), reuse the same payment intent. | |
| Reuse the same payment intent to retry a failed capture with a different card. |
Simplify
|
|
||
| Call the Stripe SDK's `confirmPaymentIntent` method to finalize the payment. | ||
| The payment is captured automatically. | ||
| :::tip Retrying a failed capture |
There was a problem hiding this comment.
| :::tip Retrying a failed capture | |
| :::tip Retry a failed capture |
|
|
||
| # Initialize the device for payments | ||
|
|
||
| Connect your device to the Stripe Terminal reader before accepting payments. |
There was a problem hiding this comment.
| Connect your device to the Stripe Terminal reader before accepting payments. | |
| Connect your device to the Stripe Terminal reader to start accepting in-person card payments. |
| # Initialize the device for payments | ||
|
|
||
| Connect your device to the Stripe Terminal reader before accepting payments. | ||
| This involves setting up a connection token provider and running the reader discovery flow. |
There was a problem hiding this comment.
| This involves setting up a connection token provider and running the reader discovery flow. | |
| This process involves setting up a connection token provider and running the reader discovery flow. |
Updating the intro so it flows better.
| This involves setting up a connection token provider and running the reader discovery flow. | ||
|
|
||
| ## Prerequisites {#prerequisites} | ||
|
|
There was a problem hiding this comment.
You need the following to initialize your device.
The section needs an introductory text to improve flow. They need all of these things, right? Vs one or two?
|
|
||
| Simulations for the following scenarios are not available yet: | ||
|
|
||
| - Chargebacks and disputes. |
There was a problem hiding this comment.
| - Chargebacks and disputes. | |
| - Chargebacks and disputes |
| } | ||
| ``` | ||
|
|
||
| ## Not yet available {#not-available} |
There was a problem hiding this comment.
| ## Not yet available {#not-available} | |
| ## Coming soon {#not-available} |
Positive
|
|
||
| ## Not yet available {#not-available} | ||
|
|
||
| Simulations for the following scenarios are not available yet: |
There was a problem hiding this comment.
| Simulations for the following scenarios are not available yet: | |
| Simulations for the following scenarios are in development and will be included in a future release. |
?? Positive spin
| Simulations for the following scenarios are not available yet: | ||
|
|
||
| - Chargebacks and disputes. | ||
| - Refunds. |
There was a problem hiding this comment.
| - Refunds. | |
| - Refunds |
| - Chargebacks and disputes. | ||
| - Refunds. | ||
|
|
||
| These will be added in a future release. |
There was a problem hiding this comment.
Remove - added to the intro
No description provided.