#paymentplugins
1 messages · Page 1 of 1 (latest)
The Afterpay-hosted module I believe is handled exclusively by Afterpay, but I'd be happy to raise this with the product team as feedback to see if they can identify a solution
@agile zodiac thank you. Should I let the merchant know that at this time, that's all handled internally and there isn't anything we can do to alter that redirect url?
Want to make sure I have the correct messaging
Let me dig and make sure there isn't a workaround first. Will be right back
@agile zodiac thank you
Are you using Checkout? Or a custom payment flow?
All good. Let me dig a bit more before I send you to do that
Just as an update, I'm going to send to the product team to see if this is something they can look into as a permanent fix. What I'm trying to do now is see if we know anything about passing custom query parameters in the URL on a manual redirect to set the locale: https://stripe.com/docs/payments/afterpay-clearpay/accept-a-payment?platform=web&ui=API#handle-redirect
I'm not sure if that's info we have, but I'm phoning a friend to check anyway.
Ok thank you. We're using the stripe.confirmAfterpayClearpayPayment client side to trigger the redirect
Ah, yeah. So There isn't any workaround that I can think of. I'm happy to raise this with the product team. Like I said, that site is obviously not owned by Stripe, so there's no guarantee that we can do anything, but I'll check in anyway.
It might be worth contacting Afterpay to see if they have a novel idea for setting locale via URL query parameters (or similar), because it seems odd that they wouldn't just default to the browser's locale
@agile zodiac will do. I'll check with Afterpay. I image that locale in the url might be based on the Stripe account's registration country. Changing the url might lead to failed payments if Afterpay isn't accepting the locale. Thank you for your time