#madison-k-_best-practices

1 messages ¡ Page 1 of 1 (latest)

round whaleBOT
#

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

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

cyan root
#

Add'l context --

We are creating a payment intent for a customer and automatic reconciliation is enabled.

Should that customer provide an amount to customer balance that doesn't fully satisfy the payment intent, automatic reconciliation still applies the customer balance to the intent and the intent enters a state of requires_action.

We would like to be able to capture the intent despite its full amount not being met.

We considered canceling the original intent and creating two new intents -- one for the amount applied and one for the difference -- but we are concerned about a few things:

  1. Canceling the original intent will return the monies applied to customer balance. How can we guarantee that they will be applied correctly to the new payment intent created instead of some other payment intent that was created separately?
  2. Canceling and recreating "resets" the clock on things like automatic timeouts, cancelations, etc.
worn schooner
#

Are you using Invoices too?

cyan root
#

We are not.

worn schooner
#

I don't think you can do what you want to do with Payment Intents. You could with Invoices - that's pretty much what they're designed for.

round whaleBOT