#Kamesh

1 messages · Page 1 of 1 (latest)

lone flameBOT
#

Hello! We'll be with you shortly. 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.

  • Kamesh, 1 minute ago, 8 messages
wintry tinsel
#

Depends on what components are you using

static beacon
#

sorry what do you mean by components?

wintry tinsel
#

Which integrations! ie. PaymentElement, or PaymentSheet on mobile...

static beacon
#

payment element

wintry tinsel
#

Then yes it should display the payment methods on Dashboard, as long as you use automatic payment method when creating the PaymentIntent

static beacon
#

but what if I would like to explicitly not display some options based on some conditions. can I tell SDK display only certain payment methods? (assuming all those payment methods are enabled in dashbaord)?

wintry tinsel
#

Sure, on the PaymentIntent creation time you can explicitly choose your payment methods

static beacon
#

thanks

#

also is there a way to get list of payment methods that are available for that browser settings?

#

i.e. how to get a list of payment methods available for that specific SDK instance initialised in a browser

wintry tinsel
#

Except wallets, the payment methods should be the same and not depend on the browser

static beacon
#

can we get which wallets are available ?

wintry tinsel
#

Could be not possible. What are you trying to do with it?

static beacon
#

trying to implement something like this in the screen shot

#

but the credit card is our own credit card form and not the one from SDK

#

so trying to find out whether we can do a customer accordian, initialise each accordian with it;s own payment element SDK with only that method mentioned in the payment_method_types

#

and under the credit card section we can use out custom form

#

when we do this, we need to check if google and apple pay are available prior to displaying this section and manually have those available.

wintry tinsel
#

That's not a good idea, because it will expose you to PCI Compliance. Using your own form means managing credit card on your own risk

static beacon
#

yes we understand that and we are already CPI compliant for this reason

#

we are trying to migrate existing payment but we are not ready to migrate the credit card payment yet

#

we will be migrating that later but in the mean time we would like to integrate payment element with all payment methods except for credit card and acheive the UX design as per the screenshot posted above. please help

#

NOTE: we have already acheived that using payment request but we are switching to payment element so that we can utilise additional payment methods

wintry tinsel
#

I see. Then on PaymentElement you exclude card from the payment_method_types parameter, you will have it without the card option

wintry tinsel
#

@static beacon reopenned here

static beacon
#

thanks

#

if i exclude card from payment method types, it will also exclude google and applypay

#

even if i exclude card, if i want to achieve the design screenshot as above, how can I introduce custom form into the design with SDK element

wintry tinsel
#

First yes card comes with ApplePay and GooglePay. If you plan to use Stripe's ApplePay and GooglePay probably you will need 2 separated PaymentIntents

#

Not exactly as your screenshot but maybe somewhat close

static beacon
#

will SDK html always hosted as an iframe?