qrCode<\/strong>","pm_directory":"iris","contact":"false"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/iris\/api-only","title":"IRIS for API only","content":"You can add IRIS to your existing integration. The following instructions show only what you must add to your integration specifically for IRIS.\nIf an instruction on this page corresponds with a step in the main integration guide, it includes a link to corresponding step of the main integration guide.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have an existing API-only integration.\n \n\n\nAction handling\nMake sure that your existing integration is set up to handle the additional action. action.type: redirect and qrCode.\n\n\n\nSetup steps\n - Before you begin, add IRIS in your Customer Area. - Before you can go live, request the IRIS payment method from your Greek bank, and from Adyen, by submitting your DIAS code, as well as the merchant account and the associated stores you want to have it activated on.\n\n\n\nHow it works\n\nThe shopper selects IRIS as the payment method.\nThen, there are two flows possible:\n\nIssuer-redirect: A list of issuers is shown, and the shopper selects their issuing bank. The shopper is then redirected to the issuing bank and completes the payment. The shopper is then redirected back to your page.\n\nIssuer-redirect flow is applicable to Mobile and Desktop checkout scenarios\n\nQR-code: a QR code is shown, which the shopper scans with the issuer app. The shopper completes the payment in the app on their device. You will be notified of the payment result.\n\nQR code flow is intended for Desktop only; on mobile this flow is not recommended, because often the app used for scanning the QR code resides on the same device.\n\n\nYou complete the order.\n\nBuild your payment form\nInclude fields to collect important information from your shopper in the payment form.\nFor the Issuer-redirect flow you need to show a list of issuing banks. The list of issuing banks is included in the \/paymentMethods response. The list may include the following banks:\n\n\n\nBank name\nIssuer ID\n\n\n\n\nPiraeus Bank\nPIRBGRAA\n\n\nEurobank\nERBKGRAA\n\n\nNational Bank of Greece\nETHNGRAA\n\n\nAlpha Bank\nCRBAGRAA\n\n\nViva\nPRXBGRAA\n\n\nCrediaBank\nATTIGRAA\n\n\n\n\nYou can download the logo for IRIS to use in your form.\n\nWe also provide logos for the issuing banks, which you can use on your payment form. For more information, refer to downloading logos.\nGet IRIS as an available payment method\nWhen you make the \/paymentMethods to get available payment methods, specify the following so that IRIS is included in the response.\n\n\n\nParameter\nValues\n\n\n\n\n countryCode\nGR\n\n\n amount.currency\nEUR\n\n\n\n\n \n\nThe \/paymentMethods response contains paymentMethod.type: iris, as well as the list of issuer banks.\n\n \n\nAdd additional parameters to your \/payments request\nWhen you make a payment, add the following parameters:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\n paymentMethod.type\n\niris\n\n\n returnUrl\n\nThe URL to which the shopper should be redirected after completing the payment. Required only for Issuer-redirect flow. Not required for QR code flow.\n\n\n paymentMethod.issuer\n\nThe issuer ID of the shopper's selected bank. This is only relevant (and required) for the Issuer redirect flow.If the issuer ID is included, the \/payments response will contain the redirect URL. If the issuer ID is not included, the \/payments response will contain the QR code data.\n\n\n\nIssuer-redirect flow\nThe following example shows how to make a payment request for 10 EUR, requesting the redirect flow.\n\n \n\nIn the \/payments response, note the action object. This contains the information needed 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 the following recommendations into consideration:\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\nQR code flow\nThe following example shows how to make a payment request for 10 EUR, requesting the QR code flow.\n\n \n\nIn the \/payments response, note the action object. This contains the information needed to generate the QR code.\n\n \n\nAfter initiating the payment, the shopper has 10 minutes to complete the transaction. We recommend that you show this timer to the shopper.\nPresent the QR code\nFollow these steps to render the QR code on your checkout page:\n\nUse the qrCodeData from the action object to render the QR code on your checkout page.\nAfter the shopper scans the QR code and completes the payment, we send a webhook informing you of the payment result.\nPresent the payment result to your shopper.\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper, or wait for a webhook to know the outcome of the payment.\nThe resultCode values you can receive for IRIS payments are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe shopper completed their payment, and it has been sent to the bank for processing. In most cases, this means that you will receive the funds.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on their bank's website.\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. You will receive the final result of the payment in an 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\nThe webhooks you can receive for IRIS 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\n\nIn the QR code flow, you have to wait for webhooks to know the outcome of the payment. This also applies to the Issuer redirect flow, if the shopper failed to return to your website or app.\nTest and go live\nBefore you accept live payments, test your integration using Adyen\u2019s IRIS simulator. In this simulator, the payment outcome (Successful, Refused, or Cancelled) can be selected on an Adyen-hosted page. This page will load depending on the IRIS flow:\n\nIssuer redirect flow: the page URL is in the redirect link in Adyen\u2019s \/payments response.\nQR code (Ecommerce and In-person Payments): the page URL is encoded in the QR code, which can be opened with any smartphone camera.\n\nCheck the status of IRIS test payments in your Customer Area > Transactions > Payments.\nBefore you go live, go through the onboarding steps with your Greek bank, and enable IRIS payment method for your live merchant account on Customer Area.\nSee also\n\n\n API-only integration guide\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"IRIS","lvl3":"IRIS 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\/iris","lvl3":"\/pt\/payment-methods\/iris\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":[]},"articleFiles":{"payment-methods-request.js":"payment-methods-request.js<\/p>","payment-methods-response.json":"
payment-methods-response.json<\/p>","payments-request-qr.js":"
payments-request-qr.js<\/p>","payments-request-redirect.js":"
payments-request-redirect.js<\/p>","payments-response-qr.json":"
payments-response-qr.json<\/p>","payments-response-redirect.json":"
payments-response-redirect.json<\/p>","redirect-request.js":"
redirect-request.js<\/p>","redirect-response.json":"
redirect-response.json<\/p>"}}
![\"-white_check_mark-\"](\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" "\\"-white_check_mark-\\"")
<\/td>\n