Hi,
We're experiencing an issue where our clients are being charged multiple times because our system returns errors after a payment is completed from the browser. We'd like to switch to completing payments from our server instead to prevent this from happening.
We tried implementing the beta feature described here: https://stripe.com/docs/payments/finalize-payments-on-the-server?type=payment. However, we encountered an error that says "Unhandled payment Element loaderror: error: { type: 'unexpected', message: 'Account acct_xxxxxxxxxx not gated into deferred intent behavior' }". We're not sure how to resolve this.
As a second approach, we're thinking of authorizing the payment without capturing the funds on the client side, and then handling the capture from our server. Do you think this is an acceptable approach? Are we not falling into an anti-pattern?
and
.