#ionu_api
zenith cargoBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1239910040106700851
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
crude laurel
hi there!
- for now it works, and there are no plans to remove it. but in general we recommend to use the new approach with the Stripe-Account header
- no expiration date
jaunty yacht
Thanks. The reason I am needing it, is for frontend tokenization. But if there are no plans to remove it, than it is great.
crude laurel
yeah it should continue to work for a while.
jaunty yacht
@crude laurel is there any other way to get a publishable key after the connection is done? Just in case 🙂
crude laurel
no, that's one of the reason we recommend using the Stripe-Account header instead.
jaunty yacht
that being the case for the front end tokenization as well, right ?
crude laurel
I'm not sure what that means. can you clarify what you are trying to do exactly?
jaunty yacht
import {loadStripe} from '@stripe/stripe-js';
const stripe = await loadStripe(public_key);
this.stripe.createToken(card, billing_data).then((result) -> get the token
this way we get the token to send in the backend for generating the transactions
In this case we need the public key to load it
crude laurel
using Tokens to accept payments is also a very old API that we no longer recommend using.
instead you should be using PaymentIntent and PaymentMethod: https://docs.stripe.com/payments/payment-intents/migration
jaunty yacht
oh, ok. That would make the publishable key redundant.
We will look into it.
Thank you very much