#Baptiste
1 messages · Page 1 of 1 (latest)
Hi, it looks like you'd want to reach out to our support team on your deferred intent behavior gate error. Our support team will be able to assist you better than I can: https://support.stripe.com/contact
On your second point, are you referring this, https://stripe.com/docs/payments/place-a-hold-on-a-payment-method ?
For the second point, yes that's correct
Depending on your use case you can but please know that it has limitations as documented here: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#auth-capture-limitations. In most cases, you need to capture funds within 7 days. However, I think writing in to support and inquiring about the gate error would be much better given that you would immediately capture instead of waiting for some time to capture.
Do you know if / how we can reduce the capture expiry to an hour or any specific value?
You can capture anytime before the expiry but with your business use case I recommend the deferred intent option.
I mean, can we set the default expiry value to something different than 7 days?
No
Just to confirm, by deferred intent you're referring to this beta feature correct? https://stripe.com/docs/payments/finalize-payments-on-the-server?type=payment
Yes, just looking at your message earlier and the error code
Cool yea in our case we intend on:
- only using for CC payment
- Always capturing within a few seconds
Given the capture_method approach fits more closely with our current implementation (which is already live) we are thinking to go with that
I guess we'll just need to make sure to keep track of any opened intents and be sure to cancel them ourselfs asap, but if we miss any then your system will always catch it within 7 days
Sorry just final check given the caveats we / you have shared you dont see any problems with this?
The third pair of eyes here is very much appreciated
Like I said, I do not recommend it as you're capturing the funds right away. Your business use case does not fit with the path. Therefore, I keep asking you to reach out to support to look into 'gated into deferred intent behavior'. You seem to thing there is an issue, what are your concerns?
Its really just that we can see more work required on our end to make that path work
and there is a little uncertainty given this is in beta status
If you think it better suits your business and you're not concerned about the limitations shared above, sure!