#k3davis

1 messages · Page 1 of 1 (latest)

upbeat plazaBOT
torpid tree
#

No, SetupIntents can automatically attach payment methods but attaching does not do anything automatic for setup intents

#

I am a bit unclear on your question. Can you tell me what API calls you are making here?

#

Also what is the end goal? Just to save a card I assume?

fast linden
#

req_YG7jkKLT8wz0hK - i'm attaching a payment method and getting a decline even though I haven't done any intent yet

#

i tried first to do the setupintent but that complained that the payment method wasn't attached, so I thought this step was necessary...

#

it is a test method that i expect to decline, to be clear. i just expected it to decline at the intent and not the attach

torpid tree
#

Gotcha, thanks for the info and request ID. Checking in to this...

#

Can you tell me more about the error that happened with the SetupIntent?

fast linden
#

Unfortunately no, I don't have a ready example on hand of that. If that's supposed to work I can try to reproduce it and ask a question about that instead

torpid tree
#

Also what test card number were you using? I think that may have just been a normal decline on the attach. When a card is attached to a customer it is validated so I think that is what happened there.

fast linden
#

I have a customer id and a payment method id that are unrelated to one another, and I should be able to do a setupintent with that combination?

torpid tree
#

SetupIntents are the current recommended way to save payment methods so I would recommend trying that again.

#

Not sure I understand your setup, so you have the PaymentMethod already and you want to create a SetupIntent for it?

fast linden
#

yes

#

is that unusual..? don't you need a payment method to perform a setupintent?

#

I believe I was using 4000000000000002

torpid tree
#

SetupIntents actually primarily exist to help make payment methods. Have you seen this doc on saving payment methods for future use? It is our current recommended flow if you are starting out
https://stripe.com/docs/payments/save-and-reuse

#

There are some scenarios where you will create a setup intent with an already existing payment method but those are mostly for things like creating a bank mandate after the first one expired. For simply saving payment method details with a PaymentMethod object, we recommend using SetupIntents

fast linden
#

alright, I will look more closely at the docs, I guess I misunderstood some things. thank you.

torpid tree
#

No worries, definitely get that confusion. Just let us know if you run in to any other questions

opal lily
#

👋 @fast linden

fast linden
#

hi, thanks orakaro

#

pompey said above that setupintents were the main way of creating payments. After a closer look I don't see how I can use it this way in my context where the setup intents are "moto" and I have to confirm when the setupintent is created, it seems like I have to create the payment method first in that case. Am I misunderstanding?

opal lily
#

I think my colleague advised not based on the assumption you are using moto. Moto is a private beta feature and we shouldn't talk here really. I would recommend open an email conversation with Support when you can authenticate your account

#

A quick answer, you can create and confirm a SetupIntent immediately with moto and the card information in 1 call

fast linden
#

OK, it's impossible to tell the way your docs are structured which features are delivered and which are private betas. That's frustrating. I can interact with support instead, though I'm curious about your last statement as there doesn't seem to be a card option in payment method data in setup options, only bank account (and others)

#

I understand you shouldn't discuss here so I can follow up with support. My apologies.