#andregagnon_unexpected

1 messages ¡ Page 1 of 1 (latest)

inner fiberBOT
#

👋 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/1440537127602491484

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

sweet tiger
#

hello! Gimme a while to take a look

#

do you have a sense of when this stopped working? i.e. was it working fine previously?

lapis sparrow
#

Maybe 3 hours ago? Yes it was working previously

sweet tiger
#

do you have a example page which we can access to view the issue?

lapis sparrow
#

Sure, we patched ours, but let me roll it back

sweet tiger
#

oh, if you patched it, that's fine then

#

don't worry about rolling it back

#

but to clarify, you're using the deferred intent flow where you pass in setupFutureUsage=null in the options?

lapis sparrow
#

Ah, yes, exactly

#

We patched it, it's not a problem. But we are a distributed platform on WordPress, so our users have to manually update. Many don't know their payments are down. This also is affecting Easy Digital Downloads as a platform too. Perhaps others.

sweet tiger
#

okay, we're going to raise this to the relevant team to look into this right now. Thanks for flagging this!

lapis sparrow
#

Thanks for the attention on it!

#

Some more info. Creating a payment intent serverside returns null for setup_future_usage with this request:

{
  "amount": "79900",
  "application_fee_amount": "0",
  "automatic_payment_methods": {
    "enabled": "true"
  },
  "confirm": "false",
  "currency": "usd",
  "customer": "cus_TRSxQnnDXJXTxE",
  "description": "Pro - 5 Stores Lifetime",
  "off_session": "false",
  "payment_method_options": {
    "card": {
      "mandate_options": {
        "amount": "199900",
        "amount_type": "maximum",
        "interval": "sporadic",
        "reference": "a894ef85-0824-49b1-b010-b4b439dff00f",
        "start_date": "1763500052",
        "supported_types": {
          "0": "india"
        }
      }
    }
  }
}

But we can't set setupFutureUsage to null on the client, so we are getting this:

image_4.png
sweet tiger
#

This is a slightly different problem. Since you're doing a deferred flow, the client options, and what is defined on the PaymentIntent must be the same

lapis sparrow
#

Ah, so we should explicitly pass setup_future_usage there to match the client, right?

#

Instead of passing nothing and it being null?

sweet tiger
#

yep, that's correct.In your case, if you are not saving the PaymentMethod for future usage, then I would just omit setup future usage altogether. I also wanted to mention that we are working on a fix, and it would likely be deployed in a couple of hours. So maybe it might be easier for you to rollback and wait?

lapis sparrow
#

Ah, this is fantastic! Alex, you are awesome

sweet tiger
#

I would actually suggest that you go about the rest of your day as per usual, cause I don't have an exact timeframe to share on when this will be fixed. By the time you wake up, this should already be fixed though.

lapis sparrow
#

Okay thank you!

inner fiberBOT
charred robin
#

Hi there! Stepping in for my colleague. This issue should be fixed now. Do test it again and let me know if you still face any issues with it.