Are you looking for test card numbers?

Would you like to contact support?

Payment-method icon

Finland online banking Drop-in integration

Add Finland online banking to your existing iOS Drop-in integration.

Our iOS Drop-in renders Finland online banking in your payment form, and redirects the shopper to complete the payment. As with other redirect payment methods, you need to handle the redirect result after the shopper returns to your app.

Before you begin

This page explains how to add Finland online banking to your existing iOS Drop-in integration. The iOS Drop-in integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Drop-in integration guide.

Before starting your Finland online banking integration:

  1. Make sure that you have set up your back end implementation, and added Drop-in to your payment form.
  2. Add Finland online banking in your test Customer Area.

Show Finland online banking in your payment form

Drop-in uses the countryCode and the amount.currency from your /paymentMethods request to show the available payment methods to your shopper.

To have Drop-in render Finland online banking in your payment form, specify in your /paymentMethods request:

When the shopper selects to pay with Finland online banking, Drop-in invokes the didSubmit method. Collect the values passed in data.paymentMethod, and pass these to your server.

Make a payment

  1. From your server, make a POST /payments request, specifying:

    • paymentMethod: The data.paymentMethod from the didSubmit event from your client app.
    • returnUrl: The URL where the shopper will be redirected back to after completing the payment. Use the custom URL for your app, for example, my-app://. For more information on setting custom URL schemes, refer to the Apple Developer documentation.
    • shopperEmail: The shopper's email address. This is where Finland online banking will send the payment instructions.
    curl https://checkout-test.adyen.com/v67/payments \
    -H "x-API-key: YOUR_X-API-KEY" \
    -H "content-type: application/json" \
    -d '{
      "merchantAccount": "YOUR_MERCHANT_ACCOUNT",
      "reference": "YOUR_ORDER_NUMBER",
      "paymentMethod": {
        "type": "ebanking_FI"
      },
      "amount": {
        "currency": "EUR",
        "value": "1000"
      },
      "shopperLocale": "fi_FI",
      "countryCode": "FI",
      "telephoneNumber": "+358840839298",
      "shopperEmail": "youremail@email.com",
      "shopperName": {
        "firstName": "Testperson-fi",
        "lastName": "Approved"
      },
      "shopperReference": "YOUR_UNIQUE_SHOPPER_ID",
      "returnUrl": "my-app://"
    }'

    The /payments response contains an action object with the information needed to redirect the shopper.

    /payments response
    {
    "resultCode":"RedirectShopper",
    "action":{
      "paymentMethodType":"ebanking_FI",
      "method":"GET",
      "url":"https://checkoutshopper-test.adyen.com/checkoutshopper/checkoutPaymentRedirect?redirectData=...",
      "type":"redirect"
    }
    }
  2. Pass the action object to your client app.

Handle the redirect result

Drop-in uses dropInComponent.handle(action) to redirect the shopper to Finland online banking.  

  1. To inform Drop-in when the shopper returns to your app, implement the following in your UIApplicationDelegate:
func application(_ app: UIApplication, open url: URL, options: [UIApplicationOpenURLOptionsKey: Any] = [:]) -> Bool {
    RedirectComponent.applicationDidOpen(from: url)
    return true
}

After Drop-in completes the action, it invokes the didProvide method.

  1. From your server, make a POST /payments/details request providing the data from the didProvide method from your client app.

/payments/details request
  curl https://checkout-test.adyen.com/v67/payments/details \
  -H "x-API-key: YOUR_X-API-KEY" \
  -H "content-type: application/json" \
  -d '{
       "details": {
         "redirectResult": "eyJ0cmFuc1N0YXR1cyI6IlkifQ=="
     }
  }'

You receive a response containing:

  • resultCode: Use this to present the result to your shopper.
  • pspReference: Our unique identifier for the transaction.
    /payments/details response
    {
       "resultCode": "Authorised",
       "pspReference": "88154795347618C"
    }

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for Finland online banking are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
You will receive the funds in 3 days.
Cancelled The shopper canceled the payment while they were on the Finland online banking-hosted payment page. Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error There was an error when the payment was being processed. Inform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.
Pending or
Received
The shopper has completed the payment but the final result is not yet known. Inform the shopper that you've received their order, and are waiting for the payment to be completed.
To know the final result of the payment, wait for the AUTHORISATION notification.
Refused The payment was refused by the shopper's bank. Ask the shopper to try the payment again using a different payment method.

If the shopper failed to return to your website or app, wait for notification webhooks to know the outcome of the payment. The notification webhooks you can receive for Finland online banking are:

eventCode success field Description Action to take
AUTHORISATION false The transaction failed. Cancel the order and inform the shopper that the payment failed.
AUTHORISATION true The shopper successfully completed the payment. Inform the shopper that the payment has been successful and proceed with the order.
OFFER_CLOSED true The shopper did not complete the payment. Cancel the order and inform the shopper that the payment timed out.

Test and go live

Before accepting live payments, test your integration using the test environment and sample data provided by Paytrail.

Testing multiple partial refunds is currently not available.

See also