#himel_code

1 messages · Page 1 of 1 (latest)

wet hawkBOT
#

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

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

misty pawnBOT
#

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.

ionic ember
#

maybe my question got cut

#

If an invoice payment fails later, such as with an ACH debit, it might decline after 1 or 2 days. If it fails, will Stripe automatically attempt to charge the invoice again?
I have a few questions about attempt_count and status management:

  1. Statuses to Monitor: What specific statuses should be monitored? For instance, if an invoice fails, it should have something like "failed" or "attention"? When re-attempting the charge, what should the status be, and how can we consistently maintain it?
  2. Preventing Double Charges: If a re-attempt is in progress and the user tries to pay with another payment method, how can we prevent double charging or conflicts?
  3. Practical Use Case for attempt_count: What is the practical use case for attempt_count? How does it help in managing the payment process effectively?
wanton musk
ionic ember
#

I guess for standalone invoice stripe dont to retries?

wanton musk
#

What makes you say that?

ionic ember
#

i guess i am just confused with all these docs!

wanton musk
#

Smart retries work for one-off Invoices too, so don't worry about that part

ionic ember
#

If a re-attempt is in progress and the user tries to pay with another payment method, how can we prevent double charging or conflicts?

#

what's your thought on this?

#

is there any way for me to know re-attempting or retry is happning so i can show that to my user!

wanton musk
#

There's no double pay. Stripe doesn't retry payments on an Invoice that has already been paid

ionic ember
#

next_payment_attempt with this i can show in the UI when the next attemp will be made!

wanton musk
#

Yup

ionic ember
#

is there way to know no more retries will be made on this invoice!

wanton musk
#

You check the attempt_count and compare it to your Dashboard settings

ionic ember
#

another question regarding this same topic! we are actually building a invoice management sass app! we are using stripe connect! people will conect thier stripe accout create customer and invoice for them! now for connect user how re-tries actually work! is there any for me to know thier retries settings!

wanton musk
ionic ember
wanton musk
#

So are you using Direct Charges or Destination Charges?

wet hawkBOT
ionic ember
#

what happens when the invoice is paid it's added to his standard account! so he decide what he want to do!

wanton musk
#

That's not how that works. You (the platform) have to decide which charge type to use. You will need to know whether you intend to use Direct or Destination charges in order to understand how different things affect you and your Connect accounts. Certain settings are only applicable to Standard accounts with Direct charges, versus Standard accouns with Destination Charges

ionic ember
#

currently user create invoice and the clients of the user add thier payment method and pay the invoice! when it succeed the standard account show the payment success! what you call this flow?

#

maybe direct charge\

fleet cedar
#

Hello
Taking over as two-shoes needs to step away

#

Is your platform creating these invoices for these standard accounts? OR are they creating their own invoices using the dashboard?

ionic ember
#

our platform creating invoice like this const invoiceDraft = await stripe.invoices.create( { description: memo, customer: customer_id, payment_settings: { payment_method_types, }, metadata: { isFromApp: "true" }, }, { stripeAccount: stripe_connect_account_id } );

fleet cedar
#

That's direct charges

ionic ember
#

Okay that make sense

fleet cedar
#

Hmm retry settings are usually dashboard only. I don't think we reflect these on the account object anywhere

ionic ember
#

okay one last query! for ach debit! it stated that maximum two attempts would be made over the period of 14 days! question is it possible it customize like only 1 attempt or more 2 attempt! or it just hard coded 2

fleet cedar
#

It isn't customizable unfortunately.

ionic ember
#

that good 🤣

#

is it possible when no future retry will be made next_payment_attempt will be just null?