#tylertc10

1 messages · Page 1 of 1 (latest)

lyric nimbusBOT
fathom walrus
#

Hello

#

Can you share an example object ID from your account for whatever flow you use that I can take a look at?

#

Also if you know which integration flow you use, like Stripe Checkout vs. Elements vs. an older integration then that would be helpful too.

blazing summit
#

Yes also is there a more private way to chat because it looks like everyone's tickets are public

#

Stripe Checkout

fathom walrus
#

This is a public server, if you want to chat in private then you would want to reach out to our Support team via https://support.stripe.com/contact/login. To be clear, object IDs are not sensitive as nothing can be done with them without your secret key.

#

Okay with Stripe Checkout you won't really need to make any changes with the new API version

blazing summit
#

oh okay sounds good

fathom walrus
#

Actually, the only change might be if you are charging your customers off_session later on.

blazing summit
#

As in object id what do you mean a subscription object?

fathom walrus
#

Are you doing that?

#

Do you only use Subscriptions?

blazing summit
#

We only have subscriptions

fathom walrus
#

Then you are fine and no changes needed.

#

This would only affect if you are taking one-time payments off_session

#

Or using Elements (not Stripe Checkout)

blazing summit
#

Is there a way to double check that?

fathom walrus
#

The recommendation whenever you upgrade your API version is always to thoroughly test it out in test mode.

blazing summit
#

Can I do that with REST api?