Excluding transitive dependencies

[jvanderwee]

Description

Is it possible to exclude transitive dependencies such as wechatpay when using drop-in? we have no intention of supporting WeChat as a payment method, nor some others such as Seven Eleven

Integration Information

1. Server-side integration: Sessions/Advanced flow
2. Client-side integration: Drop-in
3. SDK version: 5.17.0

[OscarSpruit]

Hi @jvanderwee, thank you for reaching out! Yes, drop-in is designed to exclude transitive dependencies. However, there is one important side note: if you exclude the transitive dependency for a certain payment method, then you have to make sure this payment method is not passed to drop-in with the PaymentMethodsApiResponse or CheckoutSession. If the excluded payment method does appear in one of those objects, it will be displayed in the payment method list. When a user clicks on it, it might result in a crash. We aim to improve this in the next major release (v6).

[jvanderwee]

Thank you! Is this documented somewhere that I've missed?

[OscarSpruit]

This is currently not documented anywhere. Thank you for bringing that up, I will share this with the team internally