#hooky_testing-subscriptions

1 messages · Page 1 of 1 (latest)

floral cypressBOT
gusty epochBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

floral cypressBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1235974285143834634

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

gusty epochBOT
vivid bluff
#

Hi there 👋 you should be wary of the error message about not passing raw card details, you will likely want to use our frontend components via Stripe Elements to collect payment method details.

potent cape
vivid bluff
#

For that failed request, I believe the problem here is that the you're trying to create a Subscription rather than just process a payment.

#

What is the flow you're trying to test?

potent cape
#

Yeah. The flow is a subscription creation. We are a company that helps with payment recovery, churn, etc. In this case, I am testing reactivations: a campaign for a canceled subscription (emails offering to start the subscription again).

So in my testing process, I "trigger" a campaign by creating a test cstomer, a test subscription, and cancelling it.

#

I had this code working. I am surprised I didn't get the credit card number warning until now. Maybe it is a small oversight that you guys don't throw that error if one is using Connect?

vivid bluff
#

I think it's more likely the other account you're using may have been granted an exception to the raw card details rule. You can still pass raw details if you need to, but now to do so you have to work with our Support team to ensure PCI compliance and have that feature enabled.

#

Do you need to process raw card details, and if so are you PCI compliant?

potent cape
#

No, I don't need that really. I use Stripe Elements in production.

#

Ohhh, maybe I could use Stripe Elements to generate my test subscrpitions? Although it may be a bit of a hassle, but is that feasible?

#

All I am using this for (the raw card details) is for running test scenarios: Like, simulating a customer creating a sub and then canceling, which triggers my system.

vivid bluff
#

Yup, I'm pretty sure that's what you're going to need to do. pm_card_visa isn't set up to be a specific Payment Method on a Customer, so I believe it's expected for it to not work as the default_payment_method for a Subscription.

potent cape
#

Ahhhh I see!

vivid bluff
#

I'm pretty sure you can use it with an intent to create a new Payment Method for your Customer, and then use that new PM for testing.

potent cape
#

would I need to use Elements?

#

or is there a sequence I can do programatically?

vivid bluff
#

If you already have a functioning elements flow in testmode, it may be faster to use that. Otherwise I'd suggest trying to create and confirm a Setup Intent for your Customer. I'd suggest trying to do it as an off-session intent to save some steps.

potent cape
#

Awesome, thank you, that is helpful

vivid bluff
#

Any time! Let me know if that doesn't work out for any reason

floral cypressBOT
#

hooky_testing-subscriptions