#xiaowo_unexpected

1 messages ¡ Page 1 of 1 (latest)

ruby kilnBOT
neon whaleBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

ruby kilnBOT
#

👋 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/1242772213770485810

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

slow marsh
#

Hi, I am not sure what's your question exactly

dull basin
#

when we user google pay, and this error show up

#

We tested Apple Pay two days ago and it was successful. But I failed to test goole pay today. Firstly, I would like to know the reason for this prompt? And then I want to know how to solve it

slow marsh
#

How are you integrating Google Pay?

dull basin
#

we use this document to intergrating

#

If the Google account we are using does not have Google Pay enabled, will it cause the screenshot to appear?

slow marsh
#

Do you see the Mobile Payment Element before this error pops up?

dull basin
slow marsh
#

I don't see Google Pay here at all, how do you access it?

dull basin
#

Wait a moment, I'll have my colleague redo the screen recording process

#

I have another question that I would like to inquire about:
We are currently finding an urgent issue when calling payments.
The problem is as follows: when the current user pays online, the first payment saves the credit card information and completes the payment; the second payment has to fill in the credit card information again.
That is, users need to fill in the credit card information again every time they pay, which is very troublesome!
Is there any way to do this without having to refill the credit card every time the call is made?

still phoenix
#

hi! I'm taking over this thread.

dull basin
#

Thank you very much! We have two more questions, please do help!

  1. We would like to use secret-free payments, and all current payments require the user to click on consent. Is it possible for the user to authorize us in advance to pay within a certain amount without the user having to agree again?
  2. We would like to use the subscription model, i.e. monthly payment membership. However, we may have multiple monthly subscriptions for one app and one user at the same time, is it possible to support this?

Translated with DeepL.com (free version)

still phoenix
#

I'm sorry I don't understand your questions. can you share more details?

dull basin
#

Question 1: We would like the user to authorize the app to initiate a chargeback within a certain amount without the user's consent again.
Question 2: We would like users to be able to pay by monthly subscription, and after paying $29.9 on May 21, 2024, the payment will be deducted automatically in the following month.