#s0__0-pm-order-creating-PI

1 messages · Page 1 of 1 (latest)

torpid bolt
#

Hello 👋
Not sure I follow.
Can you give me an example?

jagged pawn
#

i see paymentMethodOrder in the DOC

#

but not sure where to set it

torpid bolt
#

can you share the link?

torpid bolt
#

ah sorry I meant the link to the doc

torpid bolt
#

Yeah I think you're looking at the wrong docs.
This is for client-side library

#

When you create a PaymentElement

#

It isn't relevant for a PaymentIntent

jagged pawn
#

in PaymentIntent, can i hide some payment method?

torpid bolt
jagged pawn
#

i pay by google pay when i go live

#

however it didnt go to return_url that i have set

#

it just stays on the card form

torpid bolt
#

Are you seeing any errors in your console?

jagged pawn
torpid bolt
#

Seems like your google pay payment is failing?

jagged pawn
#

my card is paid, have a sms

#

and it is all right in test mode @@

#

i cant test too much time in live mode

#

this is 400 too @@

#

this is not issue about .htaccess, because i del all content inside it, still 400/403

torpid bolt
#

Let me check something quickly

#

do you have a PaymentIntent ID for this?

jagged pawn
#

pi_3Klb5bGRGdCFkMmo3N513Ozq

torpid bolt
#

can you share the full screenshot of the error?

jagged pawn
#

this is capture in live mode

#

same url

earnest granite
#

Hi there! @torpid bolt had to step away. Give me a moment to catch up....

#

Am I understanding correctly that you are seeing this error after you complete the Google Pay modal?

jagged pawn
#

wanna see why same url with diff device, mobile has that error

#
  1. F5, error shown, didnt press anything
  2. live mode, pay by google pay, no redirect to return_url
#

I am having these two problems

jagged pawn
#

hello?

thick kiln
#

@jagged pawn Hello - I'm also hopping in to help. Sorry I was catching up

jagged pawn
#

please visit this in mobile, to see if same error occur @@

thick kiln
#

I don't see the same error on my device

#
  1. F5, error shown, didnt press anything
    On the device that does show the error, are you able to continue on with Google Pay, or do you just get more errors?
jagged pawn
#

i can pay by Google Pay, but after that , no redirect to my return_url

#

the result is , just staying in the same page

thick kiln
#

You're only seeing the redirect not work on the device with errors right? Not the device without errors?

jagged pawn
#

i have only one mobile, however, in test mode, all things work fine

thick kiln
#

What kind of device is it again? And when you go through the flow on mobile can you show me what your networks tab looks like

jagged pawn
#

s20 ultra

thick kiln
#

Gotcha - and let me know when you have more details on what the failing requests look like

jagged pawn
#

after i paid in live, the three-row-error occur again

#

my card is charged, db is recorded paid, product is sent too

#

if i refresh this page , this will become "this bill is paid"

thick kiln
#

Is there anything different about your wifi setup for your mobile device and the device that isn't seeing errors?

jagged pawn
#

it is in the same wifi

thick kiln
#

and can you share the Payment Intent ID?

jagged pawn
#

pi_3Klc5BGRGdCFkMmo2IoP2MK2

thick kiln
#

That Payment Intent hasn't been paid - so something is wrong on your code if refreshing the page shows "this bill is paid"

jagged pawn
#

also, in this device, when i tab card number feild, some saved card number will appear. After i type CVC, it supposes to help me fill in the card num but it didn't

thick kiln
#

Let's focus on one problem at a time - when we get past this google pay error we can move on to the autofilling one

jagged pawn
#

oh sorry u should check this
pi_3KlbwBGRGdCFkMmo2gakslXZ

#

as i refresh the billing page, the payment intent will refresh

#

should i turn to test mode and try those google pay again?

#

i find a old mobile , this time i pay with typing card number, not google pay. after paying, no redirect again

thick kiln
#

So you're seeing these redirect issues just across the board, right? It's not limited to google pay?

jagged pawn
#

yes, no redirect at all

thick kiln
#

Yes, but ignoring those errors for a minute (I don't think they're affecting your ability to actually pay with google pay, so I want to narrow in on what the actual issue is)

jagged pawn
#

is it the reason?

thick kiln
#

Ah, yup that's definitely the reason.

jagged pawn
#

i add this because of wechat QR code

#

i want to close the QR code with no redirect

thick kiln
#

Is your goal to always do the redirect? If so, you need to change it to redirect: always. We don't redirect for card/digital wallet payments if you have redirect: if_required.

jagged pawn
#

sorry for that stupid question

#

yes! i want redirect always, but not closing the wechat qrcode

thick kiln
#

There isn't a way to conditionally specify which payment methods you want the redirect to happen for. If you set redirect: always then we will do the redirect for wechat pay after you click the "exit" button on the qr code

jagged pawn
#

so for the best, i should leave it alone, with closing QR code , redirect

thick kiln
#

yes, i would be best to just always redirect

thick kiln
#

You're referring to chrome autofilling the credit card information, correct?

jagged pawn
#

this occur in only s20

#

yesyes

#

can u try if u can fill auto?

thick kiln
#

I'm not seeing any issues with autofill on my end, but it may be a bug specifically with the s20

jagged pawn
#

my pc work fine too

thick kiln
#

Can you check the autofill settings on your s20 and send a screenshot of what they see?

jagged pawn
#

oh my phone is S21, not s20 hahaha

#

samsung S21 5G ultra

thick kiln
#

Can you still check your settings?

jagged pawn
#

after success CVC , card No. still 1234 1234...

jagged pawn
thick kiln
#

There should be autofill settings somewhere on your phone - I don't know where they are specifically on a samsung device, but you should be able to find them if you search

jagged pawn
#

but that autofill is just about google password and samsung password

thick kiln
#

there should also be autofill settings that apply to payment methods

jagged pawn
#

no relevant setting found @@

#

nevermind maybe this is just my fault, or a s21 bug, i have to go live now

#

thanks for your patient helping

thick kiln
#

happy to help! For your specific autofill bug I'd suggest googling around to see where these autofill settings live and whather this may be a setting issue. If you don't find anything, you can also report this as a bug by writing into support at https://support.stripe.com/contact and someone will take a closer look

jagged pawn
#

oh , i visit stripe.dev/elements-examples/
my s21 have the same issue

young oar
#

Writing in to support, as @thick kiln said, is your best bet in terms of finding a resolution.

jagged pawn
#

ok thanks:)

#

Hello, I found that the Wechat QR code and alipay is china version wallet, is there any method to change to other region wallet of them ?
Like wechat HK, alipay Macau etc, as they consider as different app/wallet

young oar
#

You can enable WeChat Pay or AliPay in your dahsboard. They are available payment methods.

jagged pawn
#

I have enabled them, but it is china wechat and china alipay

#

is there any method to change to other region wallet of them ?

young oar
jagged pawn
#

if i choose wechat_pay, this is china version, any HK wechat pay option?

young oar
#

We do not differentiate that this time AFAIK

jagged pawn
#

can i specify apple pay here?

young oar
#

Which field are you looking at and on what object?

jagged pawn
#

$stripe = new \Stripe\StripeClient(STRIPE_API_KEY);

    $intent = $stripe->paymentIntents->create(
      [
        'amount' => $row_result['amount'] * 100,
        'currency' => 'hkd',
        "payment_method_types" => ["apple-pay"],
      ]
    );
#

something like that?

young oar
#

Digital wallets are treated the same as Cards on our back-end. If you want to implement a digital wallet only approach you could try using the payment request button

jagged pawn
#

okok thanks~