[MKT_949]:feature/ add turnstileToken for checkout payloads

[jaaaaavier]

Adds an optional turnstileToken field to the three checkout payloads so the checkout client can forward a Cloudflare Turnstile token to the payments API.

[xabg2]

If captcha token is the fallback one and turnstile is the primary, should the captcha token optional and the other one the required? 🤔

[jaaaaavier]

If captcha token is the fallback one and turnstile is the primary, should the captcha token optional and the other one the required? 🤔

It makes sense, and that’s how I saw it, but I considered the scenario where perhaps these interfaces are used on sites I dont know, and I wouldn’t want to break anything, then I also considered the scenario where Cloudflare goes down, for example (just as Google might), and I thought it’s better to have the fallback as the required and this one as optional. Bearing in mind what I said earlier, I don’t know if, for example, any other object-storage repo use interfaces.

[xabg2]

If captcha token is the fallback one and turnstile is the primary, should the captcha token optional and the other one the required? 🤔

It makes sense, and that’s how I saw it, but I considered the scenario where perhaps these interfaces are used on sites I dont know, and I wouldn’t want to break anything, then I also considered the scenario where Cloudflare goes down, for example (just as Google might), and I thought it’s better to have the fallback as the required and this one as optional. Bearing in mind what I said earlier, I don’t know if, for example, any other object-storage repo use interfaces.

You can check if the interface is used in other places. The thing here is that, if we are changing from captcha to turnstile, it should be applied everywhere.