#proxymis-bancontact
jolly bluff
@pulsar hamlet if you want to support bancontact it does require making some changes to your code.
You mention things like \Stripe\Charge::create which is legacy(and doesn't support 3D Secure card payments).
Overall you should move to using our Checkout hosted payment page product which natively supports cards and Bancontact and creating subscriptions
https://stripe.com/docs/payments/checkout
https://stripe.com/docs/payments/bancontact/accept-a-payment
pulsar hamlet
So you are telling me... I need to rewrite everything and using checkout !
jolly bluff
@pulsar hamlet not necessarily but it would simplify things and allow you to support new payment methods and 3D Secure authentication and wallets like Apple/Google Pay.
But you do need to use PaymentIntents at least for Bancontact(seems like you don't currently?)
pulsar hamlet
Correct: I do not use PaymentsIntents
There are so many docs.. that I am lost with all possibilities. The strange thing is.. why do stripe publish some "old" methods that doe not allow 3D Secure for instance. Looks like I lost time before I realized I need to use checkout method
jolly bluff
why do stripe publish some "old" methods that doe not allow 3D Secure for instance
things like the Charges API were built before 3D Secure was prevalent. We have documented PaymentIntents as the default integration since 2019 so it or Checkout are what we'd recommend for an integration today.