#haydn5
short meteor
little cove
Good question. Checking in to where that data is stored. You may need to retrieve something on that event. Not all checkout data is sent with the event
unkempt axle
ya. Just weird it doesn't come over in the checkout session, yet the stripe docs says it should. https://stripe.com/docs/payments/checkout/custom-fields#retrieve-fields
little cove
It looks like this is happening because this feature is still in beta, so you need to have your webhook endpoint set up with the beta header:
To use this beta feature, you must update your checkout.session.completed webhook endpoint’s API version with the beta header, such as api_version: "2022-11-15;custom_fields_beta=v1".
https://stripe.com/docs/payments/payment-links#custom-fields:~:text=To use this,custom_fields_beta%3Dv1".
unkempt axle
Yep. I totally get that. The problem is, how do I upgrade? If I'm using the no-code custom fields, where do I go to put in the beta code? So far no one has been able to answer that.
where do I go…
I understand that 100%. The problem is it's all within stripe.
little cove
It should be a configuration in your dashboard when setting up the webhook endpoint
unkempt axle
no idea where to look for that. but I'll look again
little cove
Checking in to where this shows up myself
little cove
So it looks like this actually isn't settable in teh dashboard at the moment. You would need to create a new webhook endpoint via the API and pass 2022-11-15;custom_fields_beta=v1 in as the API version https://stripe.com/docs/api/webhook_endpoints/create#create_webhook_endpoint-api_version
unkempt axle
That's what I thought. I'm confused that Stripe allows for custom fields but doesn't actually pass the data along in the no-code area. That's a bummer 😦
mystic crane
What's the 'no-code area' in this context?
unkempt axle
Why provide the option for custom fields if you can't pass the data through?
mystic crane
We do – you just need to add some additional configuration to your webhook as we and the docs outlined. I realise that can be problematic for some Payment Links users, it's less than ideal. It's just how beta features work unfortunately.
But this additional configuration is only a requirement whilst the custom fields feature is still in beta. Once this actually released, the fields will be available on checkout.session.completed events without additional setup.
unkempt axle
ok. I totally get it. Just frustrating as it's halfway there, but not all the way. Any idea on when you think it will be out of beta?
mystic crane
You'd need to speak to the team directly about that (I guess you had an email about the feature)
unkempt axle
I got a few emails about the fields being in beta.
mystic crane
Just frustrating as it's halfway there, but not all the way
it is beta software, after all
unkempt axle
oh yes. I completely understand
mystic crane
I got a few emails about the fields being in beta.
I'd reply directly to one of those. We here have no timeline for beta features
unkempt axle
oh. ok. I figured those emails were noreply kind of things.
mystic crane
Normally there's an email from an address specific to that beta feature
mystic crane
sure, np!