#precious-void_best-practices

1 messages · Page 1 of 1 (latest)

hard roostBOT
#

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

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

small merlin
#

I'm really not too familiar with this though, and especially not from the Issuing POV

hard roostBOT
umbral root
#

Thanks for a quick reply!
As far as I understand, though, the balance availability is somehow managed by the stripe issuing, that's an even more interesting case, when talking about spending controls... So predictability of available for use assets is pretty crucial.

Also how and does the stripe limits the possible amount for capture for the authorization?

Is there sm1 who has a deeper knowledge on Issuing part that could assist here? Thanks in advance 🙂

valid thicket
umbral root
#

So merchant can't really charge more than authorized amount, right? (Except for the force captures)

As for the charges less than authorized amount, same questions still remain.

valid thicket
umbral root
#

Hmm, got it, thanks!
And as for the initial question about multi-capture and status of the authorization?

In case of 50$ authorized and 30$ was captured. What I'm seeing now is that all the 50$ hold is released before this capture.
Does this mean that after 50$ release and 30$ capture cardholder can use the rest of the 20$ and they are not held?

There is no way to know that the merchant is going to charge the rest of the amount (20$)?
What happens if he doesn't charge them? Will the authorization for them somehow expire?

valid thicket
#

Do you have a specific example object ID you can share?

umbral root
#

I have an example of multi-capture authorization.
It's not a perfect example, because two captures were received within a minute.

This is the authorization event: evt_1PQDe4Q27n4twfFZfAQuNJAR

Which later got two captures.
So – two issuing_authorization.updated events:

  1. evt_1PQf1FQ27n4twfFZuiv0Emd1
  2. evt_1PQf1HQ27n4twfFZJv08yo5P

Already after the first event authorization was closed and in balance_transactions you could see that the whole authorized and held amount is released due to capture.

#

Maybe it's expected based on the docs, but logically it isn't really.

  1. 50$ is authorized and held
  2. Only 30$ is captured (probably, another 20$ will be captured in the future), why would the whole 50$ released?
valid thicket
#

Let me look at those examples

#

I'm struggling to establish the differences between the two events

#

I guess I want to know how you're understanding this authorization was created by the merchant with multi-capture in mind?

#

OK, I see the multi transactions now

fluid quarry
#

hi! I'm taking over this thread. looking into this...

#

Maybe it's expected based on the docs, but logically it isn't really.
yes I agree it's a bit odd, but not sure if that's expected or not. I would recommend to ask your question to Stripe support directly, where they will have more time to investigate: https://support.stripe.com/contact