#shashankbk
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Let's chat here
Hello, sure.
So here is the payment intent ID: pi_3LypWiCh0aVQteBp15u41LXc_secret_620X91XGlLd2iOws8BYbhirK0
We are trying to bring up the payment sheet - we are using Expo 46, afterpay is enabled as a payment method in the dashboard.
When we use expo app this is what we see on the payment sheet.
No afterpay as you can see.
But when we use the same payment intent ID to pull up a payment sheet on a web app (not using expo) we can see afterpay
One of the suggestions made last time was to try this on expo 46 (as we were on expo 45) to see if this might fix the issue, but it has not.
This is the code that is used to bring up the payment sheet.
const { error } = await initPaymentSheet({
googlePay:true,
testEnv:true,
applePay:true,
paymentIntentClientSecret:"pi_3LypWiCh0aVQteBp15u41LXc_secret_620X91XGlLd2iOws8BYbhirK0",
merchantDisplayName:"Stripe",
merchantIdentifier:'merchant.com.communitiapp'
});
if (!error) {
}
};
any ideas on how to proceed here ? This has been an issue for several months for us.
Taking a look, expo is known to cause issues testing different payment methods ๐
Let me see what I can dig up
Yes please, thank you.
How exactly are you testing the App on the device?
Are you creating an EAS build or just using expo go?
EAS build.
Yes it was the same on IOS as well.
Okay. yeah I'm running out of ideas on this one.
Do you already have a ticket about this with us? If not, I'd recommend sending an email to support@stripe.com with as much as details that you can provide.
Don't have a ticket on this.
Okay so add all this information in an email and send it to support@stripe.com ?
Lets say we did end up doing this, any ideas on how long it would take to resolve?
Hi ๐
@haughty knoll had to step away but the best way to get support on this issue is to send in the email as mentioned earlier. Unfortunately we cannot give you an ETA on resolution until we dig into it more thoroughly
Okay sounds good. I'll send the email shortly. Thanks.