Skip to content

Commit

Permalink
fix: fix stripe testing documentation (#444)
Browse files Browse the repository at this point in the history
type in the secrets command and wrong example value for
STRIPE_ENDPOINT_SECRET
  • Loading branch information
travis authored Nov 25, 2024
1 parent 180842f commit b6ee242
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,13 +58,13 @@ See: https://docs.sst.dev for more info on how things get deployed.
#### Testing Stripe Integration

To test the Stripe integration, set the `STRIPE_SECRET_KEY` and `STRIPE_ENDPOINT_SECRET`
secrets using `sst secret set` (use `npm exec sst -- secret set` to do this in the root of this project).
secrets using `sst secrets set` (use `npm exec sst -- secrets set` to do this in the root of this project).

`STRIPE_SECRET_KEY ` should be set to the "secret" API key found on the test mode API keys page: https://dashboard.stripe.com/test/apikeys

To get a value for `STRIPE_ENDPOINT_SECRET` you'll need to create a webhook on https://dashboard.stripe.com/test/webhooks and point it at the Stripe webhook handler for your development server. You can get webhook handler URL by adding `/stripe` to the end of the
`w3infra-UploadApiStack` `ApiEndpoint` output after running `npm start` and letting it deploy.
The full value of `STRIPE_ENDPOINT_SECRET` will look something like `https://z1jsa5b24d.execute-api.us-west-2.amazonaws.com/stripe`.
The full value of `STRIPE_ENDPOINT_SECRET` will look something like `whsec_AEWftGyXzREfERw4nMyPDFVCerafe`.

You can use the `stripe` CLI to trigger test events, like:

Expand Down

0 comments on commit b6ee242

Please sign in to comment.