Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.<\/p>\n
Include Trustly in the list of available payment methods.<\/p>\n
We provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos<\/a>.<\/p>\n<\/div><\/div>\nIf you are using the \/paymentMethods<\/a> to show available payment methods to the shopper, specify the following:<\/p>\n\n countryCode<\/a>: Any supported country\/region. For example, SE<\/strong><\/span><\/li>\n amount.currency<\/a>: Any supported currency. For example, SEK<\/strong><\/span>.<\/li>\n amount.value<\/a>: The value of the payment, in minor units<\/a>.<\/li>\n channel<\/a>: Specify Web<\/strong><\/span>, iOS<\/strong><\/span>, or Android<\/strong><\/span>.<\/li>\n<\/ul>\nThe response contains paymentMethod.type<\/code>: trustly<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: trustly<\/strong><\/span><\/li>\ncountryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
If you are using the \/paymentMethods<\/a> to show available payment methods to the shopper, specify the following:<\/p>\n\n countryCode<\/a>: Any supported country\/region. For example, SE<\/strong><\/span><\/li>\n amount.currency<\/a>: Any supported currency. For example, SEK<\/strong><\/span>.<\/li>\n amount.value<\/a>: The value of the payment, in minor units<\/a>.<\/li>\n channel<\/a>: Specify Web<\/strong><\/span>, iOS<\/strong><\/span>, or Android<\/strong><\/span>.<\/li>\n<\/ul>\nThe response contains paymentMethod.type<\/code>: trustly<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: trustly<\/strong><\/span><\/li>\ncountryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
The response contains paymentMethod.type<\/code>: trustly<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: trustly<\/strong><\/span><\/li>\ncountryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
paymentMethod.type<\/code>: trustly<\/strong><\/span>.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: trustly<\/strong><\/span><\/li>\ncountryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
From your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: trustly<\/strong><\/span><\/li>\ncountryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
paymentMethod.type<\/code>: trustly<\/strong><\/span><\/li>\ncountryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
countryCode<\/code>: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2<\/a> country code. Exception: QZ<\/strong> (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.<\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
In the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
To complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
When using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Redirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
After the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
details<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
In the response note the following:<\/p>\n
resultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
pspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Use the\u00a0 resultCode<\/a> that you received in the \/payments\/details<\/a> response\u00a0to present the payment result to your shopper.<\/p>\n <\/p>\nThe resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
<\/p>\n
The resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
resultCode<\/code> values you can receive for Trustly are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/td>\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong> or Received<\/strong><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook<\/a>.<\/td>\n<\/tr>\n\nRefused<\/strong><\/td>\nThe payment was refused by the shopper's bank.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/td>\nfalse<\/strong><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/td>\ntrue<\/strong><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTest and go live<\/h2>\nTrustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
<\/a> If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:<\/p>\n
Trustly provides a test environment<\/a>. For Login ID\/Personal number<\/strong> values, you can enter any digits, following the format YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
YYMMDD-XXXX<\/code> (for example: 111111-1111<\/strong>). <\/p>\nYou can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
You can check the status of Trustly test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Transactions<\/strong>\u00a0>\u00a0Payments<\/strong>.<\/p>\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Before you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","articleFields":{"description":"Add Trustly to an existing API-only integration.","parameters":{"payment_method":"Trustly","country_code":"SE","currency_code":"SEK","payment_method_type":"trustly","payment_method_type_mobile":"trustly","integration":"API-only","platform":"Web","integration_guide_url":"build-your-integration\/advanced-flow?platform=Web&integration=API%20Only","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy.."},"last_edit_on":"26-05-2023 15:40","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly\/api-only","title":"Trustly for API only","content":"Accept Trustly payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add Trustly in your test Customer Area.\n\n\n\nBuild your payment form for Trustly\nInclude Trustly in the list of available payment methods.\n\nWe provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, SE\n amount.currency: Any supported currency. For example, SEK.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: trustly.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: trustly\ncountryCode: The shopper's country\/region. Format: the two-letter ISO-3166-1 alpha-2 country code. Exception: QZ (Kosovo). Include this in the request for a better shopper experience. When the shopper is redirected to Trustly's website, the country\/region will be automatically selected from the dropdown list.\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the\u00a0 resultCode that you received in the \/payments\/details response\u00a0to present the payment result to your shopper.\n \nThe resultCode values you can receive for Trustly are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful. You will receive the funds in 3 days.\n\n\nCancelled\nThe shopper canceled the payment while they were on the Trustly-hosted payment page.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the shopper's bank.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nTest and go live\nTrustly provides a test environment. For Login ID\/Personal number values, you can enter any digits, following the format YYMMDD-XXXX (for example: 111111-1111). \nYou can check the status of Trustly test payments in your\u00a0Customer Area\u00a0>\u00a0Transactions\u00a0>\u00a0Payments.\nBefore you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Trustly","lvl3":"Trustly for API only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/trustly","lvl3":"\/pt\/payment-methods\/trustly\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["Trustly"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
payments.js<\/p>"}}