#jbin_api

1 messages · Page 1 of 1 (latest)

frail fogBOT
#

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

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

marsh breach
#

Hi, are you asking if we have a way to test 'pending' status with various payment methods?

vapid fossil
#

Yes exactly - in particular with SEPA. And if that's not possible, I'd like some clarity on the behavior so I can at least test this properly with mocking on my end

#

And we're creating these via the SetupIntent API (not the PaymentIntent API)

marsh breach
#

Have you attempted this?

vapid fossil
#

Yes I've tried a number of the test accounts listed there but they all immediately transition to the success status. I see the docs explicitly state these work for PaymentIntent, so I'm wondering if they don't work for me b/c I'm using SetupIntent.

#

The related request ID that I attached to the original message is for one of these calls

marsh breach
#

I see your point, let me further look

#

Yeah, from testing it works with PaymentIntent but not with SetupIntent.

#

I will share your feedback to add a test number that works for SetupIntents.

#

Is there a question behind the question here?

vapid fossil
#

Okay thanks for confirming. So 2 questions:

  1. Does that mean there's not possible way to test this without real cards?
  2. From the original question - I want to list these "pending" setup intent payment methods via my API and return the same sort of structure that is returned by the payment method list endpoint. I see there's a "payment_method" field returned - will that be present after adding a SEPA card that enters pending? And will it point to a real payment method that I can retrieve?
frail fogBOT
marsh breach
#

We do not recommend testing with real data, but I'm happy to answer questions depening on what you're looking to achieve

#

On your second question, what do you mean by 'return the same sort of structure that is returned by the payment method list endpoint.'? What do you want to use that for?

vapid fossil
#

I have an API endpoint to list payment methods (currently just pulled via "stripeClient.customers.listPaymentMethods". I want to augment this list with any pending payment methods so we can show them in the UI. To acheive this I'm trying to fetch pending SetupIntents via stripeClient.setupIntents.list but ultimately I want to grab the associated PaymentMethod object from that response

#

So I'm wonder if, for SEPA methods that take days to process, will the SetupIntent.payment_method field have the same shape as the stripeClient.customers.listPaymentMethods endpoint (if I expand it) for "pending" setup intents

vapid fossil
hard pulsar
#

Hi there 👋 jumping in as my teammate needs to step away.

#

Are you asking about this because you've had problems in livemode around this flow?

I'm trying to build a context of what is going on, and one thing I'm noticing is that we show that a Payment Intent is expected to go into a processing state in our SEPA payments guide:
https://docs.stripe.com/payments/sepa-debit/accept-a-payment?web-or-mobile=web&payment-ui=elements#web-confirm-success
but I'm not seeing the same for just saving bank details via a Setup Intent:
https://docs.stripe.com/payments/sepa-debit/set-up-payment?platform=web&payment-ui=elements#web-submit-payment-method

vapid fossil
#

I'm trying to test in test mode at the moment as we're still building out the API. The blocker I'm encountering is that the test cards for SEPA work for entering the pending state for PaymentIntent, but the same account numbers go directly into succeeded state for SetupIntent

hard pulsar
#

I just found confirmation internally that Setup Intents are not expected to go into a processing state for SEPA Payment Methods. They should either immediately succeed, or return a relevant error, unlike Payment Intents.

vapid fossil
hard pulsar
#

I'm not readily spotting an example of a payment method type that has Setup Intents that can go into a processing state, but I'm hesitant to say there isn't one

vapid fossil
#

Okay great thank you - that’s very helpful information. Is any of this documented somewhere? I know the “how setupintents work” document which implies it can happen, so I just want to make sure I do all due diligence before placing this feature in front of users

hard pulsar
#

I was finding most of the context I've been sharing in our payment method specific guides for saving them for future usage (like the docs I've linked above). I don't think there is a consolidated place where we list all of this, and it's worth remembering that not all payment method types support being setup for future usage.

Thankfully, we do have a good doc for seeing which ones don't support being setup:
https://docs.stripe.com/payments/payment-methods/payment-method-support#additional-api-supportability