#jared_unexpected
placid patrolBOT
đź‘‹ Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1315720459999907922
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
foggy cave
Rejection message "Your application is using a Google Pay branded payment button but has not implemented the PayButton API to render it."
placid patrolBOT
subtle narwhal
Hello! We can't really help with a rejection from Google, we can only help with the Stripe side of things. Did they provide any details beyond that?
foggy cave
Howdy,
Unfortunately not...
Full message:
Subhani googlepay-api-support@google.com
7 Dec 2024, 01:31 (2 days ago)
to me, googlepay-api-support@google.com
Hi,
We have an update on your recent Google Pay API integration submission.
We need more information about com.gorillasoftware.portforwarder:
Your application is using a Google Pay branded payment button but has not implemented the PayButton API to render it. Please follow the instructions in the provided link to update your integration to use the PayButton API.
The PayButton API is now a requirement when using a Google Pay branded payment button. The API ensures:
The button stays consistent across all of our partners’ applications
The button stays up to date with the latest Google Pay branding
The button displays properly across device sizes and applications
Text on the button is localized to the user’s device settings
Once completed, re-submit your integration again through Google Pay & Wallet Console. If the above feedback cannot be implemented because you are using a dedicated sdk solution provided by your Payment Service Provider or some other reason, please reach out to us by responding to this email.
Thank you for submitting your integration through the Google Pay & Wallet Console. It’s been a pleasure working with you.
Q: Does the Mobile Payment Element use the PayButton API to render the Google Pay button?
subtle narwhal
Yep, it does, which is why I'm confused. See here: https://github.com/stripe/stripe-android/blob/0eb1931d7f24696c2d70d2bcfe2646916586009c/paymentsheet/src/main/java/com/stripe/android/paymentsheet/ui/GooglePayButton.kt
foggy cave
Lol OK - thanks for the link.
I'll take this link to them and see if that's acceptable.
Super strange that they rejected the integration in that case!
subtle narwhal
Maybe there was a misunderstanding or miscommunication at some point? I think reaching out to them for clarification is your next step. 🙂
foggy cave
https://developers.google.com/pay/api/android/guides/resources/pay-button-api
Is it using the actual 'com.google.android.gms.wallet.button.PayButton' however?
subtle narwhal