Test result codes<\/div>
Learn how to trigger specific result codes to test how your integration handles them.<\/p><\/p><\/a><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/online-payments\/build-your-integration\/payment-result-codes","articleFields":{"description":"Use result codes to understand the current state of a payment.","id":"42834099","type":"page","_expandable":{"operations":""},"status":"current","feedback_component":true,"filters_component":false,"page_id":"eaed354e-47cc-4e4f-b3f5-9076034f7f3d","last_edit_on":"13-11-2023 17:19","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/online-payments\/build-your-integration\/payment-result-codes","title":"Result codes","content":"When you submit a payment request, you get a result code that indicates the current status of the payment. You can use the result code to inform the shopper about the payment status. The status of a payment can sometimes change after you get the result code, so we recommend that you do not use the result code to update your order management system.\nRequirements\nBefore you begin, take into account the following requirements.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nAn online payments integration.\n\n\nAPI credential roles\nMake sure that you have the following roles: Merchant PAL webservice role Checkout webservice role\n\n\n\nGetting the result code\nHow you get the result code depends on the server-side flow that your integration uses.\n\n\n\nServer-side flow\nDescription\n\n\n\n\nSessions flow\nWhen the payment flow finishes, you get the resultCode object from Drop-in or the Component.\n\n\nAdvanced flow\nFor payments that do not require an additional action, you get the resultCode parameter in the \/payments response. For payments that require an additional action, you get the resultCode parameter in the \/payments\/details response.\n\n\n\nAuthentication-only result codes\nFor standalone authentication integrations, the result codes indicate if you need to take any action before you can proceed to authorize the payment.\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthenticationNotRequired\nThe transaction does not require 3D Secure 2 authentication. You can check the \n authenticationNotRequiredReason\n field to learn why authentication was not required.\nProceed to authorize the payment.\n\n\nAuthenticationFinished\nThe payment has been successfully authenticated with 3D Secure 2.\nCollect the 3D Secure 2 authentication data that you need to authorize the payment.\n\n\n\n3D Secure 2 authentication result codes\nFor payment flows that require 3D Secure 2 authentication, the result codes indicate the action to take to authenticate the shopper.\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nChallengeShopper\nThe issuer requires authentication from the shopper, for example, through facial recognition or entering a code received on their phone.\nInitiate the challenge flow to present the challenge to the shopper, and submit the result to Adyen.\n\n\nIdentifyShopper\nThe issuer requires authentication from the device the shopper is using.\nInitiate the frictionless flow to get the shopper's device fingerprint, and submit the result to Adyen.\n\n\nRedirectShopper\nThe issuer requires the shopper to provide authentication in an an external web page or app.\nRedirect the shopper to complete the authentication.\n\n\n\nIntermediate result codes\nFor some payment methods, you can receive an intermediate result code indicating the payment has not reached a final state yet. This happens when a payment is completed but the final status of the payment cannot be obtained, or for flows where it takes a while before the shopper can complete the payment.\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nReceived\nIndicates the payment request was successfully received by Adyen, and will be processed. This is the initial state for all payments.\nInform the shopper that you received their order, and are waiting for the final payment status.\n\n\nPending\nThe payment order was successfully received but the final status of the payment is not available yet.This is common for payment methods with an asynchronous flow.\nInform the shopper that you received their order, and are waiting for the shopper to complete the payment.\n\n\nPresentToShopper\nIndicates that there is additional information that you need to present to the shopper so that they can use it to complete a payment. For example, a voucher.\nPresent the voucher to the shopper, and inform the shopper that you are waiting for them to complete the payment.\n\n\n\nWhen the shopper has completed the payment successfully, you receive a successful AUTHORISATION webhook.\n\nFor some payments, it can take minutes, hours, or even days to be completed.\n\nPartial authorization result codes\nIf you accept partial authorizations for card payments, you receive a result code that indicates the issuing bank authorized a partial amount instead of the full order amount.\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nPartiallyAuthorised\nThe payment was authorized for a partial amount. This happens when the cardholder has insufficient funds.\nInform the shopper that their payment was partially authorized. You can now: Start a new transaction for the outstanding balance.Cancel the transaction.Capture the partial amount and take no further action.For recurring payments, retry later.\n\n\n\nFinal state result codes\nThese result codes indicate that the payment has reached a final state.\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successfully authorised.\nInform the shopper that the payment was successful. You also get a webhook with an updated payment status that you can use to update your order management system. If you are using manual capture, you also need to capture the payment.\n\n\nCancelled\nThe payment was cancelled (by either the shopper or your own system) before processing was completed.\nInform the shopper that their payment was cancelled and check if they want to continue with their order.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment.\n\n\nRefused\nThe payment was refused.\nInform the shopper that their payment was refused and ask them to try the payment again, for example, by using a different payment method or card.\n\n\n\n\nFor payments that are not Authorised, you will receive a \n refusalReason\n, indicating the cause of the error. We do not recommend disclosing this refusal reason to the shopper.\n\nNext steps\n\nTest result codesLearn how to trigger specific result codes to test how your integration handles them.\n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Build your integration","lvl3":"Result codes"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/online-payments","lvl2":"https:\/\/docs.adyen.com\/pt\/online-payments\/build-your-integration","lvl3":"\/pt\/online-payments\/build-your-integration\/payment-result-codes"},"levels":4,"category":"Online Payments","category_color":"green","tags":["Result","codes"]}}