IRIS for API only

You can add IRIS to your existing integration. The following instructions show only what you must add to your integration specifically for IRIS.

If 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.

Requirements

How it works

1. The shopper selects IRIS as the payment method.
2. Then, there are two flows possible:
   • Issuer-redirect: A list of issuers is shown, and the shopper selects their issuing bank. The shopper is then redirected to his issuer and completes the payment. He is then redirected back to your page.
     • Issuer-redirect flow is applicable to Mobile and Desktop checkout scenarios
   • QR-code: a QR code is shown, which the shopper scans with his issuer app. He completes the payment in his app. You will be notified of the payment result.
     • QR 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.
3. You complete the order.

Build your payment form

Include fields to collect important information from your shopper in the payment form.

For 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:

We also provide logos for the issuing banks, which you can use on your payment form. For more information, refer to downloading logos.

Get IRIS as an available payment method

When you make the /paymentMethods to get available payment methods, specify the following so that IRIS is included in the response.

The /paymentMethods response contains paymentMethod.type: iris, as well as the list of issuer banks.

Add additional parameters to your /payments request

When you make a payment, add the following parameters:

Parameter	Required	Description
paymentMethod.type		iris
returnUrl		The URL to which the shopper should be redirected after completing the payment. Required only for Issuer-redirect flow. Not required for QR code flow.
paymentMethod.issuer		The 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.

Issuer-redirect flow

The following example shows how to make a payment request for 10 EUR, requesting the redirect flow.

In the /payments response, note the action object. This contains the information needed to redirect the shopper.

Handle the redirect

1. To complete the payment, redirect the shopper to the action.url returned in the /payments response, taking the following recommendations into consideration:

   • When using the HTTP GET method:
     For 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.

   • Redirection for mobile integrations:
     For 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.

2. After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:

   • details: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.

In the response note the following:

• resultCode: use this to present the result to your shopper.
• pspReference: our unique identifier for the transaction.

QR code flow

The following example shows how to make a payment request for 10 EUR, requesting the QR code flow.

In the /payments response, note the action object. This contains the information needed to generate the QR code.

After initiating the payment, the shopper has 10 minutes to complete the transaction. We recommend that you show this timer to the shopper.

Present the QR code

Follow these steps to render the QR code on your checkout page:

1. Use the qrCodeData from the action object to render the QR code on your checkout page.
2. After the shopper scans the QR code and completes the payment, we send a webhook informing you of the payment result.
3. Present the payment result to your shopper.

Present the payment result

Use 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.

The resultCode values you can receive for IRIS payments are:

The webhooks you can receive for IRIS are:

In 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.

Test and go live

Before you accept live payments, test your integration using the following:

Check the status of IRIS test payments in your Customer Area > Transactions > Payments.

Before 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.

See also