#ht-beta-access

1 messages · Page 1 of 1 (latest)

coral rose
#

Hi there, I can't really say about how long it will take.

#

It is mostly up to that beta team and how many folks they are accepting into the beta.

sullen haven
#

Thanks @coral rose actually so only the updatePaymentIntent() is in beta? coz the rest of the API seems to be avaialble

coral rose
#

Mostly. The updatePaymentIntent() and the secret_key_confirmation parameter server-side are the two main things needed for that flow that aren't publicly available currently.

sullen haven
#

right

#

will the legacy way be deprecated?

jade pike
#

Hello! I'm taking over and catching up...

#

The legacy approach is not recommended and is already deprecated. It will continue to work for the foreseeable future though.

sullen haven
#

ah okay so it's matter of time before the beta implementation available publicly?

jade pike
#

Yep. No timeframe I can share though.

sullen haven
#

understand that

#

thanks for your time

jade pike
#

Happy to help!

#

We really do recommend client-side confirmation if possible though.

sullen haven
#

but even testing the beta need access right? And it's not in production yet?

jade pike
#

Correct.

#

Correct for the beta for server-side confirmation, I mean.

#

Client-side confirmation is available now.

sullen haven
#

yes understand that

#

but if we want to build some special workflow when the customer click "Pay" and confirming the payment. Then we need to build with server side confirmation?

jade pike
#

What kind of special workflow?

sullen haven
#

it's fine; I think as long as the legacy implementation works and we don't have beta access yet then will stick with legacy first

#

thanks for replying; apprecaite it