#Mahesh
1 messages · Page 1 of 1 (latest)
hello! can you share the relevant code snippets as to how you're implementing the Payment Element? Also, at which point/line of your code are you getting that error?
i have observed this two scenario
- when the connected stripe account has atleast one capability enabled, then everything is working as expected.
- when the connected stripe account don't have any capabilities enabled or incomplete stripe setup, then the custuomer paid using a other payment methods like Paypal etc., then on redirecting to next confirmation page we are getting this error.
we are following this documentation approach: https://stripe.com/docs/payments/accept-a-payment-deferred?platform=web
if you want to access the live site, its available here: https://qadubai106.1prod.one/#!/
are you initializing stripe like this client-side?
var stripe = Stripe('{{PLATFORM_PUBLISHABLE_KEY}}', {
stripeAccount: '{{CONNECTED_STRIPE_ACCOUNT_ID}}',
});
const { loadStripe } = await import('@stripe/stripe-js');
const stripePromise = loadStripe(checkoutSettings.stripePublishableKey, {
betas: ['mobilepay_pm_beta_1'],
});
<Elements
stripe={stripePromise}
options={{
mode: 'payment',
amount: 100000,
currency: 'EUR',
paymentMethodTypes: Array_Of_Methods or emptry Array,
}}
></Elements>
like this
I'm quite confused here, what has this got to do with the connected account?
you're using your platform's publishable key in your code right?
we use connected account stripe_publishable_key in client side right?
you should follow this if you're making API calls on behalf of your connected accounts - https://stripe.com/docs/connect/authentication
anyway, that may not be the issue, it's just an observation
Can you share the code where you're submitting/confirming the payment frontend? Also, is the link you provided using the live or test Stripe keys? If it's using the test Stripe keys, can you provide step by step instructions on how to replicate the issue?