Are you looking for test card numbers?

Would you like to contact support?

Payment-method icon

Apple Pay Component

Add Apple Pay to an existing Components integration.

Our Apple Pay Component renders Apple Pay in your payment form. When the shopper selects Apple Pay, the Component invokes the payment sheet where shoppers select the card they want to use, provide contact details and shipping address, and then authenticate the payment through Face ID or Touch ID.

Before you begin

This page explains how to add Apple Pay to your existing Web Components integration. The Web 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 Apple Pay integration:

  1. Make sure that you have set up your back end implementation, and created an instance of AdyenCheckout.
  2. Add Apple Pay in your test Customer Area.
  3. Contact Support Team to enable Apple Pay for your account, and provide the domain names and shop name that you want to use.

You don't need an Apple Developer account to use our built-in Apple Pay enablement. If you want to integrate with your own Apple Developer account, follow our instructions on enabling Apple Pay.

Show Apple Pay in your payment form

After you have finished enabling Apple Pay, you can present the Apple Pay Component in your payment form:

  1. Make a POST /paymentMethods request specifying:

  1. Pass the full response from the /paymentMethods call as the paymentMethodsResponse object when creating an instance of the AdyenCheckout.

  2. Add the Apple Pay Component:

    a. Create a DOM element, placing it where you want the Apple Pay button to be rendered:

    <div id="applepay-container"></div>

    b. Create an instance of the Apple Pay Component, specifying:

    • currencyCode: The three-character currency code.
    • amount: The amount of the transaction.
    • countryCode: The two-letter country code of your merchant account.
    • onValidateMerchant OPTIONAL: Optional from v3.16.0. Event called when the payment sheet is displayed. If you don't call onValidateMerchant manually, we call the event by default. Follow the code samples to learn how to call onValidateMerchant manually. For more information, see Apple Pay documentation.
    • If you are using an Apple Pay Web Component version earlier than v3.17.1:
      • configuration.merchantName: The merchant name that you want displayed on the Apple Pay payment sheet.
      • configuration.merchantIdentifier: Your Apple Merchant ID.

    We will call the onValidateMerchant event by default. If you want to make the call manually, you can do so as well (as shown in the following code sample).

    Component configuration
    const appleNode = document.getElementById("applepay-field");
    const applepay = checkout.create("applepay", {
        currencyCode: "EUR",
        amount: 1000,
        countryCode: "DE",
        configuration: {
           // Required for Component versions earlier than 3.17.1. Name to be displayed on the form.
           merchantName: "Adyen Test merchant",
           // Required for Component versions earlier than 3.17.1. Your Apple merchant identifier as described in
           merchantIdentifier: "adyen.test.merchant"
        // Button config
        // Optional. The type of button you want to be displayed in the payments form
        buttonType: "plain",
        // Optional. Specify the color of the button
        buttonColor: "black",
        onValidateMerchant: (resolve, reject, validationURL) => {
          // Optional. Call your server, passing the URL from the validationURL attribute.
          // Your server uses the validation URL to request a session from the Apple Pay server.
          // Call resolve(MERCHANTSESSION) or reject() to complete merchant validation.
            .then(response => {
              // Complete merchant validation with resolve(MERCHANTSESSION) after receiving an opaque merchant session object, MerchantSession
            .catch(error => {
              // Complete merchant validation with reject() if any error occurs
        // You can optionally override the onSubmit or onChange already defined in your AdyenCheckout instance
        onChange: (state, component) => {
          // Call your server to make `/payments` request
            .then(response => {
              // Your function to show the final result to the shopper
            .catch(error => {
              throw Error(error);

    c. Check whether Apple Pay is available to the shopper. If it is, mount the Component:

    Do not mount the Component if Apple Pay is not available to the shopper.

        .then(() => {
        .catch(e => {
            // Apple Pay is not available

Optional Component configuration

With the Apple Pay Component, you can also:

  • Configure the appearance of the Apple Pay button.
  • Include additional data such as transaction information, fields for billing and shipping contact information.
  • Add logic for specific events on your payment form.

Button configuration

Configuration object Description
buttonType The type of button you want displayed on your payments form. Possible values:
- plain: Apple Pay
- buy: Buy with Apple Pay
- donate: Donate with Apple Pay
- check-out: Check out with Apple Pay
- book: Book with Apple Pay
- subscribe: Subscribe with Apple Pay
buttonColor Specify the color of the button you want displayed on the payment form. Possible values:
- black: Black button
- white: White button with no outline
- white-with-line: White button with black outline

Payment request data

Payment request data Configuration object Description
Transaction information version Check the Apple Pay on the Web documentation for version features and compatibility details. Possible values:
  • Version 3: Default. Available in macOS 10.13 and iOS 11.
  • Version 4: Required if you want to use Apple Pay with Maestro. Available in macOS 10.14.1 and iOS 12.1.
totalPriceStatus Default value is final. Indicate if the line item is final or pending.
totalPriceLabel String. Description of the line item.
lineItems A set of line items that explain recurring payments, additional charges, and discounts. Refer to Apple Pay documentation for sample values.
merchantCapabilities Payment capabilities supported by the merchant. Default value is [`supports3DS`]. Refer to Apple Pay documentation for other options.
shippingMethods List of available methods for shipping physical goods. Refer to Apple Pay documentation for sample values.
shippingType Optional value that indicates how purchased items are to be shipped. Refer to Apple Pay documentation for available options.
supportedCountries Specify the ISO 3166 country codes if you only support payments from cards issued in specific countries.
supportedNetworks The payment networks you support, for example, visa. Refer to Apple Pay documentation for more information.
Requested billing and shipping contact information requiredBillingContactFields Billing information fields that you require from the shopper to process the transaction. Refer to Apple Pay documentation for sample values.
requiredShippingContactFields Shipping information fields that you require from the shopper to fulfill the order. Refer to Apple Pay documentation for sample values.
Known contact information billingContact Set an up-to-date billing contact information for the shopper.
shippingContact Set an up-to-date shipping contact information for the shopper.
Custom data applicationData A Base64-encoded string used to contain your application-specific data. For example, a shopping cart identifier or an order number that you will need to identify this transaction.


The following event handlers are supported for Apple Pay. Select the event handler names to see the related Apple Pay documentation.

onChange or onSubmit
Called after the shopper authorizes the payment with Apple Pay. The first parameter (state) of this function contains all the necessary data to make a payment using the /payments API.
Called when the shopper clicks the Google Pay button. Call resolve() to continue or reject() stop the payment flow. You must create the ApplePay session from a user gesture handler.
onValidateMerchant Called when the payment sheet is displayed.
onAuthorized Also called after the shopper authorizes the payment with Apple Pay. This contains all the raw event from Apple Pay.
onPaymentMethodSelected Called when the shopper selects a new payment method.
onShippingContactSelected Called when the shopper selects a shipping contact.
onShippingMethodSelected Called when the shopper selects a shipping method.
Apple Pay events
    //onSubmit or onChange defined in your AdyenCheckout instance
    const applepay = checkout.create("applepay", {
        onValidateMerchant: (resolve, reject, validationURL) => {
        // Calls your server with validationURL, which then requests a payment session from Apple Pay servers.
        // Your server then receives the session and calls resolve(MERCHANTSESSION) or reject() to complete merchant validation.

        onAuthorized: (resolve, reject, event) => {},

        * @param resolve(ApplePayPaymentMethodUpdate update) Completes the selection of a payment method with an update. This will call /applepaysession/1777995-completepaymentmethodselection.
        * @param reject(ApplePayPaymentMethodUpdate update)
        * @param event The event parameter contains the paymentMethod attribute.
        onPaymentMethodSelected: (resolve, reject, event) => {},

        * @param resolve(ApplePayShippingContactUpdate update) Completes the selection of a shipping contact with an update. This will call
        * @param reject(ApplePayShippingContactUpdate update)
        * @param event The event parameter contains the shippingContact attribute.
        onShippingContactSelected: (resolve, reject, event) => {},

        * @param resolve(ApplePayShippingMethodUpdate update) Completes the selection of a shipping method with an update. Will call
        * @param reject(ApplePayShippingMethodUpdate update)
        * @param event The event parameter contains the shippingMethod attribute.
        onShippingMethodSelected: (resolve, reject, event) => {}

Make a payment

When the shopper selects to pay, the Component calls the onChange event, which contains a

  1. If state.isValid is true, collect the and pass this to your server.

  2. From your server, make a /payments, specifying:

    • paymentMethod: The from the onChange event from your front end.
    curl \
    -H "x-API-key: YOUR_X-API-KEY" \
    -H "content-type: application/json" \
    -d '{
      "{ from onChange or onSubmit}paymentMethod{/hint}":{
        "applePayToken": "QWIwMmI0YzAhQlFBQkFnQjMv.."
    # Set your X-API-KEY with the API key from the Customer Area.
    adyen =
    adyen.api_key = "YOUR_X-API-KEY"
    response = adyen.checkout.payments({
      :amount => {
        :currency => "EUR",
        :value => 1000
      :reference => "YOUR_ORDER_NUMBER",
      :paymentMethod => {
        :type => "applepay",
        :applePayToken => "QWIwMmI0YzAhQlFBQkFnQjMv.."
      :merchantAccount => "YOUR_MERCHANT_ACCOUNT"
    // Set YOUR_X-API-KEY with the API key from the Customer Area.
    // Change to Environment.LIVE and add the Live URL prefix when you're ready to accept live payments.
        Client client = new Client("YOUR_X-API-KEY", Environment.TEST);
        Checkout checkout = new Checkout(client);
        PaymentsRequest paymentsRequest = new PaymentsRequest();
        String merchantAccount = "YOUR_MERCHANT_ACCOUNT";
        Amount amount = new Amount();
        ApplePayDetails applePayDetails = new ApplePayDetails();
        PaymentsResponse paymentsResponse = checkout.payments(paymentsRequest);
    // Set your X-API-KEY with the API key from the Customer Area.
    $client = new \Adyen\Client();
    $service = new \Adyen\Service\Checkout($client);
    $params = array(
      "amount" => array(
        "currency" => "EUR",
        "value" => 1000
      "reference" => "YOUR_ORDER_NUMBER",
      "paymentMethod" => array(
        "type" => "applepay",
        "applePayToken" => "QWIwMmI0YzAhQlFBQkFnQjMv.."
      "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': {
          'type': 'applepay',
          'applePayToken': 'QWIwMmI0YzAhQlFBQkFnQjMv..'
       '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{
      Type = "applepay",
      ApplePayToken = "QWIwMmI0YzAhQlFBQkFnQjMv.."
    var paymentRequest = new Adyen.Model.Checkout.PaymentRequest
      Reference = "YOUR_ORDER_NUMBER",
      Amount = amount,
      MerchantAccount = "YOUR_MERCHANT_ACCOUNT",
      PaymentMethod = details
    var paymentResponse = checkout.Payments(paymentsRequest);
    // Set your X-API-KEY with the API key from the Customer Area.
    const {Client, Config, CheckoutAPI} = require('@adyen/api-library');
    const config = new Config();
    // Set your X-API-KEY with the API key from the Customer Area.
    config.apiKey = '[API_KEY]';
    config.merchantAccount = '[YOUR_MERCHANT_ACCOUNT]';
    const client = new Client({ config });
    const checkout = new CheckoutAPI(client);
        amount: { currency: "EUR", value: 1000 },
        paymentMethod: {
            type: 'applepay',
            applePayToken: 'QWIwMmI0YzAhQlFBQkFnQjMv..'
        reference: "YOUR_ORDER_NUMBER",
        merchantAccount: config.merchantAccount
    }).then(res => res);

    The response contains the result of the payment.

    /payments response
      "pspReference": "881539337151149C",
      "resultCode": "Authorised"

Present the payment result

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

The resultCode values you can receive for Apple Pay are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
Refused The payment was refused by the shopper's bank. Ask the shopper to try the payment again using a different payment method.

Recurring payments

To make recurring Apple Pay payments, you first need to create a shopper token and then make subsequent recurring transactions with the token.

Refer to Tokenization for more information and detailed instructions.

Test and go live

Use Apple's test card numbers to test your integration.

Card Type Card number Expiry date CVC/CID
Discover 6011 0009 9446 2780 11/2022 111
Mastercard 5204 2477 5000 1471 11/2022 111
Visa 4761 1200 1000 0492 11/2022 533

For a full list of test cards and instructions how to add these to your test device, see Sandbox testing on Apple's Developer website.

Check the status of an Apple Pay test payment in your Customer Area > Transactions > Payments.

Going live

To process live Apple Pay payments, your API credential needs to have the API Clientside Encryption Payments role. You can check this in your live Customer Area or ask your Admin user to verify.

If you do not have an Apple Developer account, you will also need to follow these steps to enable Apple Pay for live transactions:

  1. Download and unzip the domain association file.
  2. Host the domain association file with the name apple-developer-merchantid-domain-association on each domain you want to use, under the following path:
  3. Send a request to our Support Team, asking them to enable Apple Pay for your live account.

See also