---
title: "Walley Redirect Component"
description: "Add Walley to an existing Components integration."
url: "https://docs.adyen.com/payment-methods/walley/android-component"
source_url: "https://docs.adyen.com/payment-methods/walley/android-component.md"
canonical: "https://docs.adyen.com/payment-methods/walley/android-component"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# Walley Redirect Component

Add Walley to an existing Components integration.

[View source](/payment-methods/walley/android-component.md)

**If you are using Android Components v5.0.0 or later:**

This payment method requires no additional configuration.

Follow the [Components integration guide](/online-payments/build-your-integration/sessions-flow?platform=Android\&integration=Components) and use the following module and Component names:

* To [import the module](/online-payments/build-your-integration/sessions-flow/?platform=Android\&integration=Components#import): **instant**
* To [launch and show the Component](/online-payments/build-your-integration/sessions-flow?platform=Android\&integration=Components#launch-and-show): **InstantPaymentComponent**

You do not need to collect any information from your shopper in your payments form. If you have an existing [Android Components](/online-payments/build-your-integration/sessions-flow?platform=Android\&integration=Components) integration, you can use our Redirect Component to redirect the shopper to complete the payment. As with other redirect payment methods, you need to [handle the redirect](#handle-the-redirect) after the shopper returns to your app.

## Requirements

| Requirement          | Description                                                                                                                                                                                                                                 |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Integration type** | Make sure that you have built your [Components integration](/online-payments/build-your-integration/sessions-flow?platform=Android\&integration=Components%2F%3Ftarget%3D_blank). Walley for Android works with all versions of Components. |
| **Setup steps**      | Before you begin, contact our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to add Walley in your test Customer Area.                                                                                  |

## Show Walley in your payment form

You do not need to collect any information from the shopper in your payment form. To show **walley** for business-to-consumer and **walley\_b2b** for business-to-business in the list of available payment methods:

1. Use the following table to specify parameters in a [/paymentMethods](https://docs.adyen.com/api-explorer/Checkout/latest/post/paymentMethods) request:

   | Country/region | `countryCode` | `amount.currency` |
   | -------------- | ------------- | ----------------- |
   | Denmark        | **DK**        | **DKK**           |
   | Finland        | **FI**        | **EUR**           |
   | Norway         | **NO**        | **NOK**           |
   | Sweden         | **SE**        | **SEK**           |

   Also specify `channel`: **android**.

Payments in Denmark (**DK**) or with the **DKK** currency are available only for *B2C* payments.

### API response

The response contains `paymentMethod.type`: **walley** for business-to-consumer and `paymentMethod.type`: **walley\_b2b** for business-to-business.

Adyen provides a logo for Walley that you can use on your payment form. For more information, refer to [Downloading logos](/online-payments/build-your-integration/advanced-flow?platform=Web\&integration=API%20only\&version=71#downloading-logos).

## Make a payment

When the shopper proceeds to pay, the Component returns the `paymentComponentState.data.paymentMethod`.

1. From your server, make a [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) request, specifying:

   * `paymentMethod.type`: **walley**. The API response contains **paymentMethod.type: walley** for business-to-consumer, and **paymentMethod.type: walley\_b2b** for business-to-business.
   * `returnURL`: The URL the shopper is redirected to after they complete the payment. This URL can have a maximum of 1024 characters. Get this URL from the Component in the `RedirectComponent.getReturnUrl(context)`.

   In the [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) response, check the `action` object for the information that you must use to redirect the shopper.

   **/payments response**

   ```json
   {
     "resultCode":"RedirectShopper",
     "action":{
       "paymentMethodType":"walley",
       "method":"GET",
       "url":"https://checkoutshopper-test.adyen.com/checkoutshopper/checkoutPaymentRedirect?redirectData=...",
       "type":"redirect"
     }
   }
   ```

2) Pass the `action` object to your client app. You need this to initialize the Redirect Component.

## Handle the redirect

1. Use the [Redirect Component](/online-payments/build-your-integration/sessions-flow/?platform=Android\&integration=Components#handle-a-redirect) to redirect the shopper to Walley's website where they can provide their account details. When the shopper returns to your app, the Redirect Component provides the `actionComponentData` object.

2. After the shopper returns to your app, make a POST [/payments/details](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments/details) request from your server, providing:

   * `details`: The `actionComponentData.details` object from the Redirect Component.

**/payments/details request**

```bash
curl https://checkout-test.adyen.com/v72/payments/details \
-H 'x-api-key: ADYEN_API_KEY' \
-H 'content-type: application/json' \
-d '{
     "details": {
       "redirectResult": "eyJ0cmFuc1N0YXR1cyI6IlkifQ=="
   }
}'
```

You receive a response containing:

* `resultCode`: Use this to present the payment result to your shopper.
* `pspReference`: Our unique identifier for the transaction.

**/payments/details response**

```json
{
      "resultCode": "Authorised",
      "pspReference": "PPKFQ89R6QRXGN82"
}
```

## Show the payment result

1. Use the `resultCode` that you received in the [/payments/details](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments/details) response to present the payment result to your shopper.

You can receive the following `resultCode` values for Walley:

| resultCode                  | Description                                                                                                                                                                                                                                         | Action to take                                                                                                                                                                                                                         |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authorised**              | The 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. If you are using manual capture, you also need to [capture the payment](/online-payments/capture). | Inform the shopper that the payment has been successful.                                                                                                                                                                               |
| **Cancelled**               | The shopper cancelled the payment while on their bank's website.                                                                                                                                                                                    | 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 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](/development-resources/webhooks/webhook-types). |
| **Refused**                 | The payment was refused by the shopper's bank.                                                                                                                                                                                                      | Ask the shopper to try the payment again using a different payment method.                                                                                                                                                             |

You also receive the outcome of the payment asynchronously in a [webhook](/development-resources/webhooks). If the shopper failed to return to your website or app, wait for notification webhooks to know the outcome of the payment. You can receive the following notification webhooks for Walley:

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

## Test and go live

You can perform the test scenarios described on [Walley's technical documentation](https://dev.walleypay.com/docs/checkout/test-data) using Adyen's [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) endpoint. Consider the following:

* Include the `CivRegNo` as the [socialSecurityNumber](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments#request-socialSecurityNumber).
* When testing a Walley B2B transaction, provide the company information as shown in the following example:
  ```json
  "company": {
      "name": "Adyen N.V.",
      "registrationNumber": "5562000116"
  }
  ```

Check the status of Walley verification payments in your **Customer Area** > **Transactions** > **Payments**.

## See also

* [Android Components integration guide](/online-payments/build-your-integration/sessions-flow?platform=Android\&integration=Components)
* [Webhooks](/development-resources/webhooks)
* [Tokenization for recurring payments](/online-payments/tokenization)
* [API Explorer](https://docs.adyen.com/api-explorer/#/CheckoutService/latest/overview)
