No momento, esta página não está disponível em português
Payment-method icon

Card Component v4.x.x integration

Add card payments to your existing Components integration.

Our Card Component renders the available cards in your payment form, and securely collects sensitive card information, so it doesn't touch your server.

Before you begin

This page explains how to add cards to your existing Android Components integration. The Android Components integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Components integration guide.

Before starting your integration:

  1. Make sure that you have set up your back end implementation for making API requests.
  2. Add the cards that you want to accept in your test Customer Area.
  3. Get your client key: 1. Log in to your Customer Area.
  4. Go to Developers > API credentials, and select the credential username for your integration, for example ws@Company.[YourCompanyAccount].
  5. Under Client settings > Authentication select the Client key tab.
  6. Select Generate client key.
  7. Select the copy icon and store your client key securely in your system.
  8. Under Add allowed origins, enter your domains and select Add.
  9. Select Save changes.

Show the available cards in your payment form

For information about the supported countries and currencies for each card, refer to Payment methods.

To show the Card Component in your payment form, you need to:

  1. Specify in your /paymentMethods request a combination of countryCode and amount.currency. This is used to determine which cards are available to the shopper.

  2. Deserialize the /paymentMethods response, and get the object with type: scheme.
    For showing stored cards, get the object with type: storedPaymentMethods.

  3. Add the Card Component:

    a. Import the Card Component to your build.gradle file.

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

    For the latest version, refer to our GitHub.

    b. Create a cardConfiguration object, and pass your client key. You can also include optional configuration, for example to make the cardholder name required.

     val cardConfiguration = CardConfiguration.Builder(context, "YOUR_CLIENT_KEY")
          // Makes the cardholder name required
          // When you're ready to accept live payments, change the value to one of our live environments.

    c. Initialize the Card Component. Pass the object from the /paymentMethods response and the cardConfiguration object.

       val cardComponent = CardComponent.PROVIDER.get(this@YourActivity, paymentMethod, cardConfiguration)

    d. Add the Card Component view to your layout.


    e. Attach the Component to the view to start getting your shopper's payment details.

       cardView.attach(cardComponent, this@YourActivity)

    f. When shoppers enter their payment details, you start receiving updates. If isValid is true and the shopper proceeds to pay, pass the to your server and make a payment request.

     cardComponent.observe(this) { paymentComponentState ->
        if (paymentComponentState?.isValid == true) {
           // When the shopper proceeds to pay, pass the `` to your server to send a /payments request

Optional configuration

When you create the CardConfiguration object, you can optionally add configuration parameters.

Address field configuration

Configure the postal code field in AddressConfiguration.PostalCode.

Include the following parameter:

Parameter Description Default value
addressFieldPolicy Set if shoppers are required to fill in the fields.
Possible values:
- Required
- Optional
- OptionalForCardTypes: include the brand parameter, which is a list of values of type String to specify which brands input is optional for.

Make a payment

When the shopper proceeds to pay, the Component returns the

  1. Pass the to your server.
  2. From your server, make a /payments request, specifying:

    • paymentMethod: The from your client app.

The /payments response contains:

  • pspReference: Our unique identifier for the transaction.
  • resultCode: Use this to present the payment result to your shopper.
  • merchantReference: The reference from the /payments request.
  • additionalData: Additional information about the transaction.
    To specify the fields that you want to receive in additionalData, log in to your Customer Area, and go to Developers > Additional data.

Present the payment result

Use the  resultCode from the /payments response to present the payment result to your shopper. You will also receive the outcome of the payment asynchronously in a webhook.

For card payments, you can receive the following resultCode values:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
If you are using manual capture, you also need to capture the payment.
Cancelled The shopper cancelled the payment. 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. For more information, check the refusalReason field. Inform the shopper that there was an error processing their payment.
Refused The payment was refused. For more information, check the refusalReason field. Ask the shopper to try the payment again using a different payment method.

Additional resultCode values are possible in case of the 3D Secure authentication flow. For more information, refer to Result codes.

Recurring payments

Adyen's tokenization service allows you to securely store shopper's card details for recurring payments. To make recurring payments, you first need to create a shopper token, and then use the token to make future payments for the shopper.

Create a token

When a shopper chooses to pay with card, the Card Component renders a switch for saving the card details for future payments. If a shopper selects this option, the paymentComponentState from the Component will include data.storePaymentMethod. Pass this to your server.

To create a token, include in your /payments request:

  • storePaymentMethod: The from your client app.
  • shopperReference: Your unique identifier for the shopper.

If you don't want to show the switch for saving card details, set showStoredPaymentMethods to false when creating the cardConfiguration object:

     val cardConfiguration = CardConfiguration.Builder(context, "YOUR_CLIENT_KEY")
          // hides the switch for saving card details

Show a stored card in your payment form

When the shopper proceeds to pay, the Component returns the

  1. Pass the to your server.
  2. From your server, make a /payments request, specifying:

    • paymentMethod: The from your client app.

    • shopperReference: The unique shopper identifier that you specified when creating the token.
    • shopperInteractionContAuth.
    • recurringProcessingModel: CardOnFile.

The /payments response contains:

  • resultCode: Use this to inform the shopper about the payment status.

You can also use tokens to make shopper-not-present payments for subscriptions or contracts. For more information, refer to Making a payment for a subscription or contract.

Test and go live

If your client-side integration isn't ready, you can test API requests with encrypted card details by adding a test_ prefix to the test card details.

Before making live card payments:

  1. Test your integration using our test card numbers. You can check the status of test payments in your Customer Area > Transactions > Payments.

  2. Add the cards that you want to accept in your live Customer Area.

  3. Configure the Component using the client key from your live Customer Area.

  4. Before you can start accepting card payments in the live environment, you need to assess your PCI DSS compliance and submit the required Self-Assessment Questionnaire A document. For more information, refer to PCI DSS compliance guide.

See also