#jagberg-token
1 messages · Page 1 of 1 (latest)
hi there! which token are you referring to? Can you share the docs which you're looking at?
I was looking in: https://stripe.com/docs/api/tokens
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Its the payment token for paying by card
there's no expiry time on Stripe's end. A card token is single use only, unless attached to a customer.
Is there a reason why you're attempting to create a Token though? You should really be using our latest integration / APIs i.e. PaymentMethods instead
is there any expiry on the form or anything else in stripe?
im comparing to another provider of ours who has a timeout and wanted to compare the implementation
i'm afraid the question is a little vague, there may be an expiry time on certain objects, but it's difficult to list everything upfront
i'd suggest taking a look at the step by step guide : https://stripe.com/docs/payments/accept-a-payment
if you load the iframe with the credit card fields, when you submit the form you get a token. Then using that token you can take a payment
so wanted to find out if theres any timeouts/expirations related to loading of that form and the time between getting the token and taking a payment using the token
no there isn't any timeout or expirations as far as I'm aware for the flow you've described. But it sounds like you're using Legacy Checkout which is heavily deprecated at this point - can you share the code for loading that form / iframe so that I can take a look? Remember to redact any sensitive information like API keys in case they're included in your code