New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stripe CLI: Trigger of "subscription.payment_succeeded" does not work #1116
Comments
I'm seeing this error as well, using the same cli and api versions as @DenisKnecht02. strangely enough, this also triggered a warning message from Stripe to our team as well: |
I'm seeing this error as well, using the same cli and api versions as @DenisKnecht02. Environment |
I'm having the same issue, MacOS 11.7.1 with event |
The same issue: $ stripe stripe trigger subscription.payment_succeeded
Setting up fixture for: payment_method
Running fixture for: payment_method
Trigger failed: Request failed, status=402, body={
"error": {
"message": "Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing. To enable raw card data APIs in test mode, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis.",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_wWx************",
"type": "invalid_request_error"
}
}
|
Update Stripe version with I was on 1.13.10 version and got same errors, updated to 1.19.2 and it's working now. |
Issue
I wanted to test a successful payment on a subscription by triggering the event via Stripe CLI. I talked to a developer in the Developer Discord. He tested it on MacOS, where it worked.
I used CLI versions v1.17.0 and v1.17.1 and API version 2023-08-16.
When editing the trigger, it shows the following fixtures etc:
Expected Behavior
Successful trigger of this event.
Steps to reproduce
stripe login
stripe trigger subscription.payment_succeeded
Traceback
The logs are:
Environment
Windows 10 Home 22H2
The text was updated successfully, but these errors were encountered: