#javeeik_code

1 messages ยท Page 1 of 1 (latest)

clever walrusBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ 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.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— 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/1367133649014751313

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

surreal ibex
#

Hi ๐Ÿ‘‹ sorry if I overlooked it, but I'm not seeing a question in your post. What are you hoping to get answered?

Seems like this may relate to 3DS, and that you're still on a Charges integration. If you want an SCA compliant flow that is prepared to handle 3DS challenges, you'll need to look into migrating to an integration based on Payment Intents:
https://docs.stripe.com/payments/payment-intents/migration/charges

tawdry junco
#

sorry i didnt fill in the middle bit in very well as we are in a bit of a shit sitch!

that we understand, we were hoping somone might be able to assist with which is likely our best route:

 A) rip out Payum for Stripe and add a bare Checkout Session + webhook 
 B) upgrade Payum to 2.x and use flux-se/payum-stripe-bundle 3.0

Anything scary in jumping Payum 1.x โ†’ 2.x? Tips welcome.

this has happened on event day as we were...tits and didnt test with the 3ds cards, DOH!

surreal ibex
#

I'm not sure, I don't know what Payum is. Is that a prebuilt integration being provided to you be a third party? If so, I'd suggest reaching out to their support team for more insight on what upgrading their integration entails, and what additional features it grants you access to.

clever walrusBOT
tawdry junco
#

Payum is an open-source PHP library that wraps many payment gateways (Stripe, PayPal, Klarna, etc.) behind a single API. Our fork is on payum/stripe 1.5.1, which still calls Stripe\Charge::create()

was hoping somone might have been through this nightmare themselves - were trying to work out path of least resistance and whats going to cause us the least mess.

If youre not familiar with Payum, maybe we are best looking to create our own checkout session as there is probably more support available?

do you have any sample PHP code for Checkout Session or Payment Intent migration?

surreal ibex
#

We don't really have migration guides for migrating from a pre-built integration to a custom-built one. We do have plenty of guides for building your own integration though.

For Checkout Sessions, I'd suggest starting there to get an understanding for the three variants of those that exist before jumping into a guide for building a Checkout Session integration:
https://docs.stripe.com/payments/checkout/build-integration#compare-features-and-availability

For a Payment Element integration using Payment Intents, I'd suggest starting here:
https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements

tawdry junco
#

thanks Toby, appreciate your time mate!