Question: support for tokenization? about react-native-adyen-payment HOT 5 OPEN

@marco-jantke Will defenitely have a look into it.

from react-native-adyen-payment.

Short answer: Yes it is possible (at least on Android, will try for iOS next week)

In order to enable it you have to add the property showStorePaymentField to the component data:

var componentData = {
    scheme: {
       card_public_key : CARD_PUBLIC_KEY,
       showStorePaymentField: true,
    },
    bcmc: {
       card_public_key : CARD_PUBLIC_KEY,
       showStorePaymentField: true,
    }
}

I did not find this anywhere in the documentation, so it is probably a good idea to add this somewhere (as I won't expect anyone to go through the source code of this wrapper to figure it out).

from react-native-adyen-payment.

I checked on iOS and it seems not to work using the same solution as shown above for Android. Seems like I have to dive into the implementation to figure out the correct call in the coming days.

from react-native-adyen-payment.

I found the issue on iOS. It turns out that the properties have different names on Android and iOS. On Android it is called showStorePaymentField and on iOS it is called showsStorePaymentMethodField (note the extra 's' after show).

TLDR of the messages above:
Yes, tokenization is supported on both iOS and Android. In order to enable it you have to pass two properties to the componentData:

const componentData = {
    scheme: {
       card_public_key : CARD_PUBLIC_KEY,
       showStorePaymentField: true,   // For Android
       showsStorePaymentMethodField: true, // For iOS
    },
    bcmc: {
       card_public_key : CARD_PUBLIC_KEY,
       showStorePaymentField: true,   // For Android
       showsStorePaymentMethodField: true, // For iOS
    }
}

from react-native-adyen-payment.

from react-native-adyen-payment.