From b6ee242ba04a97362ae37e85c253774d7ca85ce9 Mon Sep 17 00:00:00 2001 From: Travis Vachon Date: Mon, 25 Nov 2024 18:57:50 +0100 Subject: [PATCH] fix: fix stripe testing documentation (#444) type in the secrets command and wrong example value for STRIPE_ENDPOINT_SECRET --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0369b22f..a9da4316 100644 --- a/README.md +++ b/README.md @@ -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: