#nicolas-fernandez-falco_api

1 messages ยท Page 1 of 1 (latest)

somber kilnBOT
thin tideBOT
#

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.

somber kilnBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255228755920552070

๐Ÿ“ Have more to share? Add details, code, screenshots, videos, etc. below.

austere nexus
coarse patio
#

Yes, I understand that. I have couple of questions

#

Like how creating a payment intent will impact the payout? Because a customer could pay multiple invoices and some of them might have the fastes speed selected and the others the standard one. So I'm trying to understand what's for that setting

austere nexus
#

Sorry, which setting are you referring to? Can you provide a link?

coarse patio
#

I thought it was more in terms that if a customer pay an invoice with ACH the amount of days it takes to process that payments generally is 4-5 days. If I create that payment intent with fastes I thought that the amount of days is improved. In our case our account has been approved for T+2

austere nexus
#

Okay, so what's your question about this?

coarse patio
#

Maybe it is that yes. What I sent to you related to the payment intents is how you configure the ach debit timing right?

#

I'm trying to understand what would be the impact of that setting I shared to you

#

Trying to make sure I'm making the correct change

austere nexus
#

The impact is what it says; it changes the settlement speed if your account is eligible. I'm not sure if this is the correct thing for you to do or not because I don't know what your goal is.

coarse patio
#

Okay I get your point. Our account has been approved for T+2. So I'm trying to use that. So I'm trying to confirm with you that If I create a payment intent with payment_method_options.us_bank_account.preferred_settlement_speed = "fastest" it will use T+2 and if I set that to "standard" it will use our regular T+4

austere nexus
#

That's how it should work if your account is approved, yes.

somber kilnBOT
coarse patio
#

Cool. Now I have two other questions

#

1- Where I should view those settings in my account?

#

If I go to developers -> payment methods ACH DIrect Debit it's not even turn ON but our customers use that

#

So I'm trying to understand how that's possible also Bank Transfers

glass crag
#

Hello
Looking at one of the PaymentIntent you've shared above, you're sending us_bank_account as a PaymentMethod type

coarse patio
#

Agree

#

That's why I'm asking all these questions. I think I'm not understanding the big picture

glass crag
#

I don't think I fully grasp what you're asking. Your earlier ask for about settlement timing. Then later you asked about how ACH debit was being shown as a PaymentMethod.

Just trying to be on the same page ๐Ÿ™‚ What's your outstanding ask? What part are you not clear on?

coarse patio
#

Is it possible to make a huddle or something similar? I think it would be easier to explain

glass crag
#

Unfortunately, not. But feel free to take your time to summarise.

coarse patio
#

Okay.

#

So let me explain again.

#

The problem we have is that today, when our customer/clients when pay an invoice (using payment intents with US bank account) the time it takes once the customer pays the invoice and we actually receive the money through the succeeded event takes generally 4-5 days. Our account has been approved to use T+2. T+2 have a cost so we don't want to offer this feature to all the invoices. We defined a thresshold to determine if we will create a payment intent using T+2 or not.

T+2 should improve our problem since the amount of days since the client pays the invoice and we actually receive the money should be less.

Now, I'm trying to understand if the parameter/setting I sent to you (payment_method_options.us_bank_account.preferred_settlement_speed) it's the correct one and make sure it will do what I'm expecting to do.

glass crag
#

When you say invoices though

coarse patio
#

Yes, sorry I already edit the orignal message

glass crag
#

are you creating invoices by using Invoice API or are you generating your own invoices and using PaymentIntent for payments?

coarse patio
#

When I refer to invoices It's invoices from our side. It's just Payment Intents from Stripe side

#

So to summarize if a Customer pays a payment intent with bank account and I have created that payment intent using the settlment speed = fastest (in case our account has the T+2 approved) that payment intents should be proccesed in two days aprrox right? That should be the time between the processing and succeeded event right?

glass crag
#

Correct

coarse patio
#

Cool.

#

Now, where I;m supposed to find those settings? The T+4, T+2?

#

I want to make sure that our default is T+4 and only use T+2 when the "fastest" parameter is sent

glass crag
#

I think for that, you'd need to enable ACH Debit from dashboard & set a default settlement speed.

coarse patio
#

Okay that's why I asked earlier how it's possible that our customer are paying using US Bank Account and we don't have ACH Debit enabled

glass crag
#

The setting for settlement configuration is under ACH Debit payment method capability.

Generally, folks rely on automatic_payment_methods parameter and use the dashboard to control the payment methods presented. But you're not using that parameter.

Instead you're passing payment_method_types explicitly when making the API request which is similar to manually enabling that payment method for this specific PaymentIntent

#

When you manually pass the payment_method_types (without configuring settlement timing via the dashboard or set preferred_settlement_speed in the API), I believe we default to T+4 settlement timing

#

does that clarify?

coarse patio
#

Cool. Yes, that makes a lot of sense. Enabling the ACH Direct Debit in the Dashboard shouldn't impact at all right? I've tried doing that in the testing environment and I was abel to see the settlement speed configuration

glass crag
#

yup should be fine

coarse patio
#

Before enabling the feature, a modal appeard suggesting to enable webhooks. We rely on Payment Intents events. That's correct right? Like created, processing, succeeded, failed

glass crag
#

yup, since ACH debit is delayed notification payment method - it may take a few days to succeed/fail

#

Listening to webhook events would notify you when it does that

coarse patio
#

Agree. So we are good. Now If I understood you correct. Enabling or not the ACH Direct Debit wouldn't affect since I'm establishing those configurations each time I;m creating a payment intent

glass crag
#

correct

coarse patio
#

Cool. Now I'm having a better understanding and make sense. It was really weird to me go to the dashboard and see Bank transsfer, ACH DIrect Debit disable since I know our customers are ussing those payment methods haha

#

Now last question. How would it be possible to test the settlement speed in the testing environment? Any suggestion? In the testing environment of course that delay of processing it's not 4-5 days. The succeeded event is triggered a couple of seconds after the processing event. So I'm not sure If I'm gonna be able to test this beside of making sure that the correct parameter is sent in the payment intent

glass crag
#

I don't think you'd be able to test this in test mode, no.

coarse patio
#

Okay. I will make the changes under a feature flag just in case and that's it

#

Well, really appreciate your help and sorry if I didn't explain my self correct from the begining

glass crag
#

All good! Happy to help ๐Ÿ™‚
Good luck

coarse patio
#

Have a good one!