#cnguyen-elements-cardonly
weak briar
ocean anchor
I want to use setupintent
but i don't want to use the stripe form with all the other payment solution like klarna, etcc
so I want to do a custom payment form
do you have a link with an example for this ?
near wadi
why?
ocean anchor
because i want that
near wadi
you want what? sorry you didn't really clear explain what the issue is. You can use PaymentElement and do card only for example if the problem is you don't want Klarna. Can you be specific about wht you are really trying to do?
ocean anchor
I want to purpose a customize payment form to my customer
with SetupIntent
in order to save the customer card for offline payment
glacial ferry
The point of Stripe's elements is so sensitive data never touches your systems or servers, and removing the PCI Compliance burden from your company (a long and annual audit process). Is your company ready to take on that burden?
near wadi
@ocean anchor I'm sorry you're still going really fast and saying words a bit too vague
"all payment solutions" what does that mean? Do you mean you just want to collect card details?
because if so, we already support that and it's easy to fix and I can show you how
ocean anchor
klarna, ideal, etc...
I want only one form with one payment solution
the stripe one
but not the other tab (klarna, afterpay, etc)
near wadi
😅
You want to collect card details, and nothing else. Is that correct?
You said "the stripe one" but I don't know what that means
near wadi
The best integration path is to use PaymentElement and only configure it for cards. Would that work for you?
ocean anchor
In the first picture, you have multiple tab => Klarna, AfterPay, etc... Can we remove this ?
glacial ferry
All those other methods (indeed, all methods) are OPTIONAL
ocean anchor
If you say that with paymentElement we can do this kind of payment form (here it's an exemple, it will be a setupintent without 53€ ofc). It's good 😄
near wadi
Have you tried at all? Or did you just stop at the docs? Just to understand at which step you are right now?
ocean anchor
I used to use the CVCElement, CardElement, etc..; to make my custom checkout
near wadi
that still works, you can still use that and it's totally fine?
ocean anchor
And now, I start a new project with a new custom payment form. I have to handle a setupintent to make future payment
So I read the doc and I see that you have a new way
but before to do it, I want to check with you if it's pssible to do it
because, in the documentation, I only see the uncustomize and multiple payment form with StripeElement
near wadi
You can keep the original code you have and call confirmCardSetup() and it will work just fine
Or you can use SetupIntents and pass payment_method_types: ['card'] on creation so that it only supports card details
cnguyen-elements-cardonly
ocean anchor
and with the new way, can I custome the payment form as I show you above ?
near wadi
it won't be exactly what you showed us above, but yes you can do a lot of customization. Mostly spend a few minutes trying it, that will be a lot more explicit
ocean anchor
ok. And where is the doc to handle with CvcElement, etc..; with setupIntent ?