\n <\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in","articleFields":{"description":"Add Klarna Debit Risk to your Drop-in integration.","never_cache_twig":true,"parameters":{"tx_variant":"directEbanking","component_class_name":"DropIn","pm_directory":"klarna-debit-risk","component_class_config":"directEbanking","android_pm_type":"","payment_method":"Klarna Debit Risk","action_type":"redirect"},"filters_component":true,"filters_config_folder":"payment-methods\/klarna-debit-risk\/android\/dropin"},"algolia":[{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in","title":"Klarna Debit Risk Android Drop-in","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Sessions flow Drop-in integration. Required version of Checkout API: v68 or later. \n\n\nSetup steps\nBefore you begin, add Klarna Debit Risk in your Customer Area.\n\n\n\nAdd additional parameters to your \/sessions request\nYou do not need to add any additional parameters when you create a payment session.\nAdd additional configuration for Klarna Debit Risk\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\nRecurring payments\nWe support recurring transactions for Klarna Debit Risk through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\n\nWe strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.\n\nCreate a token\nStore SEPA details using a Klarna Debit Risk payment\nWhen creating a token with a Klarna Debit Risk payment, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters.\nInclude the following parameters in your \/payments request:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\npaymentMethod.type\n\nSet to directEbanking.\n\n\n returnUrl\n\nURL to where the shopper should be redirected back to after they complete the payment.\n\n\n countryCode\n\nThe shopper's country\/region in a two-letter country code format. Include this in the request to make sure the shopper can proceed in the Klarna flow.\n\n\n shopperLocale\n\nThe language that the Klarna Debit Risk page should be rendered in. The page can be the local language (for example, nl-NL for the Netherlands) or in en-US.\n\n\n shopperEmail\n\nThe email of the shopper. If included, Klarna will pre-fill it if the shopper does not have a Klarna account yet and needs to create one.\n\n\n telephoneNumber\n\nThe phone number of the shopper. If included, Klarna will pre-fill it in the Klarna log-in screen.\n\n\n recurringProcessingModel\n\nThe type of recurring payment the token is intended for.If you want to use the token for more than one type of recurring payment, use the type that is most appropriate at the time of token creation. In subsequent transactions, you can specify another recurringProcessingModel.Possible values:UnscheduledCardOnFile: A transaction that occurs on a non-fixed schedule and\/or have variable amounts.Subscription: A transaction for a fixed or variable amount, which follows a fixed schedule.CardOnFile: A transaction where bank account details are stored to enable one-click or omnichannel journeys, or to offer a faster checkout later. Because of the chargeback risks associated with SEPA Direct Debit, it is not recommended to use SEPA Direct Debit for CardOnFile flows. Because the user is present, it is recommended to let the user authorize individual payments with Klarna Debit Risk.\n\n\n shopperInteraction\n\nIndicates the sales channel through which the shopper authorizes the payment. For online transactions, this is Ecommerce.\n\n\n shopperReference\n\nYour unique reference for the shopper. Do not include personally identifiable information (PII), such as name or email address.Format:Minimum length: 3 characters.Case-sensitive.\n\n\n storePaymentMethod\n\nWhen you first create a token, set to true to store the shopper's payment details. For subsequent payments, this parameter is not required.\n\n\n\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. The payment will be processed as a SEPA Direct Debit payment. You do not need to include any additional parameters.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. The payment will be processed as a SEPA Direct Debit payment. You do not need to include any additional parameters.\n\n \nTest and go live\nBefore accepting live payments, test your integration using the test environment and sample data provided by Klarna.\nYou can then check the status of Klarna test payments in your Customer Area > Transactions > Payments.\nBefore going live make sure to enable Klarna Debit Risk on your live merchant account on the Customer Area.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Klarna Debit Risk","lvl3":"Klarna Debit Risk Android Drop-in"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk","lvl3":"\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in"},"levels":4,"category":"Payment method","category_color":"green","tags":["Klarna","Debit","Android","Drop-in"]},{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in?flow=Sessions flow&integration=Drop-in","title":"Sessions flow Drop-in","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Sessions flow Drop-in integration. Required version of Checkout API: v68 or later. \n\n\nSetup steps\nBefore you begin, add Klarna Debit Risk in your Customer Area.\n\n\n\nAdd additional parameters to your \/sessions request\nYou do not need to add any additional parameters when you create a payment session.\nAdd additional configuration for Klarna Debit Risk\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\nRecurring payments\nWe support recurring transactions for Klarna Debit Risk through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\n\nWe strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.\n\nCreate a token\nStore SEPA details using a Klarna Debit Risk payment\nWhen creating a token with a Klarna Debit Risk payment, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters.\nInclude the following parameters in your \/payments request:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\npaymentMethod.type\n\nSet to directEbanking.\n\n\n returnUrl\n\nURL to where the shopper should be redirected back to after they complete the payment.\n\n\n countryCode\n\nThe shopper's country\/region in a two-letter country code format. Include this in the request to make sure the shopper can proceed in the Klarna flow.\n\n\n shopperLocale\n\nThe language that the Klarna Debit Risk page should be rendered in. The page can be the local language (for example, nl-NL for the Netherlands) or in en-US.\n\n\n shopperEmail\n\nThe email of the shopper. If included, Klarna will pre-fill it if the shopper does not have a Klarna account yet and needs to create one.\n\n\n telephoneNumber\n\nThe phone number of the shopper. If included, Klarna will pre-fill it in the Klarna log-in screen.\n\n\n recurringProcessingModel\n\nThe type of recurring payment the token is intended for.If you want to use the token for more than one type of recurring payment, use the type that is most appropriate at the time of token creation. In subsequent transactions, you can specify another recurringProcessingModel.Possible values:UnscheduledCardOnFile: A transaction that occurs on a non-fixed schedule and\/or have variable amounts.Subscription: A transaction for a fixed or variable amount, which follows a fixed schedule.CardOnFile: A transaction where bank account details are stored to enable one-click or omnichannel journeys, or to offer a faster checkout later. Because of the chargeback risks associated with SEPA Direct Debit, it is not recommended to use SEPA Direct Debit for CardOnFile flows. Because the user is present, it is recommended to let the user authorize individual payments with Klarna Debit Risk.\n\n\n shopperInteraction\n\nIndicates the sales channel through which the shopper authorizes the payment. For online transactions, this is Ecommerce.\n\n\n shopperReference\n\nYour unique reference for the shopper. Do not include personally identifiable information (PII), such as name or email address.Format:Minimum length: 3 characters.Case-sensitive.\n\n\n storePaymentMethod\n\nWhen you first create a token, set to true to store the shopper's payment details. For subsequent payments, this parameter is not required.\n\n\n\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. The payment will be processed as a SEPA Direct Debit payment. You do not need to include any additional parameters.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. The payment will be processed as a SEPA Direct Debit payment. You do not need to include any additional parameters.\n\n \nTest and go live\nBefore accepting live payments, test your integration using the test environment and sample data provided by Klarna.\nYou can then check the status of Klarna test payments in your Customer Area > Transactions > Payments.\nBefore going live make sure to enable Klarna Debit Risk on your live merchant account on the Customer Area.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Klarna Debit Risk","lvl3":"Klarna Debit Risk Android Drop-in"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk","lvl3":"\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in"},"levels":4,"category":"Payment method","category_color":"green","tags":["Sessions flow","Drop-in"]},{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in?flow=Advanced flow&integration=Drop-in","title":"Advanced flow Drop-in","content":"Requirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing Advanced flow Android Drop-in integration.\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 Klarna Debit Risk in your Customer Area.\n\n\n\nAdd additional configuration for Klarna Debit Risk\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\nAdd additional parameters to your \/payments request\nYou do not need to add any additional parameters to the \/payments request.\nRecurring payments\nWe support recurring transactions for Klarna Debit Risk through SEPA Direct Debit. To make recurring payments, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\n\nWe strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.\n\nCreate a token\nStore SEPA details using a Klarna Debit Risk payment\nWhen creating a token with a Klarna Debit Risk payment, use the standard tokenization parameters in your payment request. You do not need to include any additional parameters.\nInclude the following parameters in your \/payments request:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\npaymentMethod.type\n\nSet to directEbanking.\n\n\n returnUrl\n\nURL to where the shopper should be redirected back to after they complete the payment.\n\n\n countryCode\n\nThe shopper's country\/region in a two-letter country code format. Include this in the request to make sure the shopper can proceed in the Klarna flow.\n\n\n shopperLocale\n\nThe language that the Klarna Debit Risk page should be rendered in. The page can be the local language (for example, nl-NL for the Netherlands) or in en-US.\n\n\n shopperEmail\n\nThe email of the shopper. If included, Klarna will pre-fill it if the shopper does not have a Klarna account yet and needs to create one.\n\n\n telephoneNumber\n\nThe phone number of the shopper. If included, Klarna will pre-fill it in the Klarna log-in screen.\n\n\n recurringProcessingModel\n\nThe type of recurring payment the token is intended for.If you want to use the token for more than one type of recurring payment, use the type that is most appropriate at the time of token creation. In subsequent transactions, you can specify another recurringProcessingModel.Possible values:UnscheduledCardOnFile: A transaction that occurs on a non-fixed schedule and\/or have variable amounts.Subscription: A transaction for a fixed or variable amount, which follows a fixed schedule.CardOnFile: A transaction where bank account details are stored to enable one-click or omnichannel journeys, or to offer a faster checkout later. Because of the chargeback risks associated with SEPA Direct Debit, it is not recommended to use SEPA Direct Debit for CardOnFile flows. Because the user is present, it is recommended to let the user authorize individual payments with Klarna Debit Risk.\n\n\n shopperInteraction\n\nIndicates the sales channel through which the shopper authorizes the payment. For online transactions, this is Ecommerce.\n\n\n shopperReference\n\nYour unique reference for the shopper. Do not include personally identifiable information (PII), such as name or email address.Format:Minimum length: 3 characters.Case-sensitive.\n\n\n storePaymentMethod\n\nWhen you first create a token, set to true to store the shopper's payment details. For subsequent payments, this parameter is not required.\n\n\n\n\n \n\nWhen a token is created, you receive a recurring.token.created webhook. The webhook contains the storedPaymentMethodId that you can use to make subsequent payments using the stored payment details.\nMake a payment with a token\n\nOnly use tokenised payments in scenarios where the shopper is not present, that is, UnscheduledCardOnFile and Subscription payments.\n\nMake a subscription payment\nMake a subscription payment using the standard tokenization parameters. The payment will be processed as a SEPA Direct Debit payment. You do not need to include any additional parameters.\n\n \n\nMake an unscheduled card-on-file payment\nMake an unscheduled card-on-file using the standard tokenization parameters. The payment will be processed as a SEPA Direct Debit payment. You do not need to include any additional parameters.\n\n \nTest and go live\nBefore accepting live payments, test your integration using the test environment and sample data provided by Klarna.\nYou can then check the status of Klarna test payments in your Customer Area > Transactions > Payments.\nBefore going live make sure to enable Klarna Debit Risk on your live merchant account on the Customer Area.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Klarna Debit Risk","lvl3":"Klarna Debit Risk Android Drop-in"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/klarna-debit-risk","lvl3":"\/pt\/payment-methods\/klarna-debit-risk\/android-drop-in"},"levels":4,"category":"Payment method","category_color":"green","tags":["Advanced flow","Drop-in"]}],"articleFiles":{"sepa-create-token-klarna-debit-risk.js":"
sepa-create-token-klarna-debit-risk.js<\/p>"}}