[NEED ASSIST] How to add a pre-populated address when using Apple Pay from the Drop-In Component

[Lukaz32]

I couldn't find in the docs/source code a way to set a shippingContact object for pre-filling the user address when making a purchase with Apple Pay through the Drop-In component. Is there a way to do that?

Thanks in advance.

[descorp]

Hey @Lukaz32

This feature will be added in v4. Sorry for the inconvenience

[Lukaz32]

@descorp Thanks for the quick reply. Is it possible to retrieve the shipping address provided by the user in the Apple Pay sheet after the payment has been completed?

[descorp]

Hey @Lukaz32

Sorry for misinformation. In v4 have added .billingContact, not a .shippingContact. Shipping contact is a complicated flow, that is not easy to incorporate for generic purpose. We will research on how to make it possible in v4.1.0 Thanks for bringing this idea on the table :D

For now, I can only suggest to make a custom implementation of ApplePay outside of the DropIn; especially since using ApplePay as "fast-checkout" is recommended by Human Interface Guidelines

[Lukaz32]

Alright. Thanks for the clarification. On a related matter, is it not possible to display the Apple Pay option in the Drop-In payment methods when the user doesn't have a card configured for Apple Pay in the device? The field is not displayed at all on those cases and I couldn't find any API to configure this.

[descorp]

Yes, this is correct - we only showing ApplePay field in Drop-in when payment is possible:

• device supports Apple Pay;
• country code and currency is correct;
• amount in summaryItems is non negative;
• at last one card from supported networks is present in shopper's wallet (e.x. Apple Pay will not be displayed if shopper have only one maestro in wallet, but maestro is not configured as payment method in your Adyen Customer Area);
• e.t.c

[descorp]

Hey @Lukaz32

We have noticed that it is not necessary to filter payment attempts by supported networks. ApplePay will suggest to a shopper to add a new card. ~~We will work on update in v4.1.0~~ Will be released in 4.3.0

[descorp]

I am closing this issue due to lack of activity