Search

Are you looking for test card numbers?

Would you like to contact support?

Android Components

Build your checkout form with our Android Components.

We built separate Components per payment method that you can use to render UI and collect your shopper's payment details. For more information on which payment methods have a Component, see list of Components.

If you are new to integrating with Adyen, see our Online payments page for an overview of integration options and available features.

Components is supported from v49 of the /paymentMethods, /payments, and /payments/details endpoints.

See sample code

  Check out Components on GitHub.

Whenever you want to offer a new payment method, you need to add the specific Component on your payments form. The steps for integrating each Component is similar regardless of the payment method.

On this page we talk about both server-side and client-side integration steps:

  1. From your server, submit a request to get a list of payment methods available to the shopper.
  2. Add Components to your payments form.
  3. From your server, submit a payment request with the data returned by the Component.
  4. Determine from the response if you need to perform additional actions on your client app, such as to redirect the shopper to complete the payment.
  5. From your server, submit additional payment details.
  6. Present the payment result to the shopper.

Before you begin

Before you start integrating with our online payments API and Components for Android, make sure that you have performed the following steps:

  1. Sign up for an Adyen test account.
  2. Get your API Key. Save a copy as you need it for API calls you make to the Adyen payments platform.
  3. Install one of our Libraries to connect with the Adyen APIs.
  4. If you're building for multiple merchants, provide some basic information so that we can offer you better support.
  5. Install Components for Android.

Install Android Components

Android Components are available through jcenter, you only need to add a build dependency on Gradle.

  1. Import the specific Android Component by adding it to your build.gradle file.

    Check the payment method page for the specifc Component you are adding.

    For example, to use the Card Component, add the following to your build.gradle file.

    implementation "com.adyen.checkout:card-ui:<latest-version>"
  2. To use the Redirect Component, add the following to your build.gradle file.

    implementation "com.adyen.checkout:redirect:<latest-version>"

You can check for the latest Adyen Android release version on GitHub. Once you have installed the Component, you're ready to start building your implementation.

Step 1: Get available payment methods

  1. Make a POST /paymentMethods request, providing:

    • merchantAccount: Your merchant account name.
    • countryCode: The shopper's country.
    • amount: The currency and value of the payment.
    • channel: The platform of the shopper's device. Use Android.

    We use the countryCode, amount, and channel to tailor the list of payment methods to your shopper.

    curl https://checkout-test.adyen.com/v49/paymentMethods \
    -H "x-API-key: YOUR_X-API-KEY" \
    -H "content-type: application/json" \
    -d '{
      "merchantAccount": "YOUR_MERCHANT_ACCOUNT",
      "countryCode": "NL",
      "amount": {
        "currency": "EUR",
        "value": 1000
      },
      "channel": "Android"
    }'
    # Set your X-API-KEY with the API key from the Customer Area.
    adyen = Adyen::Client.new
    adyen.api_key = "YOUR_X-API-KEY"
    
    response = adyen.checkout.payment_methods({
      :merchantAccount => 'YOUR_MERCHANT_ACCOUNT',
      :countryCode => 'NL',
      :amount => {
        :currency => 'EUR',
        :value => 1000
      },
      :channel => 'Android'
    })
    // Set your X-API-KEY with the API key from the Customer Area.
    Client client = new Client(xApiKey,Environment.TEST);
    
    Checkout checkout = new Checkout(client);
    PaymentMethodsRequest paymentMethodsRequest = new PaymentMethodsRequest();
    paymentMethodsRequest.setMerchantAccount("YOUR_MERCHANT_ACCOUNT");
    paymentMethodsRequest.setCountryCode("NL");
    Amount amount = new Amount();
    amount.setCurrency("EUR");
    amount.setValue(1000L);
    paymentMethodsRequest.setAmount(amount);
    paymentMethodsRequest.setChannel(PaymentMethodsRequest.ChannelEnum.Android);
    PaymentMethodsResponse response = checkout.paymentMethods(paymentMethodsRequest);
    // Set your X-API-KEY with the API key from the Customer Area.
    $client = new \Adyen\Client();
    $client->setXApiKey("YOUR_X-API-KEY");
    $service = new \Adyen\Service\Checkout($client);
    
    $params = array(
      "merchantAccount" => "YOUR_MERCHANT_ACCOUNT",
      "countryCode" => "NL",
      "amount" => array(
        "currency" => "EUR",
        "value" => 1000
      ),
      "channel" => "Android"
    );
    $result = $service->paymentMethods($params);
    #Set your X-API-KEY with the API key from the Customer Area.
    adyen = Adyen.Adyen()
    adyen.client.xapikey = 'YOUR_X-API-KEY'
    
    result = adyen.checkout.payment_methods({
      'merchantAccount': 'YOUR_MERCHANT_ACCOUNT',
      'countryCode': 'NL',
      'amount': {
        'value': 1000,
        'currency': 'EUR'
      },
      'channel': 'Android'
    })
    // Set your X-API-KEY with the API key from the Customer Area.
    var client = new Client ("YOUR-X-API-KEY", Environment.Test);
    var checkout = new Checkout(client);
    var amount = new Model.Checkout.Amount("EUR", 1000);
    var paymentMethodsRequest = new Model.Checkout.PaymentMethodsRequest(MerchantAccount: "YOUR_MERCHANT_ACCOUNT")
    {
       CountryCode = "NL",
       Amount = amount,
       Channel = "Android"
    };

    A list of available paymentMethods is returned in the response, including the required fields if there are any. If you want to know more about the properties returned in the response, see the response parameters on API Explorer.

    {
     "paymentMethods":[
      {
        "details":[...],
        "name":"Credit Card",
        "type":"scheme"
        ...
      },
      {
        "details":[...],
        "name":"SEPA Direct Debit",
        "type":"sepadirectdebit"
      },
      ...
      ]
    }
  2. Pass the response to your client app. You will use this in the next step to present which payment methods are available to the shopper.

Next, initialize Components on your client app.

Step 2: Initialize Components

Initialize Components to start getting your shopper's payment details on your client app. To do this, you need to:

  1. Provide the /paymentMethods response to the SERIALIZER object to deserialize the data.

    val paymentMethodsApiResponse = PaymentMethodsApiResponse.SERIALIZER.deserialize(paymentMethodsResponse)

    From the result, get the object containing the payment method type that you need. For example, to initialize the Card Component, you need to pass the object with type scheme.

    {
      "brands": [
        "mc",
        "visa",
        ...
      ],
      "details": [
        {
          "key": "number",
          "type": "text"
        },
        ...
      ],
      "name": "Credit Card",
      "type": "scheme"
    }
  2. Check specific payment method pages to confirm if you need additional required configuration and then create a Component configuration object. For example, to enable the Card Component, you need to provide your Client Side Public Key.

     val cardConfiguration =
          CardConfiguration.Builder(context, "<publicKey>")
          .setEnvironment(Environment.EUROPE)
          .build()
    // Create the configuration for the payment method that you want to add.
    // See list of Supported payment methods at https://docs.adyen.com/checkout/android/components#supported-payment-methods
  3. Initialize the Component by passing the payment method object and the configuration object if needed.

    val cardComponent = CardComponent.PROVIDER.get(this@YourActivity, paymentMethod, cardConfiguration)
      // Replace CardComponent with the payment method Component that you want to add.
      // See list of Supported payment methods at https://docs.adyen.com/checkout/android/components#supported-payment-methods
  4. Next, add the Component view to your layout.

    <com.adyen.checkout.card.CardView
           android:layout_width="wrap_content"
           android:layout_height="wrap_content"/>
    // Replace card with the Component view that you want to add.
    // See list of Supported payment methods at https://docs.adyen.com/checkout/android/components#supported-payment-methods
  5. Next, attach the Component to the view to start getting your shopper's payment details.

    cardView.attach(cardComponent, this@YourActivity)
    // Replace CardComponent with the payment method Component that you want to add.
    // See list of Supported payment methods at https://docs.adyen.com/checkout/android/components#supported-payment-methods
  6. When shoppers enter their payment details, you start receiving updates. If isValid is true and the shopper proceeds to pay, pass the paymentComponentState.data.paymentMethod to your server to make the /payments request.

    cardComponent.observe(this@MainActivity, Observer {
        if (it?.isValid == true) {
            // When the proceeds to pay, pass the `it.data` to your server to send a /payments request
        }
        // Replace CardComponent with the payment method Component that you want to add.
        // See list of Supported payment methods at https://docs.adyen.com/checkout/android/components#supported-payment-methods
    })

Next, submit a payment request from your server.

Step 3: Make a payment

  1. From your server, make a POST /payments request specifying the parameters described below, along with other parameters that might be required for your integration.

    For example, you need to include additional fields if you are implementing 3D Secure 2 native or 3D Secure redirect authentication, or if you want to tokenize the shopper's payment details for recurring payments.

    • amount
    • reference: Your unique reference for this payment.
    • paymentMethod: The paymentComponentState.data.paymentMethod from the Component.
    • returnUrl: In case of a redirection, this is the URL to where the Component should redirect the shopper back to after they complete the payment. Get this URL from the Component in the RedirectComponent.getReturnUrl(context).
    • merchantAccount: Your merchant account name.

      curl https://checkout-test.adyen.com/v49/payments \
      -H "x-API-key: YOUR_X-API-KEY" \
      -H "content-type: application/json" \
      -d '{
        "amount":{
          "currency":"EUR",
          "value":1000
        },
        "reference":"YOUR_ORDER_NUMBER",
        "paymentMethod": "COMPONENT_DATA"
        "returnUrl":"adyencheckout://your.package.name",
        "merchantAccount":"YOUR_MERCHANT_ACCOUNT"
      }'
      # Set your X-API-KEY with the API key from the Customer Area.
      adyen = Adyen::Client.new
      adyen.api_key = "YOUR_X-API-KEY"
       
      response = adyen.checkout.payments({
        :amount => {
          :currency => "EUR",
          :value => 1000
        },
        :reference => "YOUR_ORDER_NUMBER",
        :paymentMethod => "COMPONENT_DATA_PAYMENTMETHOD",
        :returnUrl => "adyencheckout://your.package.name",
        :merchantAccount => "YOUR_MERCHANT_ACCOUNT"
      })
      // Set your X-API-KEY with the API key from the Customer Area.
      Client client = new Client(xApiKey,Environment.TEST);
       
      Checkout checkout = new Checkout(client);
      PaymentsRequest paymentsRequest = new PaymentsRequest();
      paymentsRequest.setMerchantAccount("YOUR_MERCHANT_ACCOUNT");
      Amount amount = new Amount();
      amount.setCurrency("EUR");
      amount.setValue(15000L);
      paymentsRequest.setAmount(amount);
      String encryptedCardNumber = "adyenjs_0_1_18$...encryptedCardNumber";
      String encryptedExpiryMonth = "adyenjs_0_1_18$...encryptedExpiryMonth";
      String encryptedExpiryYear = "adyenjs_0_1_18$...encryptedExpiryYear";
      String encryptedSecurityCode = "adyenjs_0_1_18$...encryptedSecurityCode";
      paymentsRequest.setReference("Your order number");
      paymentsRequest.addEncryptedCardData(encryptedCardNumber,encryptedExpiryMonth, encryptedExpiryYear, encryptedSecurityCode, "John Smith");
      paymentsRequest.setReturnUrl("adyencheckout://your.package.name");
      PaymentsResponse paymentsResponse = checkout.payments(paymentsRequest);
      // Set your X-API-KEY with the API key from the Customer Area.
      $client = new \Adyen\Client();
      $client->setXApiKey("YOUR_X-API-KEY");
      $service = new \Adyen\Service\Checkout($client);
      
      $params = array(
        "amount" => array(
          "currency" => "EUR",
          "value" => 1000
        ),
        "reference" => "YOUR_ORDER_NUMBER",
        "paymentMethod" => "COMPONENT_DATA_PAYMENTMETHOD",
        "returnUrl" => "adyencheckout://your.package.name",
        "merchantAccount" => "YOUR_MERCHANT_ACCOUNT"
      );
      $result = $service->payments($params);
      #Set your X-API-KEY with the API key from the Customer Area.
      adyen = Adyen.Adyen()
      adyen.client.xapikey = 'YOUR_X-API-KEY'
      
      result = adyen.checkout.payments({
         'amount': {
            'value': 1000,
            'currency': 'EUR'
         },
         'reference': 'YOUR_ORDER_NUMBER',
         'paymentMethod': 'COMPONENT_DATA_PAYMENTMETHOD',
         'returnUrl': 'adyencheckout://your.package.name',
         'merchantAccount': 'YOUR_MERCHANT_ACCOUNT'
      })
      // Set your X-API-KEY with the API key from the Customer Area.
      var client = new Client ("YOUR_X-API-KEY", Environment.Test);
      var checkout = new Checkout(client);
      
      var amount = new Model.Checkout.Amount("EUR", 1000);
      var details = new Model.Checkout.DefaultPaymentMethodDetails{COMPONENT_DATA};
      var paymentsRequest = new Model.Checkout.PaymentRequest
      {
        Reference = "YOUR_ORDER_NUMBER",
        Amount = amount,
        ReturnUrl = @"adyencheckout://your.package.name",
        MerchantAccount = "YOUR_MERCHANT_ACCOUNT",
        PaymentMethod = details
      };
      
      var paymentResponse = checkout.Payments(paymentsRequest);

    Depending on the payment result, you receive a response containing:

    • resultCode: If the payment has been successfully completed, you get an Authorised result code. If you receive an Authorised, Error, or Refused, you can immediately present the payment result to the shopper. For more details on how to handle other resultCode values, see Result codes.
    • pspReference: Our unique identifier for the transaction.
    • refusalReason: Returned with resultCode Error or Refused. See refusal reasons for possible values.
    • action: If you get this object in the response, you need to perform additional action on your client app to complete the payment. Refer to the specific payment method page for the description of each property returned in this object.
    • paymentData: This is returned when you need to perform additional action on your client app to complete the payment. Keep a copy of the paymentData. You then need this when you submit additional payment details.

      {
      "pspReference": "88154795347618C",
      "resultCode": "Authorised"
      }
      {
      "resultCode": "RedirectShopper",
      "action": {
       "method": "POST",
       "paymentData": "Ab02b4c0!BQABAgCW5sxB4e/==",
       "paymentMethodType": "scheme",
       "type": "redirect",
       "url": "https://test.adyen.com/hpp/3d/validate.shtml",
       "data": {
         "PaReq": "eNpVUslygkAQ/RXjB8yCgEi1kyJSq..",
         "TermUrl": "https://your-company.com/...",
         "MD": "ejJydDdDeExyVUFrTEFaMTlITCt_..."
       }
      },
      "details": [
      {
       "key": "MD",
       "type": "text"
      },
      {
       "key": "PaRes",
       "type": "text"
      }
      ],
      "paymentData": "Ab02b4c0!BQABAgCW5sxB4e/=="
      }
  2. The next steps depend on if you received an action object in the response.
    • If you received an action object, you need to perform both step 4 and step 5.
    • If you did not get an action object, proceed to step 6 to present the payment result to your shopper.

Step 4: Perform additional actions on your client app

Some payment methods require additional shopper interaction before a payment can be processed. For example, for iDEAL, shoppers need to complete their payment on the issuer's website or app. For card payments, you might need to perform 3D Secure authentication before a payment can be authorised.

If an additional action is required for the payment method, the response contains an action object.

  1. Check the kind of action that you need to perform from the action.type:

    • type: This indicates the type of action to perform.

    • redirect: Redirect the shopper to a site or to another app to proceed with the payment as in the case of iDEAL or 3D Secure 1 authentication. You can either use the Redirect Component or handle the redirect on your own.
    • threeDS2Fingerprint: Perform 3D Secure 2 device fingerprinting using the 3D Secure 2 Component.
    • threeDS2Challenge:Present the 3D Secure 2 challenge to the shopper using the 3D Secure 2 Component.
    • paymentData: Keep a copy of the paymentData. You need this when you submit additional payment details.

Depending on the type, the action object also contains parameters that the specific Action Component need to perform the additional client app steps.

  1. Integrate the specific Action Component. The Action Component returns the data that you need to complete the payment.

Step 5: Submit additional payment details

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

    • details: This is the actionComponentData.details from the Component.

      curl https://checkout-test.adyen.com/v49/payments/details \
      -H "x-API-key: YOUR_X-API-KEY" \
      -H "content-type: application/json" \
      -d 'ACTION_COMPONENT_DATA'
      # Set your X-API-KEY with the API key from the Customer Area.
      adyen = Adyen::Client.new
      adyen.api_key = "YOUR_X-API-KEY"
      
      response = adyen.checkout.payments.details({
        :details => {
          :payload => "sdfsdfsdf..."
        }
      })
      // Set your X-API-KEY with the API key from the Customer Area.
      Client client = new Client(xApiKey,Environment.TEST);
      
      Checkout checkout = new Checkout(client);
      PaymentDetailsRequest paymentDetailsRequest = new PaymentDetailsRequest();
      HashMap<String, String> details = new HashMap<>();
      details.put("payload", "sdfsdfsdf...");
      paymentsDetailsRequest.setDetails(details);
      PaymentsResponse paymentsResponse = checkout.paymentDetails(PaymentDetailsRequest);
      // Set your X-API-KEY with the API key from the Customer Area.
      $client = new \Adyen\Client();
      $client->setXApiKey("YOUR_X-API-KEY");
      $service = new \Adyen\Service\Checkout($client);
      
      $params = array(
        "details" => array(
          "payload" => "sdfsdfsdf..."
        )
      );
      $result = $service->paymentDetails($params);
      #Set your X-API-KEY with the API key from the Customer Area.
      adyen = Adyen.Adyen()
      adyen.client.xapikey = 'YOUR_X-API-KEY'
      
      result = adyen.checkout.payments_details({
         'details': {
            'payload': 'sdfsdfsdf...'
         }
      })
      // Set your X-API-KEY with the API key from the Customer Area.
      var client = new Client ("YOUR_X-API-KEY", Environment.Test);
      var checkout = new Checkout(client);
      
      var details = new Dictionary<string, string>
      {
        { "payload", "Ab02b4c0..." }
      };
      var paymentsDetailsRequest = new Model.Checkout.PaymentsDetailsRequest(Details: details);
      var paymentResponse = checkout.PaymentDetails(paymentsDetailsRequest);

    Depending on the payment result, you receive a response containing:

    • resultCode: If the payment has been successfully completed, you get an Authorised result code. For other possible resultCode values and the actions that you need to take, see Result codes.
    • action: If you get this object in the response, you need to perform additional action on your client app to complete the payment.
    • pspReference: Our unique identifier for the transaction.
    • refusalReason: Returned with resultCode Error or Refused. See refusal reasons for possible values.

      {
      "pspReference": "88154795347618C",
      "resultCode": "Authorised"
      }
      {
      "pspReference": "89783918347627F",
      "refusalReason": "Not enough balance",
      "resultCode": "Refused"
      }
  2. The next steps depend on if you received an action object in the response.
    • If you received an action object, perform step 4 again.
    • If you did not get an action object, proceed to the next step to let the shopper know the status of their payment.

Step 6: Present the payment result

If you do not receive an action object from your last API request, the payment has been completed.

Use the resultCode from the response to present the payment result to your shopper on your client app. For example:

  • If you get an Authorised result code, inform the shopper that the payment has been successfully completed.
  • If you get an Error or Refused result code, inform the shopper that the payment failed.
  • If you get a Pending or Received resultCode, inform the shopper that you've received their order, and are waiting for the payment to be processed. To receive payment status updates, set up your notification webhooks to receive payment status updates.

Check out your specific payment method page for the possible result codes that you might receive, or see this list of Result codes for recommended messages that you can present to your shopper.

Action Components

You can use the following Action Components to help you perform additional required actions as described in step 4:

  • Redirect Component: Handles redirecting your shopper to another app or to a website to complete the payment. The Component also returns the information that you need to submit in your next API request.
  • 3D Secure 2 Component: Handles 3D Secure 2 device fingerprinting and 3D Secure 2 challenge flow. The Component also returns the information that you need to submit in your next API request.

Using the Redirect Component

If the Action type is redirect, initialize the Redirect Component.

  1. To use the Redirect Component, first make sure that you add the following to your build.gradle file.

    implementation "com.adyen.checkout:redirect:<latest-version>"

    You can check for the latest release version on GitHub.

  2. Next, initialize the Redirect Component.

       val redirectComponent = RedirectComponent.PROVIDER.get(this@YourActivity)
  3. Provide the action object from the /payments response.

    redirectComponent.handleAction(this@YourActivity, action)
  4. Add an IntentFilter to the Activity that will handle the returnUrl.

    <activity
        android:name=".YourActivity">
        <intent-filter>
            <action android:name="android.intent.action.VIEW"/>
    
            <category android:name="android.intent.category.DEFAULT"/>
            <category android:name="android.intent.category.BROWSABLE"/>
    
            <data
                android:host="${applicationId}"
                android:scheme="adyencheckout"/>
         </intent-filter>
    </activity>
  5. Get the result of the redirect from the Activity. Pass the intent.data back to the Redirect Component.

    override fun onNewIntent(intent: Intent?) {
           super.onNewIntent(intent)
           if (data != null && data.toString().startsWith(RedirectUtil.REDIRECT_RESULT_SCHEME)) {
               redirectComponent.handleRedirectResponse(intent.data)
           }
       }
  6. The Component notifies the observer with the information that you need to submit in a /payments/details request.

    redirectComponent.observe(this, Observer {
       // Send a /payments/details/ call containing the `actionComponentData.details`
    })

Next, pass the results to your server and perform step 5.

Using the 3D Secure 2 Component

If the Action type is threeDS2Fingerprint, initialize the 3D Secure 2 Component.

  1. To use the 3D Secure 2 Component, first make sure that you add the following to your build.gradle file.

    implementation "com.adyen.checkout:3ds2:<latest-version>"

    You can check for the latest release version on GitHub.

  2. Next, initialize the 3D Secure 2 Component.

    val threedsComponent = Adyen3DS2Component.PROVIDER.get(this@YourActivity)
  3. Provide the action object from the /payments response.

    threedsComponent.handleAction(this@YourActivity, action)
  4. The Component notifies the observer with the information that you need to submit in a /payments/details request.

    threedsComponentComponent.observe(this, Observer {
       // Send a /payments/details/ call containing the `actionComponentData.details`
    })

    Next, pass the results to your server and perform step 5.

  5. If the issuer requires further shopper interaction in a challenge flow, you might still get an action object in the /payments/details response be indicated by a threeDS2Challenge action type. To handle the challenge flow, provide the action object from the /payments/details response.

    threedsComponent.handleAction(this@YourActivity, action)
  6. The Component notifies the observer with the information that you need to submit in a /payments/details request.

      threedsComponentComponent.observe(this, Observer {
          // Send a /payments/details/ call containing the `actionComponentData.details`
      })

Next, pass the results to your server and perform step 5 again.

Customizing the UI for 3D Secure 2

The Component inherits your app's theme to ensure the UI of the challenge flow fits your app's look and feel. You can override the default theme to inherit from one of AppCompat's theme variants. To do this, add the following XML snippet to your styles.xml file.

<style name="ThreeDS2Theme" parent="Theme.AppCompat.Light.DarkActionBar">
    <!-- Customize the SDK theme here. -->
    <item name="colorPrimary">@color/colorPrimary</item>
    <item name="colorPrimaryDark">@color/colorPrimaryDark</item>
    <item name="colorAccent">@color/colorAccent</item>
</style>

Notification webhooks

Although in most cases the resultCode you received from the /payments or /payments/details endpoints already indicates the payment result, notifications are the only way to know about the outcome of a payment in cases where:

  • The resultCode is Pending or Received.
  • The shopper failed to return to your website or app.

Make sure that you set up your notification webhooks so you can receive payment status updates.

After we know the outcome of a payment, we will send you a notification containing:

  • eventCode: AUTHORISATION
  • success: Indicates the outcome of the payment. Possible values:

    • true: The payment was successful.
    • false: The payment failed.

Refer to Notification request item to see all the information returned in a notification.

Testing and going live

Before going live, use our list of test cards and other payment methods to test your integration. We recommend testing each payment method that you intend to offer to your shoppers.

You can check the status of a test payment in your Customer Area, under Transactions > Payments.

When you've completed testing, you need to complete some additional steps before you can accept live payments from shoppers. Refer to Getting started with Adyen for more information.

When you're ready to move to production, you have to switch from test to our live endpoints. See Live endpoints for more information.

Supported payment methods in Components

The following payment methods are supported in Components. If you have questions about payment methods not on the list below or those that do not have linked pages, contact our Support Team.

Payment method Web iOS Android
AfterPay -white_check_mark-
Apple Pay -white_check_mark- -white_check_mark-
BCMC Mobile -white_check_mark-
Cards, including 3D Secure 1 and 3D Secure 2
authentication
-white_check_mark- -white_check_mark- -white_check_mark-
Stored card details -white_check_mark- -white_check_mark-
Dragonpay -white_check_mark-
Dotpay -white_check_mark- -white_check_mark- -white_check_mark-
Entercash -white_check_mark- -white_check_mark- -white_check_mark-
EPS -white_check_mark- -white_check_mark- -white_check_mark-
giropay -white_check_mark-
Google Pay -white_check_mark- -white_check_mark-
iDEAL -white_check_mark- -white_check_mark- -white_check_mark-
Japanese convenience stores (Konbini)/
7-Eleven Japan
-white_check_mark-
MOLPay -white_check_mark- -white_check_mark- -white_check_mark-
Open banking -white_check_mark- -white_check_mark- -white_check_mark-
QiwiWallet -white_check_mark-
Redirect payment methods
(For example, UnionPay)
-white_check_mark- -white_check_mark- -white_check_mark-
SEPA Direct Debit -white_check_mark- -white_check_mark- -white_check_mark-
WeChat Pay -white_check_mark-

We're actively adding payment methods to Components. To check the latest on Drop-in and Components, see our release notes.

See also

Next steps