#alti_best-practices
1 messages · Page 1 of 1 (latest)
đź‘‹ Welcome to your new thread!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
đź”— 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/1212461698531987476
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
⏲️ 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. Thank you for your patience!
Hello! To clarify, you have an existing Payment Method that was previously saved, and now you want to use that to confirm a Payment Intent client-side instead of using the Payment Element?
Are you still around @unborn cloud ?
Yes sorry
@rebus_stripe not sure what you mean by “you have an existing payment method”. Are you talking about a specific stripe api entity that would need to be created before ? What we have is the credit card details
No, they mean https://docs.stripe.com/api/payment_methods where the raw card details are collected in a PCI compliance way, and now you have a payment method id representing that card. How are you collecting these credit card details?
It’s collected via another front end
That’s what we’re trying to figure out - how we can create a payment intent without using stripe elements or stripe checkout
So you're asking, how can you process a payment using the card card details on the server side?
Yes
But ideally we’d like to create a payment intent so we can hook it up to the same processing flow we have using stripe elements
Hm, you lost me on 'we can hook it up to the same processing flow we have using stripe elements'. Can you clarify?
If you're asking if you can pass raw card details on the server-side, we don’t recommend using card numbers directly in API calls or server-side code due to PCI compliance. You can learn more about it here, https://docs.stripe.com/security/guide unless you're PCI compliant, your server-side code should never have access to a customer's raw card number.
The front end that collect these is PcI compliant. Can we create a payment intent with this card info ?
The idea is that if the payment intent is created by the PCI compliant front end, using our stripe connect publishable key, we’d get a webhook hit when the payment intent is processed and the charge is created
I see, in this case, you'd want to review this: https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis and you'll need to reach out to our support team as a next step.
Perfect thx !