#lkjhgfdsa-link-testmode
1 messages · Page 1 of 1 (latest)
Hi there 👋 would you be able to share the ID of a Payment Intent that was used for your testing that I can take a closer look at? Additionally, is your test site publicly available so I could take a closer look at the flow there?
This is the last payment method I created using link
pm_1NTRHqRFh7vhwn75iR5nsYMd
I think it is. You should be able to make a donation here.
https://testplatform.stratuslive.com/uwgc/get-involved/donate/andrews-page-builder-testing
Thank you, taking a look!
lkjhgfdsa-link-testmode
I see the behavior you're describing, and am looking through settings now to see if I spot anything that could be causing it. While I do that, do you have an example from live mode that I can compare this against?
We are not recording the payloads in production like I am currently doing in my local environment. We recieved a null reference exception trying to read the CC details in production.
I can get you the payment that failed for us in production
Payment intent: pi_3NSmRURBcu58Z7uu0Y00ZiR9
Payment Method: pm_1NSmRxRBcu58Z7uu6mfiJqhi
Thank you for that! So a difference I'm seeing here is in how the Payment Intents are being created.
In production you're using Automatic Payment Methods, which is returning card and link as valid payment method types on the Payment Intent:
https://dashboard.stripe.com/logs/req_1xmxVIpX3wo2pA
But in test mode, automatic payment methods aren't being used, payment_method_types is explicitly being passed in with only card in it.
https://dashboard.stripe.com/test/logs/req_iLeHX7xij1jN7Q
Comparing yoru livemode and testmode payment method settings for your Connected Accounts, it looks like Link is on by default for both modes, so I don't think there is a concern there.