#pawel - Connect & Old API
1 messages · Page 1 of 1 (latest)
Charges are a very old API and I'm not surprised they don't support afterpay_clearpay. I think you should look into using Payment Intents and Payment Methods.
Here is a pretty solid walk-through:
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
Yes, that's correct. I've seen the new payment intents API, and I know that we should upgrade. As for now, the client asked us for afterpay so I wonder if there was a way to add it in the old way, and upgrade later.
Is there any way to achieve this other than using intents with a dedicated payment element?
I do not think this is possible using Charges. If you migrate to Payment Intents and the universal payment_element then you can use the same form & elements for cards, Google/Apple pay, and afterpay_clearpay
I've seen that afterpay is not listed on the https://stripe.com/docs/sources#supported-payment-methods
but i just wanted confirm with you that its actually not supported.
I just double checked with some colleagues and any payment methods added after 2019 (which includes Afterpay/Clearpay) are only implemented on the PaymentIntent API
Thank you !