#Nyxi

1 messages · Page 1 of 1 (latest)

sleek atlasBOT
pale tapir
#

Hey there

#

Apple Pay and Google Pay are card payment_method_types

#

We don't use a separate payment_method_type for these wallets

cobalt mica
#

That makes sense. Hold on a sec.

#

Shouldn't it also have link then?

pale tapir
#

link should be separate. Let me take a look for why it doesn't show link if you are expecting it

#

Doesn't look like you have Link turned on in your Dashboard

cobalt mica
#

I definitely do in live

#

maybe it's off for test

#

Shouldn't it be on then?

pale tapir
#

Not for Payment Element no

#

That is for PRB and Checkout

cobalt mica
#

Aha

pale tapir
cobalt mica
#

so just that?

#

Yes, that did it

#

"payment_method_types": [ "card", "link" ],

#

Thanks

pale tapir
#

👍

cobalt mica
#

It still won't render the link button though

#

even when using pi_3Mc8y6L7ilRdQXxE1bbWgKOu

#

or, the link option

pale tapir
#

Hrmm that's strange... it should if it shows as a payment_method_type.

#

There is no autofill your card with Link button?

cobalt mica
#

It just gives us the card input only

#

let me check

#

No, just card input

pale tapir
#

Any link I can reproduce at or is this local?

#

Have you logged out the client secret to ensure it is the one corresponding with the PI that has link for paymnet_method_type?

cobalt mica
#

yeah its pi_3Mc8y6L7ilRdQXxE1bbWgKOu_secret_Mxk94H7HZ1cgt5dD6k0lIyDfK

#

(test mode of course, so not so sensitive)

#

We're just putting it directly into the code right now for testing

#

And yeah it's local unfortunately

#

Hmm it seems to be related to the browser size

#

It renders it when we don't use "mobile size" in dev tools

#

in full size it renders it, and it remains if you then toggle to mobile size after, but if you load the page while in mobile mode, it won't show up, not if you exit mobile mode after either

pale tapir
#

Oh that's strange

#

I'll need to test that

#

Give me a sec

cobalt mica
#

Yeah it seems bit weird. We can't really control people's browser sizes

pale tapir
#

Agreed

#

Give me a moment

cobalt mica
#

It also seems to not want to display Apple Pay on Safari on Mac. It does show Google Pay when in Chrome. And we have a card added to the wallet on the machine

pale tapir
#

Did you register the domain for Apple Pay?

#

What browser were you testing link with?

#

Seems to be working in mobile view on Chrome

cobalt mica
#

Ah yeah that might be it when it comes to Apple Pay

#

I forgot about the domain stuff

#

Silently not working :))))

#

So another problem: You may only specify one of these parameters: automatic_payment_methods, confirmation_method.

#

I can't do manual confirmation with this?

pale tapir
#

Correct

cobalt mica
#

We don't use webhooks

#

😦

pale tapir
#

Manual Confirmation doesn't support all payment methods

#

That said

#

You could apply for deferred Intent beta

#

Then you can use it

cobalt mica
#

Beta number 3 incoming

pale tapir
#

We are working on improving this flow as you can see with that beta

#

But yeah doesn't work with the GA flow right now

cobalt mica
#

let me have a look at this

#

this looks exactly like what we need

pale tapir
#

What browser for the Link test were you using?

cobalt mica
#

our current flow also does not create a payment intent until you submit a payment method

#

Chrome.

pale tapir
#

Weird it is working for us on Chrome in Mobile view (my colleague tested)

cobalt mica
#

Odd

#

I've signed up for the beta

#

I'll email my contacts in Stripe also

pale tapir
#

Yeah that is likely fastest way to get approved

cobalt mica
#

They gave is MobilePay and Stripe Identity that way

pale tapir
#

I'm not sure on the Link thing. I'd try to just do a hard refresh of your Chrome browser

cobalt mica
#

Alright, we'll do some more testing

#

It might be a local issue

pale tapir
#

Yeah since it is working fine on our end I would suspect that's the case. But let us know if you continue to run into issues with it not showing and we can try and help debug further

cobalt mica
#

I will

#

Do you know if mobilepay will be integrated into Payment Element?

#

I assume yes?

pale tapir
#

I'd assume yes but don't know timeline

cobalt mica
#

Cool

pale tapir
#

Pretty sure the plan is to integrate all supported PaymentMethods into Payment Element in the future

cobalt mica
#

Okay

#

Is there a way for us to build this ourselves? We can't figure out how to determine what the PaymentRequestButton will end up as currently, so creating a "pay with this method" selector UI is difficult as it may be Apple Pay, Google Pay or Link

#

This was the motivation for switching to Payment Element

#

We can't use Payment Element until it accepts server-side confirmation

#

So until then

dim mantle
#

Hi there. Taking over for bismarck as they have to step out. What specifically are you wondering if there's a way to build yourself?

cobalt mica
#

So when you use the Payment Element, it will automatically detect if it's Google Pay, Apple Pay or Link, but when you use the PaymentRequestButton, it seems we can't predict what payment type it will be

#

So it's difficult to build a "choose a payment method" UI, when you don't actually know which options you have

#

We can't use Payment Element before we are allowed into the beta for manual confirmations, so until then we have to work around it

dim mantle
#

Gotcha. Well with the payment request button you have: paymentRequest.canMakePayment() which automatically displays what's available. Which individual payment methods are you interested in having a toggle for?

cobalt mica
#

We'd like to be able to distinguish between Apple Pay, Google Pay and Link, so we could have :

Select Payment Method
|--CARD--|--APPLE PAY--|
#

but since we don't know if it's Apple Pay, Google Pay or Link, it's hard to do

dim mantle
#

Yeah it is very new

cobalt mica
#

I mean this is helpful, but we still really can't do what we want where you select the payment method first, then click the button for it

#

As far as I can tell

#

But this is better than the current PaymentRequestButton at least

#

What do I need to do to get access to this?

#

Ah there's a form right there, sorry

dim mantle
#

Yeah you can on that page

cobalt mica
#

Okay

#

Thanks

#

This is a boolean promise though,no ? paymentRequest.canMakePayment()

#

Oh okay so I can provide a string to it

#

maybe that will work

dim mantle
#

So that does return whether apple pay, google pay, and link are supported for the customer, so that might work for you

cobalt mica
#

yeah but where do I get the strings ?

dim mantle
cobalt mica
#
  // Otherwise, let's see if we can use Example Pay
  const supportsExamplePay = await new PaymentRequest(
    [{ supportedMethods: "https://example.com/pay" }],
    details
  ).canMakePayment();
```
#

ahh sorry I was looking at the browser one

#

the built-in js thing

dim mantle
#

Should look like:

  applePay: true,
  googlePay: false,
  link: false,
}```
cobalt mica
#

Good

#

Thanks, this helps

#

Just so I understand correctly: It will only have 1 true of the 3 options?

#

Otherwise we need to know the priority chosen by the payment button

#

This seems to be indicated by the docs

#

Just want to make sure

dim mantle
#

So by the nature of how Apple and Google Pay work (restricted to device and browser types), they can't be active at the same time

#

Link might show true at the same time as Google Pay, for example, but I'm not entirely sure to be honest

cobalt mica
#

If you use the Payment Request Button, you always only get one option

#

So this would imply that only one of these booleans can be true at a time

#

since under link it says: paymentRequestButton Element will show as a branded Link button automatically.