#.dimitar-elements-migration
dapper zinc
river warren
Hi 👋 it may depend on the charge strucure you're using with your Connect Integration. Do you know if you're using Destination Charges or Direct Charges?
median bay
I believe we do direct charges, and we collect application_fee
river warren
Gotcha. In that case, using our flows for dynamic payment methods is likely the best approach for enabling Apple Pay for your Connected Accounts:
https://docs.stripe.com/connect/dynamic-payment-methods?connect-payment-integration-type=payment&connect-charge-type=direct&connect-account-type=standard&on-behalf-of=false
You will also need to look into registering the domains where you intend to surface Apple Pay for your Connected Accounts:
https://docs.stripe.com/payments/payment-methods/pmd-registration?platform=api#register-your-domain-while-using-connect
median bay
This sounds great, im just wondering what will i need to change in my frontend code.
Its a js elements integration
and i have "custom" fields for entering the card details and submit button
median bay
Gotcha. In that case, using our flows for dynamic payment methods is likely the ...
how will the apple pay or google pay buttons be visualised?
river warren
There is an example of what a rendered Payment Element looks like here:
https://docs.stripe.com/payments/payment-element
median bay
Oh i see, so i will no longer be able to use custom html?
river warren
Using custom input fields to collect raw card details comes with a large PCI compliance burden, I wouldn't recommend doing it and it's why we built our elements to handle that for you.