Imansur-cancel-sub | Stripe Developers | Page 1

storm aspen Sep 8, 2022, 4:22 PM

#

Hi there

#

Can you provide the request ID of the error?

#

And can you provide an example where you did this successfully in the past?

latent cloak Sep 8, 2022, 4:24 PM

#

Here's the request ID for the error: req_k9L0MwbvuAs8E0

#

And one that went through a couple of weeks ago: req_FxQUGkhCova8Yu

storm aspen Sep 8, 2022, 4:27 PM

#

Thanks, looking

#

Ah okay

#

One is your prod platform account and one is your dev platform account, correct?

latent cloak Sep 8, 2022, 4:34 PM

#

correct

storm aspen Sep 8, 2022, 4:34 PM

#

Yeah the accounts have different config

#

One sec

#

Okay will you try again now?

latent cloak Sep 8, 2022, 4:39 PM

#

The cancel went through, but not the update I tried beforehand (req_OLdzYBYXiVQfTD)

#

What changed? 🤔

storm aspen Sep 8, 2022, 4:45 PM

#

You have an example from a successful update from before?

latent cloak Sep 8, 2022, 4:46 PM

#

I don't—this is something new I'm testing

storm aspen Sep 8, 2022, 4:47 PM

#

Yeah we don't allow you to update Subs from another platform.

latent cloak Sep 8, 2022, 4:49 PM

#

Gotcha. What changed on the cancel front?

#

Did you have to change something on your end? Is this something we should've enabled when first setting up Connect?

storm aspen Sep 8, 2022, 4:52 PM

#

Yep I changed the account config to match your production account

latent cloak Sep 8, 2022, 4:52 PM

#

I see. Is that config public to us? That is, can we change it should we create another account for testing purposes?

storm aspen Sep 8, 2022, 4:53 PM

#

No it isn't public

#

If this happens in the future you should reach out to our Support team (https://support.stripe.com/contact/login) and ask that they match your dev account to your prod account

#Imansur-cancel-sub