\n <\/in-page-filtering>\n<\/div>\n\n <\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay\/android-component","articleFields":{"description":"Add Rakuten Pay to your Components integration.","never_cache_twig":true,"filters_component":true,"parameters":{"tx_variant":"rakutenpay","component_class_name":"InstantPaymentComponent","component_class_config":"InstantPayment","pm_directory":"rakutenpay","payment_method":"Rakuten Pay","action_type":"redirect"},"filters_config_folder":"payment-methods\/rakutenpay\/android\/component"},"algolia":[{"url":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay\/android-component","title":"Rakuten Pay Android Component","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Sessions flow Android Components integration.\n\n\n\nCheckout API\nMake sure that you use Checkout API v68 or later.\n \n\n\nRedirect handling\nMake sure that your existing integration is set up to handle the redirect. action.type: redirect\n\n\n\nSetup steps\nBefore you begin, add Rakuten Pay in your Customer Area.\n\n\n\nAdd additional parameters to your \/sessions request\nYou do not need to add any parameters when you create a payment session.\nImport the Component for Rakuten Pay\nTo import the library and include the module for Rakuten Pay.\n\n\n \n \n \n \n\nAdd additional configuration for Rakuten Pay\nAdd a configuration object with the following parameters:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\nsetSubmitButtonVisible\n\nSet to false to hide the submit button. The default is true.\n\n\n\n\n \n\nLaunch and show the Component for Rakuten Pay\nTo create the Component for Rakuten Pay, use the InstantPaymentComponent class.\n\n\n \n \n \n \n\nRecurring\nIf you have a business model based on subscription and unscheduled card-on-file payments, Rakuten Pay permits one-off card-on-file transactions after a review process. If you do not have a periodic charging cadence, Rakuten Pay prohibits you from initiating the Recurring Processing Model for card-on-file, which is primarily allowed for the Food & Beverage business category. You must apply for every Recurring Processing Model when you request Rakuten Pay.\nRefer to Create tokens to integrate with our tokenization feature.\n\nWe strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.\nTest and go live\nTo test Rakuten Pay payments, use the acquirer account DGFT_AcquirerAccount_RakutenPay_closedLoop in the TEST environment.\nYou will be redirected you to a DGFT simulator tool to complete the transaction. You do not need the Rakuten Pay app.\nYou can check the status of Rakuten Pay test account transactions in your Customer Area at Transactions > Payments.","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Rakuten Pay","lvl3":"Rakuten Pay Android Component"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay","lvl3":"\/payment-methods\/rakutenpay\/android-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Rakuten","Android","Component"]},{"url":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay\/android-component?flow=Sessions flow&integration=Component","title":"Sessions flow Component","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Sessions flow Android Components integration.\n\n\n\nCheckout API\nMake sure that you use Checkout API v68 or later.\n \n\n\nRedirect handling\nMake sure that your existing integration is set up to handle the redirect. action.type: redirect\n\n\n\nSetup steps\nBefore you begin, add Rakuten Pay in your Customer Area.\n\n\n\nAdd additional parameters to your \/sessions request\nYou do not need to add any parameters when you create a payment session.\nImport the Component for Rakuten Pay\nTo import the library and include the module for Rakuten Pay.\n\n\n \n \n \n \n\nAdd additional configuration for Rakuten Pay\nAdd a configuration object with the following parameters:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\nsetSubmitButtonVisible\n\nSet to false to hide the submit button. The default is true.\n\n\n\n\n \n\nLaunch and show the Component for Rakuten Pay\nTo create the Component for Rakuten Pay, use the InstantPaymentComponent class.\n\n\n \n \n \n \n\nRecurring\nIf you have a business model based on subscription and unscheduled card-on-file payments, Rakuten Pay permits one-off card-on-file transactions after a review process. If you do not have a periodic charging cadence, Rakuten Pay prohibits you from initiating the Recurring Processing Model for card-on-file, which is primarily allowed for the Food & Beverage business category. You must apply for every Recurring Processing Model when you request Rakuten Pay.\nRefer to Create tokens to integrate with our tokenization feature.\n\nWe strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.\nTest and go live\nTo test Rakuten Pay payments, use the acquirer account DGFT_AcquirerAccount_RakutenPay_closedLoop in the TEST environment.\nYou will be redirected you to a DGFT simulator tool to complete the transaction. You do not need the Rakuten Pay app.\nYou can check the status of Rakuten Pay test account transactions in your Customer Area at Transactions > Payments.","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Rakuten Pay","lvl3":"Rakuten Pay Android Component"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay","lvl3":"\/payment-methods\/rakutenpay\/android-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Sessions flow","Component"]},{"url":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay\/android-component?flow=Advanced flow&integration=Component","title":"Advanced flow Component","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Advanced flow Android Components integration.\n \n\n\nAction handling\nMake sure that your existing integration is set up to handle the additional action. action.type: redirect.\n\n\n\nSetup steps\n Before you begin, add Rakuten Pay in your Customer Area. \n\n\nImport the Component for Rakuten Pay\nTo import the library and include the module for Rakuten Pay.\n\n\n \n \n \n \n\nAdd additional configuration for Rakuten Pay\nAdd a configuration object with the following parameters:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\nsetSubmitButtonVisible\n\nSet to false to hide the submit button. The default is true.\n\n\n\n\n \n\nLaunch and show the Component for Rakuten Pay\nTo create the Component for Rakuten Pay, use the InstantPaymentComponent class.\n\n\n \n \n \n \n\nAdd additional parameters to your \/payments request\nYou do not need to add any parameters to the \/payments request when you make a payment.\nRecurring\nIf you have a business model based on subscription and unscheduled card-on-file payments, Rakuten Pay permits one-off card-on-file transactions after a review process. If you do not have a periodic charging cadence, Rakuten Pay prohibits you from initiating the Recurring Processing Model for card-on-file, which is primarily allowed for the Food & Beverage business category. You must apply for every Recurring Processing Model when you request Rakuten Pay.\nRefer to Create tokens to integrate with our tokenization feature.\n\nWe strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.\nTest and go live\nTo test Rakuten Pay payments, use the acquirer account DGFT_AcquirerAccount_RakutenPay_closedLoop in the TEST environment.\nYou will be redirected you to a DGFT simulator tool to complete the transaction. You do not need the Rakuten Pay app.\nYou can check the status of Rakuten Pay test account transactions in your Customer Area at Transactions > Payments.","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Rakuten Pay","lvl3":"Rakuten Pay Android Component"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/rakutenpay","lvl3":"\/payment-methods\/rakutenpay\/android-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Advanced flow","Component"]}]}