#harcon_api

1 messages ¡ Page 1 of 1 (latest)

autumn flaxBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

swift kayak
#

The only other reference I have to off_session is in the features object

    const customerSession = await stripeLts.customerSessions.create({
      customer: customerId,
      components: {
        payment_element: {
          enabled: true,
          features: {
            payment_method_redisplay: 'enabled',
            payment_method_save: 'enabled',
            payment_method_save_usage: 'off_session',
            payment_method_remove: 'enabled',
          },
        },
      },
    });
#

but I also have that on the payment intent creation and that seems to be working as expected

analog tundra
#

Can you share a payment method id where this happened?

swift kayak
#

seti_1QDnmxGyjGYV1j4Z1ZdT2eJd

analog tundra
#

That's a setupintent that requires payment method

#

I mean can you share a payment method id that is being redisplayed?

#

One where you didn't expect it to be redisplayed?

swift kayak
#

Sorry read wrong my bad

#

one moment

#

pm_1QDo1lGyjGYV1j4Z1vNVH6ij

analog tundra
#

Oh ok this is a setupintent

#

SetupIntents always set up future usage

swift kayak
#

okay, the payment element doesn't say that anywhere - should I add a disclaimer?

analog tundra
#

What are you using a setupintent for?

#

That's the entire purpose of a setupintent

swift kayak
#

we have a system in our app whereby a users first reservation is given credit, the price is determined on our back end based on a users credit so reservations can sometimes be $0

#

and a payment intent can't be $0

#

I understand now it's not the best way of doing it because if it's a $0 payment technically no payment method should be required

#

but we ask for payment details so future payment intents can be confirmed easily

analog tundra
#

If you need payment method anyway for future payments

#

You'd want to save it

#

I think you probably just need a disclaimer then for that

swift kayak
#

The problem is that the Payment element displays a checkbox giving users the illusion of choice, but I'm guessing that can be turned off in features right?

analog tundra
#

Yes exactly

#

That's what that config is for

swift kayak
#

I guess I just needed to rubber duck this problem my apologies - wasn't exactly aware of the fact that setup intents always save payment methods

#

the docs can be confusing sometimes

#

thanks for your help all the same

analog tundra
#

No worries