PayTabs SDK makes the integration with the PayTabs payment gateway very easy by providing a ready-made payment screen that handles the card entry and, billing & shipping information and completes the missing details.
This article is dedicated to walking you through how to perform tokenized with 3DS feature-enabled transactions using this SDK.
To enable tokenization payments to avoid making your customers provide the card details in each payment, please follow the below instructions:
- Request a token in creating any payment request by passing the "tokeniseType" along with the "tokenFormat" with the preferred type and format that suits your business needs within your PaymentSdkConfigBuilder, as shown below.
To know more about these parameters and what are the available values you can pass please check the "2.3 Native Android SDK | Enums" solution article.
Make sure your current Activity or Fragment extends class.
Configure the billing & shipping information for this payment, noting that the shipping information is optional. To know more about this, please check our 3.1 Native Android SDK | Manage Shipping and Billing details and 2.1 Native Android SDK | Configuration Options & Parameters solution articles.
Then create an object from
PaymentSdkConfigBuilderand fill it out with your credentials and payment details. To know more about what is the exact values that should be passed here, please check our 2.1 Native Android SDK | Configuration Options & Parameters and 2.2 Native Android SDK | The PaymentSdkConfigBuilder Object solution articles.
val configData = PaymentSdkConfigBuilder(profileId, serverKey, clientKey, amount ?: 0.0, currency) .setCartDescription(cartDesc) .setLanguageCode(locale) .setBillingData(billingData) .setMerchantCountryCode("AE") // ISO alpha 2 .setShippingData(shippingData) .setCartId("123") .setTransactionType(transType) .showBillingInfo(false) .showShippingInfo(true) .forceShippingInfo(true) .setScreenTitle(screenTitle) .build();
- Only then you will be ready to start/initiate the payment by passing your PaymentSdkConfigBuilder object along with the current inherited activity/fragment instance -in which you will handle the payment response- to the
function. To know more about this please check our 2.2 Native Android SDK | The PaymentSdkConfigBuilder Object and Step 5 - Native Android SDK | Handle the payment response solution articles.
startCardPayment(context = this, ptConfigData = configData, callback=this)
After this, you will receive the token and the masked card (PaymentInfoViewModel.paymentDescription) within your interface/class where you handled the payment response. You will need to save them for future usage.
Then perform any further recurring transaction according to your business needs by repeating steps 2 and 3 from this solution article, then directly start the tokenized card payment via the start3DSecureTokenizedCardPayment function by passing the PaymentSDKConfiguration object, and the inherited activity/fragment instance -which you are handling your payment within- along with the token and PaymentSDKSavedCardInfo, which includes the masked card and the card type (saved from the previous step ).
start3DSecureTokenizedCardPayment(context = this, ptConfigData = configData, savedCardInfo = PaymentSDKSavedCardInfo("Masked card", "Visa or MC or card type"), token: *TOKEN*, callback = this)
This will make the payment behavior would be like the one below, in which your customers will have to provide only their CVVs instead of the whole card details.
⌂ To get familiar with the whole process and the other steps, kindly navigate to our "The Native Android SDK Integration Manual" solution article.
⇦ And to navigate to the previous step in the integration process "Step 2 - Configure the integration method" click here. ⇦ And to get familiar with the rest of the steps regarding the current step "Step 3 - Initiating the payment" click here.
⇨ Or you can navigate to the next step in the integration process "Step 4 - Accepting the payment" kindly click here.