Skip to content

Doc 1585/ttp step 3 sandbox and rename#586

Open
max-koro wants to merge 5 commits intomainfrom
DOC-1585/ttp-step-3-sandbox-and-rename
Open

Doc 1585/ttp step 3 sandbox and rename#586
max-koro wants to merge 5 commits intomainfrom
DOC-1585/ttp-step-3-sandbox-and-rename

Conversation

@max-koro
Copy link
Contributor

@max-koro max-koro commented Mar 6, 2026

No description provided.

@linear
Copy link

linear bot commented Mar 6, 2026

@netlify
Copy link

netlify bot commented Mar 6, 2026

Deploy Preview for incomparable-tiramisu-91a96a ready!

Name Link
🔨 Latest commit 636da12
🔍 Latest deploy log https://app.netlify.com/projects/incomparable-tiramisu-91a96a/deploys/69b82ecdbc465a00080bc308
😎 Deploy Preview https://deploy-preview-586--incomparable-tiramisu-91a96a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@racene-swan racene-swan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:::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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Chargebacks and disputes.
- Chargebacks and disputes

}
```

## Not yet available {#not-available}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Not yet available {#not-available}
## Coming soon {#not-available}

Positive


## Not yet available {#not-available}

Simulations for the following scenarios are not available yet:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Refunds.
- Refunds

- Chargebacks and disputes.
- Refunds.

These will be added in a future release.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove - added to the intro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants