#daydream-Connect
1 messages · Page 1 of 1 (latest)
Let me create one.
pi_3LXIldGdCMCGaWnU1rnminDx
In my connected (test) account I am getting this warning in /settings/payment_methods
If you prefer to use payment_method_types, refer to the manual settings page.```
The payment_method_types of this PI contains both link and card. So Link and Google Pay (pre-requisite required) are both available to your customer.
So it should be showing here?
You need to follow this guide (https://stripe.com/docs/payments/link/accept-a-payment) to add Link to your PaymentElement integration
For Google Pay to work, make sure you have logged in a Google account in Chrome browser, and have an active card in your Google Pay account,
I thought I didnt have to define what payment methods are available, I thought If I left in blank it would use whatever is in my dashboard.
'payment_method_types' => [
'link',
'card'
]```
Yes these payment methods are available (you can check the payment_method_types array of the PaymentInent), but there are some pre-requisites in order to make them work. For instance in Link's case, you also need to integrate LinkAuthenticationElement
Are there requirements for each payment method? Like for Bank Accounts?
You mean ACH debit (https://stripe.com/docs/payments/ach-debit/accept-a-payment) ? No, you don't need to integrate additional component to make it work. But you need to pass additional param when creating PaymentIntent to use financial connections
The reason that Link payment method requires LinkAuthenticationElement is that it allows your customer to log in to their link account, so that the saved payment methods (if any) can be displayed to the customer.
and things like Klarna and Affirm, I have to define further params?
In normal scenario you don't need to. But there are some params specific to klarna and affirm, you can choose whether to use them based on your business.
https://stripe.com/docs/payments/affirm/accept-a-payment
https://stripe.com/docs/payments/afterpay-clearpay/accept-a-payment
Visit these pages to learn more about the payment method specific params
Ok dang. I thought that was the point of the new payment elements, that is automatically did this for you.
I'd say it did most of the things for you (i.e., you don't need write your own UIs for different payment method). It's just that some payment methods require (or offer) more params.
OK now I'm getting it. Thanks Jack for your help. ❤️
No problem!
Talk to you again I'm sure. 😛