#elppypy_api

1 messages · Page 1 of 1 (latest)

deft vaultBOT
#

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

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

sterile plankBOT
toxic osprey
#

Hi there 👋

I didn't see a question in your post, so I want to start by making sure I'm understanding what you're asking. You're trying to figure out how to verify an ACH payment method without using a Setup Intent?

If so, I'll have to do some digging. I think typically that isn't possible, but I'm going to look to see if this is something I'd found a workaround for previously.

Did the migration team provide you with any such object or guide for testing these processes? (since their migrations do things typically not possible with the API, so there isn't always a way to replicate those outcomes)

scarlet warren
#

.

#

You're trying to figure out how to verify an ACH payment method without using a Setup Intent?
Yes, because I expect the migration to finish and we would have customers with the payment methods already

Did the migration team provide you with any such object or guide for testing these processes?
No, this is a post migration step. I'm trying to replicate what would happen afterwards because we had problems with a previous migration with customers having failed payments because of it

#

I could reach to the migration support again, but usually that channel takes a bit of time to get a response. I figured asking here directly would be a faster feedback

toxic osprey
#

And why is using a Setup Intent to attach them not sufficient?

I dug back through my old threads on this topic to confirm, and there isn't a way to do the microdeposit verification for us_bank_account Payment Methods without using an intent.

scarlet warren
#

I'm trying to replicate the scenario post migration, I imagine the migration team won't creat a setup intent but instead only import customer and payment_method data

toxic osprey
#

I don't know how they set those up. If you want to test the state that the migrations team will leave you with, I'd suggest you first align with them and ensure you understand what that state will be.

scarlet warren
#

Got it

#

Another question, still on this topic

#

Do setup intents with ACH automatically start a verification uppon creation?

toxic osprey
#

No, upon confirmation.

scarlet warren
#

Considering that we should have all customers with the verified payment methods, how should this setup intent be created?

#

No, upon confirmation.
You mean if I set "confirm" to false users won't be notified and the setup intent will work normally to charge subscriptions?

toxic osprey
#

What is the point of the Setup Intent, if you have an already set up and verified Payment Method? What are you trying to accomplish?

You mean if I set "confirm" to false users won't be notified and the setup intent will work normally to charge subscriptions?
Not at all. If you set confirm to false when creating the Setup Intent, and never confirm it later, then the intent does nothing. Setup Intents don't create Subscriptions, so I'm not sure I understand the mention of subscriptions there.

scarlet warren
#

The subscription creation would come afterwards

#

If you set confirm to false when creating the Setup Intent, and never confirm it later, then the intent does nothing
But if I confirm, the users will be prompted to verify the payment_method again?

#

If so, I'd need to reach out to the migration support team and try to clarify this further. We are supposed to get customers with the payment_method verified, but this will still be a problem if we must confirm the setup intent and notify users to verify again

#

Unless there's another way to save a payment method and charge subscriptions without relying on setup intents

toxic osprey
#

But if I confirm, the users will be prompted to verify the payment_method again?
I'm not sure offhand. I'd suggest running the Payment Method that you used a Setup Intent to verify earlier through another Setup Intent and see what the outcome there is.

Setup Intents are designed for creating Payment Methods and setting them up for future usage. If you're being provided already set up Payment Methods by the migration, then you can just start using them.

I'd strongly recommend confirming with the migrations team what state the Payment Methods they will provide you with will be in. I'm not sure what exactly that state is, so I'm not sure what path would be best for what you're trying to accomplish.

scarlet warren
#

I'll reach out to them for more clarification

#

But I might as well have the wrong perspective on the subscription part

#

We don't need to have a setup intent for that at all? I imagined this would be necessary because subscriptions have a recurrent charge(in the future)

toxic osprey
#

If you have an already set up payment method, then you don't need a Setup Intent when creating a Subscription.

You'll either set that Payment Method as the default PM at the Customer object level (in invoice_settings.default_payment_method):
https://docs.stripe.com/api/customers/update#update_customer-invoice_settings-default_payment_method
Or set it as the default_payment_method at the Subscription level:
https://docs.stripe.com/api/subscriptions/create#create_subscription-default_payment_method

#

If you need to set up a payment method, becaue you don't have one currently set up, then you may need a Setup Intent. Though Subscription's will generate a Setup Intent if their first Invoice is a $0 Invoice (such as with a trial period):
https://docs.stripe.com/api/subscriptions/object#subscription_object-pending_setup_intent

Or if the first Invoice is paid and requires a Payment Method, then its Payment Intent will automatically use setup_future_usage correctly, and you can use that Payment Intent to collect payment method details and process the first payment.

scarlet warren
#

Though Subscription's will generate a Setup Intent if their first Invoice is a $0 Invoice (such as with a trial period):
We do have a trial period, in this case a setup_intent would be automatically created and therefore users would need to verify again?

toxic osprey
#

Nope, not if the payment method is already set up

#

Then you can just ignore the pending_setup_intent

scarlet warren
#

Got it

#

I'll follow up with the migration team as well

#

But good to know the setup intents are not necessary

#

thanks very much!

toxic osprey
#

Any time!