#jbuck94-payments-subs
final sorrel
Hello! Is there a specific reason you want to be working with Tokens? You can't create Tokens or Payment Methods directly with the PaymentElement, and tokens in general aren't really what most new integrations work with
torn moon
Interesting - that's how id seen a bunch of examples online. I was doing this to avoid passing sensitive info (CC/account numbers) to my own API
What is the preferred approach ?
final sorrel
Using Payment Element already allows you to avoid passing sensitive data to your own server - if you click "Checkout or Elements" at https://stripe.com/docs/security/guide#validating-pci-compliance, you can see we mention that card information never touches your server
In terms of the preferred approach, I'd recommend reading through https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements which goes through all the steps.
But backing up for a minute - is your goal here to minimize the amount of engineering work you need to put into this?
torn moon
Generally yes
final sorrel
Checkout is a much simpler integration, and should be compatible with usage-based subscritions
You'd still need code to report the usage (unless you wanted to do this yourself through the dashboard), but Checkout would take care of the initial payment method colelction
torn moon
do you have a doc on what that implementation would look like? The "read server and client implementation" link here is a 404 https://dashboard.stripe.com/settings/checkout
final sorrel
You can read about it here: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=checkout
and we have a "quickstart" version that walks through it really quick at https://stripe.com/docs/billing/quickstart