#paymentplugins

1 messages · Page 1 of 1 (latest)

stoic coralBOT
agile zodiac
#

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

hidden fossil
#

@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

agile zodiac
#

Let me dig and make sure there isn't a workaround first. Will be right back

hidden fossil
#

@agile zodiac thank you

agile zodiac
#

Are you using Checkout? Or a custom payment flow?

hidden fossil
#

A custom payment flow

#

I can send you some logs if that helps

agile zodiac
#

All good. Let me dig a bit more before I send you to do that

hidden fossil
#

Ok thank you. We're using the stripe.confirmAfterpayClearpayPayment client side to trigger the redirect

agile zodiac
#

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

hidden fossil
#

@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