{"title":"Sandbox account setup","category":"default","creationDate":1776961629,"content":"<div class=\"sc-notice warning\"><div>\n<p><strong>Hosted Payment Pages are no longer available<\/strong><br \/>\nThis page is for the Hosted Payment Pages (HPP) integration, which has reached end-of-life.  We are no longer processing transactions though HPP.<\/p>\n<p>If you have any questions, contact our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a>.<\/p>\n<\/div><\/div>\n<p>If you have a <a href=\"https:\/\/developer.paypal.com\/docs\/api\/sandbox\/sb-planning-accounts\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">PayPal Sandbox test account<\/a>, you can set it up in the Adyen test environment. The setup is very similar to granting the Adyen <a href=\"\/pt\/paypal-hpp\/paypal-account-setup\">API access<\/a> to a live PayPal account. With a PayPal Sandbox test account, you need to make sure that the Adyen test API user can access it to carry out the payment operations you want to test.<\/p>\n<p>PayPal Sandbox accounts\u00a0come in two flavors:<\/p>\n<ul>\n<li>Business: represents a merchant's PayPal account in a transaction.<\/li>\n<li>Personal:\u00a0represents a shopper's PayPal account in a transaction.<\/li>\n<\/ul>\n<p>PayPal automatically creates your first Sandbox Business and Personal\u00a0test account by cloning your live account and by appending the -facilitator and\u00a0-buyer suffix respectively to your email name.<\/p>\n<p>Follow PayPal's instructions to\u00a0<a href=\"https:\/\/developer.paypal.com\/docs\/api\/sandbox\/sb-planning-accounts\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">create your Sandbox Business and Personal accounts<\/a>.<\/p>\n<h2 id=\"set-up\">Set up<\/h2>\n<p>Set up your Business account to use it as a test merchant account in the Adyen test environment, the setup is very similar to granting the Adyen API access to a live PayPal account. With a PayPal Sandbox test account, you need to make sure that the Adyen test API user can access it to carry out the payment operation you want to test.<\/p>\n<p>Make sure that you are logged in with the created Facilitator\/Business account, not as the user who setup the sandbox accounts, on <a href=\"https:\/\/www.sandbox.paypal.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">https:\/\/sandbox.paypal.com\/<\/a>\u00a0while adding these API rights.<\/p>\n<p>Follow the steps described in PayPal account setup\u00a0and use the values listed below.<\/p>\n<ul>\n<li>\n<p>In the\u00a0<strong>Add New Third Party Permissions<\/strong>\u00a0window, go to the\u00a0<strong>Third Party Permission Username<\/strong>\u00a0field, and instead of entering\u00a0<code>paypal_api2.adyen.com<\/code>, input the following username:<\/p>\n<pre><code>sell1_1287491142_biz_api1.adyen.com<\/code><\/pre>\n<ol>\n<li>\n<p>Click <strong>Lookup<\/strong> to generate a list with the available permissions for the specified API.<\/p>\n<\/li>\n<li>\n<p>In the API permission list, select the following checkboxes:<\/p>\n<ol>\n<li>Use Express Checkout to process payments.<\/li>\n<li>Issue a refund for a specific transaction.<\/li>\n<li>Process your shopper's credit or debit card payments.<\/li>\n<li>Authorize and capture your PayPal transactions.<\/li>\n<li>Obtain information about a single transaction.<\/li>\n<li>Obtain authorization for pre-approved payments and initiate pre-approved transactions.<\/li>\n<li>Generate consolidated reports for all accounts.<br \/>\n(In some countries, you might get an error message informing you that the feature is not available in the country where you have your PayPal account. In this case, uncheck\/deselect this option.)<\/li>\n<li>Use Express Checkout to process mobile payments.<br \/>\n(If you do not support or plan to support mobile payments, leave this option unchecked.)<\/li>\n<\/ol>\n<\/li>\n<li>\n<p>Click <strong>Add<\/strong>.\u00a0<\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<p>After completing this task, contact our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a> to notify the\u00a0PayPal Sandbox Business test account email address\u00a0you want to use for your PayPal test payment integration.<\/p>\n<h2 id=\"test-payments\">Test payments<\/h2>\n<p>For testing, use the PayPal Sandbox personal shopper email address you specified in your PayPal developer environment. Using your own shopper email allows keeping track of your test payments in the\u00a0<a href=\"https:\/\/www.sandbox.paypal.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">PayPal sandbox<\/a>\u00a0at\u00a0a shopper level.<\/p>\n<h2 id=\"negative-testing\">Negative testing<\/h2>\n<p>Sandbox mimics the live PayPal site as closely as possible and the default setting is a positive test environment where you can test your system or application as it follows an error-free path. To reproduce specific error conditions, your test cases need to recreate the exact scenarios that trigger those errors to\u00a0verify that the system or application under test works as expected.<\/p>\n<p>Negative testing is a testing methodology that allows you force flows through the specific error conditions you want to test to verify that the system or application under test can gracefully handle situations that\u00a0break the happy flow. For example, negative testing checks\u00a0that the system or application under test can handle errors by throwing exceptions and returning descriptive error messages that can help understand and solve the problem instead of crashing.<\/p>\n<p>To enable this method:<\/p>\n<ul>\n<li>Log in to your\u00a0<a href=\"https:\/\/developer.paypal.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">PayPal developer account<\/a>.<\/li>\n<li>On the Account landing page, click\u00a0<strong>Dashboard<\/strong>.<\/li>\n<li>In the sidebar on the left, under\u00a0<strong>Sandbox<\/strong>, click\u00a0<strong>Accounts<\/strong>.<\/li>\n<li>In the account overview list, expand the desired account you want to edit, then click\u00a0<strong>Profile<\/strong>.<\/li>\n<li>In the\u00a0<strong>Account details<\/strong>\u00a0popup dialog window, select the\u00a0<strong>Settings<\/strong>\u00a0tab.<\/li>\n<li>On the\u00a0<strong>Settings<\/strong>\u00a0tab, set\u00a0<strong>Negative testing<\/strong>\u00a0to\u00a0<strong>ON<\/strong>.<\/li>\n<li>Click\u00a0<strong>Close<\/strong>.<\/li>\n<\/ul>\n<p>This sets the sandbox to the negative testing state for transactions. Without this configuration, the sandbox does not raise error conditions.<\/p>\n<p>After enabling negative testing for a sandbox profile, your account expects transaction amounts to be handled as error codes. To go back to normal positive testing, set <strong>Negative testing<\/strong> to <strong>Off<\/strong>.<\/p>\n<h3 id=\"negative-test-examples\">Negative test examples<\/h3>\n<p>The type of error you want to trigger defines the actual value you need to pass.\u00a0For example, you can use the '10606'\u00a0value to trigger a\u00a0Transaction rejected\u00a0error.<\/p>\n<p>To trigger an error condition on a field related to the amount, specify an error code value as a minor unit, as you would normally do for a standard payment.\u00a0On our test platform, the following error codes are mapped to the corresponding refusal reasons:<\/p>\n<table>\n<thead>\n<tr>\n<th>Error code \/ Amount<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>10001<\/td>\n<td>Internal error.<\/td>\n<\/tr>\n<tr>\n<td>10002<\/td>\n<td>Authentication\/Authorization failed.<\/td>\n<\/tr>\n<tr>\n<td>10201<\/td>\n<td>Agreement cancelled.<\/td>\n<\/tr>\n<tr>\n<td>10204<\/td>\n<td>Denied.<\/td>\n<\/tr>\n<tr>\n<td>10207<\/td>\n<td>Retry.<\/td>\n<\/tr>\n<tr>\n<td>10411<\/td>\n<td>This express checkout session has expired.<\/td>\n<\/tr>\n<tr>\n<td>10417<\/td>\n<td>Transaction cannot complete.<\/td>\n<\/tr>\n<tr>\n<td>10422<\/td>\n<td>Customer must choose new funding sources.<\/td>\n<\/tr>\n<tr>\n<td>10445<\/td>\n<td>This transaction cannot be processed at this time. Please try again later.<\/td>\n<\/tr>\n<tr>\n<td>10485<\/td>\n<td>Payment not authorized.<\/td>\n<\/tr>\n<tr>\n<td>10486<\/td>\n<td>This transaction could not be completed.<\/td>\n<\/tr>\n<tr>\n<td>10606<\/td>\n<td>Transaction rejected, please contact the buyer. Buyer cannot pay.<\/td>\n<\/tr>\n<tr>\n<td>10736<\/td>\n<td>Shipping address invalid city state postal code.<\/td>\n<\/tr>\n<tr>\n<td>11084<\/td>\n<td>User does not have a good funding source with which to pay.<\/td>\n<\/tr>\n<tr>\n<td>11607<\/td>\n<td>Duplicate request for specified Message Submission ID.<\/td>\n<\/tr>\n<tr>\n<td>13113<\/td>\n<td>Buyer cannot pay.<\/td>\n<\/tr>\n<tr>\n<td>13122<\/td>\n<td>Transaction refused.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>There are more errors codes and refusal reasons on our live platform, but not all of them are mapped in the test environment. The mapped error set above allows carrying out targeted negative testing on PayPal transactions in our test environment to verify that your system can handle incomplete or erroneous transactions in a live environment.<\/p>","url":"https:\/\/docs.adyen.com\/pt\/paypal-hpp\/sandbox-account-setup","articleFields":{"parameters":{"anchor_new":"<a href=\"\/payment-methods\/paypal\">PayPal using Smart Payment Buttons<\/a>","parent_page":"Hosted Payment Pages (HPP)","new_desc":"looking for a new integration"},"id":"24216715","type":"page","_expandable":{"operations":""},"status":"current","last_edit_on":"27-08-2020 14:34"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/paypal-hpp\/sandbox-account-setup","title":"Sandbox account setup","content":"\nHosted Payment Pages are no longer available\nThis page is for the Hosted Payment Pages (HPP) integration, which has reached end-of-life.  We are no longer processing transactions though HPP.\nIf you have any questions, contact our Support Team.\n\nIf you have a PayPal Sandbox test account, you can set it up in the Adyen test environment. The setup is very similar to granting the Adyen API access to a live PayPal account. With a PayPal Sandbox test account, you need to make sure that the Adyen test API user can access it to carry out the payment operations you want to test.\nPayPal Sandbox accounts\u00a0come in two flavors:\n\nBusiness: represents a merchant's PayPal account in a transaction.\nPersonal:\u00a0represents a shopper's PayPal account in a transaction.\n\nPayPal automatically creates your first Sandbox Business and Personal\u00a0test account by cloning your live account and by appending the -facilitator and\u00a0-buyer suffix respectively to your email name.\nFollow PayPal's instructions to\u00a0create your Sandbox Business and Personal accounts.\nSet up\nSet up your Business account to use it as a test merchant account in the Adyen test environment, the setup is very similar to granting the Adyen API access to a live PayPal account. With a PayPal Sandbox test account, you need to make sure that the Adyen test API user can access it to carry out the payment operation you want to test.\nMake sure that you are logged in with the created Facilitator\/Business account, not as the user who setup the sandbox accounts, on https:\/\/sandbox.paypal.com\/\u00a0while adding these API rights.\nFollow the steps described in PayPal account setup\u00a0and use the values listed below.\n\n\nIn the\u00a0Add New Third Party Permissions\u00a0window, go to the\u00a0Third Party Permission Username\u00a0field, and instead of entering\u00a0paypal_api2.adyen.com, input the following username:\nsell1_1287491142_biz_api1.adyen.com\n\n\nClick Lookup to generate a list with the available permissions for the specified API.\n\n\nIn the API permission list, select the following checkboxes:\n\nUse Express Checkout to process payments.\nIssue a refund for a specific transaction.\nProcess your shopper's credit or debit card payments.\nAuthorize and capture your PayPal transactions.\nObtain information about a single transaction.\nObtain authorization for pre-approved payments and initiate pre-approved transactions.\nGenerate consolidated reports for all accounts.\n(In some countries, you might get an error message informing you that the feature is not available in the country where you have your PayPal account. In this case, uncheck\/deselect this option.)\nUse Express Checkout to process mobile payments.\n(If you do not support or plan to support mobile payments, leave this option unchecked.)\n\n\n\nClick Add.\u00a0\n\n\n\n\nAfter completing this task, contact our Support Team to notify the\u00a0PayPal Sandbox Business test account email address\u00a0you want to use for your PayPal test payment integration.\nTest payments\nFor testing, use the PayPal Sandbox personal shopper email address you specified in your PayPal developer environment. Using your own shopper email allows keeping track of your test payments in the\u00a0PayPal sandbox\u00a0at\u00a0a shopper level.\nNegative testing\nSandbox mimics the live PayPal site as closely as possible and the default setting is a positive test environment where you can test your system or application as it follows an error-free path. To reproduce specific error conditions, your test cases need to recreate the exact scenarios that trigger those errors to\u00a0verify that the system or application under test works as expected.\nNegative testing is a testing methodology that allows you force flows through the specific error conditions you want to test to verify that the system or application under test can gracefully handle situations that\u00a0break the happy flow. For example, negative testing checks\u00a0that the system or application under test can handle errors by throwing exceptions and returning descriptive error messages that can help understand and solve the problem instead of crashing.\nTo enable this method:\n\nLog in to your\u00a0PayPal developer account.\nOn the Account landing page, click\u00a0Dashboard.\nIn the sidebar on the left, under\u00a0Sandbox, click\u00a0Accounts.\nIn the account overview list, expand the desired account you want to edit, then click\u00a0Profile.\nIn the\u00a0Account details\u00a0popup dialog window, select the\u00a0Settings\u00a0tab.\nOn the\u00a0Settings\u00a0tab, set\u00a0Negative testing\u00a0to\u00a0ON.\nClick\u00a0Close.\n\nThis sets the sandbox to the negative testing state for transactions. Without this configuration, the sandbox does not raise error conditions.\nAfter enabling negative testing for a sandbox profile, your account expects transaction amounts to be handled as error codes. To go back to normal positive testing, set Negative testing to Off.\nNegative test examples\nThe type of error you want to trigger defines the actual value you need to pass.\u00a0For example, you can use the '10606'\u00a0value to trigger a\u00a0Transaction rejected\u00a0error.\nTo trigger an error condition on a field related to the amount, specify an error code value as a minor unit, as you would normally do for a standard payment.\u00a0On our test platform, the following error codes are mapped to the corresponding refusal reasons:\n\n\n\nError code \/ Amount\nDescription\n\n\n\n\n10001\nInternal error.\n\n\n10002\nAuthentication\/Authorization failed.\n\n\n10201\nAgreement cancelled.\n\n\n10204\nDenied.\n\n\n10207\nRetry.\n\n\n10411\nThis express checkout session has expired.\n\n\n10417\nTransaction cannot complete.\n\n\n10422\nCustomer must choose new funding sources.\n\n\n10445\nThis transaction cannot be processed at this time. Please try again later.\n\n\n10485\nPayment not authorized.\n\n\n10486\nThis transaction could not be completed.\n\n\n10606\nTransaction rejected, please contact the buyer. Buyer cannot pay.\n\n\n10736\nShipping address invalid city state postal code.\n\n\n11084\nUser does not have a good funding source with which to pay.\n\n\n11607\nDuplicate request for specified Message Submission ID.\n\n\n13113\nBuyer cannot pay.\n\n\n13122\nTransaction refused.\n\n\n\nThere are more errors codes and refusal reasons on our live platform, but not all of them are mapped in the test environment. The mapped error set above allows carrying out targeted negative testing on PayPal transactions in our test environment to verify that your system can handle incomplete or erroneous transactions in a live environment.","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"PayPal (HPP)","lvl2":"Sandbox account setup"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/paypal-hpp","lvl2":"\/pt\/paypal-hpp\/sandbox-account-setup"},"levels":3,"category":"","category_color":"","tags":["Sandbox","account","setup"]}}