PayPal Drop-in integration

On this page, you can find additional configuration for adding PayPal to your Drop-in integration.

Before you begin

This page assumes you've already:

• Built a Drop-in integration.
• Added PayPal in your Customer Area.

Create developer and sandbox accounts

To test your integration, you need a PayPal developer account. Under your developer account you create a PayPal sandbox environment and a PayPal Business and Personal sandbox account to test payments.

1. Create a PayPal developer account, if you don't already have one.
2. Under your developer account, create PayPal Business and Personal sandbox accounts.
   To be able to see your test payments later, it is important that you create your sandbox accounts under your PayPal developer account.

See the PayPal sandbox testing guide for more information.
The following table shows the PayPal accounts that you need for your test integration:

Set up third-party API access on your PayPal account

To connect your PayPal account to your Adyen integration, you have to grant third-party permissions to Adyen in your PayPal Business account. To do that:

Get your PayPal Merchant ID

When you add PayPal as a payment method in your Customer Area, you need to provide your PayPal Merchant ID. Your PayPal Merchant ID is generated when you create your test and your live PayPal Business accounts, and consists of 13 randomly generated alphanumeric characters.

Set up the PayPal payment method

When you add PayPal to your test Customer Area, you will be asked to provide:

• Your PayPal email address. Use your test PayPal Business email address, for example ending in @business.example.com.
• Your PayPal account ID. Use your test PayPal Merchant ID.
• Whether you want to enable authorisation first, and capture the payment later. By default, payments will be captured immediately after authorisation. Check this box only if payments should not be captured immediately.

API reference

You don't need to send additional fields for PayPal. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:

• /sessions: This is the default with Drop-in v5.0.0 or later.
• /payments: If you implemented an additional use case.

Drop-in configuration

Required configuration

Select which endpoint you're integrating:

/sessions /payments

/sessions /payments

This is the default with Drop-in v5.0.0 or later.
There's no additional configuration you need to include for PayPal.

If you implemented an additional use case.

Parameter name	Required	Description
amount		The currency and value of the transaction.
countryCode		The shopper's country code.

Include the parameters when creating an object for the global configuration of your Drop-in integration.

AdyenCheckout configuration

const configuration = {
    // ...  other required configuration
    environment: "test", // Change this to "live" when you're ready to accept live PayPal payments.
    countryCode: "NL", // Only needed for test. When live, this is retrieved automatically.
    amount: {
        currency: "EUR",
        value: 1000
    },
    countryCode: "NL" // Only needed for test. When live, this is retrieved automatically.
};

https://docs.adyen.com/pt/pt/payment-methods/paypal/web-drop-in#-code-adyencheckout-code-configuration

Drop-in v3.13.0 or earlier

For Drop-in v3.13.0 or earlier, you must also provide the following parameters in the payment method configuration.

Parameter name	Required	Description
configuration.merchantId		Your PayPal Merchant ID.
configuration.intent		Set to authorize if you don't want to immediately capture the funds. The default value is capture.

The following example shows additional required configuration Drop-in if you're using v3.13.0 or earlier.

const paypalConfiguration = {
    configuration: {
        merchantId: "YOUR_PAYPAL_MERCHANT_ID",
        //Your PayPal Merchant ID. To find your ID, see the section Get your PayPal Merchant ID on this page.
        intent: "authorize"
    }
};

Include the paypalConfiguration object when creating a configuration object:

AdyenCheckout configuration

const configuration = {
  // ...  other required configuration
  paymentMethodsConfiguration: {
    paypal: paypalConfiguration
  }
};

https://docs.adyen.com/pt/pt/payment-methods/paypal/web-component#-code-adyencheckout-code-configuration

Optional configuration

When creating an instance of Drop-in, you can also:

• Add a Content Security Policy (CSP) nonce
• Customize the layout of the PayPal Smart Payment Buttons.
• Handle shipping changes.
• Validate user input.
• Disable the PayPal Credit button.
• Disable the PayPal PayLater button

From v5.34.0 onwards, you can also set the intent for individual payments

Content Security Policy (CSP) nonce

You can include a cspNonce to add a CSP nonce if you use this on your site. This was added in v5.2.0.

Layout

You can configure the layout of the PayPal Smart Payment Buttons. To do that, configure the style element in the PayPal payment method configuration. Use the available style options.

Shipping changes

You can use PayPal's callback method onShippingChange to listen to shipping address changes, validate that you support the shipping address, and update shipping costs.

Validate user input

You can validate user input with the following parameters:

• onInit: Called when the button renders.
• onClick: Called when one of the PayPal buttons is clicked.

Disable PayPal Credit

You can use blockPayPalCreditButton to control rendering the PayPal Credit button. Set this parameter to true if you don't want the PayPal Credit button to be rendered. The default value is false.

Disable PayPal PayLater

You can use blockPayPalPayLaterButton to control rendering the PayPal PayLater button. Set this parameter to true if you don't want the PayPal PayLater button to be rendered. The default value is false.

Example

const paypalConfiguration = {
  style: { // Optional configuration for PayPal payment buttons.
      layout: "vertical",
      color: "blue"
  },
  cspNonce: "MY_CSP_NONCE",
  onShippingChange: function(data, actions) {
      // Listen to shipping changes.
  },
  onInit: (data, actions) => {
      // onInit is called when the button first renders.
      // Call actions.enable() to enable the button.
      actions.enable();
      // Or actions.disable() to disable it.
  },
  onClick: () => {
      // onClick is called when the button is clicked.
  },
  blockPayPalCreditButton: true,
  blockPayPalPayLaterButton: true
};

Set the intent for individual payments

You can use intent to determine when the funds are captured and whether the payment details are tokenized:

• capture: authorizes and capture immediately.
• authorize: authorizes immediately and captures later.
• subscription: specifies this is a subscription payment.
• tokenize: specifies this is a billing payment.

Example

const paypalConfiguration = {
    intent: "authorize"
};

Recurring payments

Enable recurring payments

To enable recurring payments for PayPal:

1. Contact PayPal Support to enable Reference Transactions on your seller account. For this, you will need your Merchant ID.
2. Enable the recurring permissions on your PayPal account. Follow the steps described in the third-party API permission setup section, and also grant the permissions Charge an existing customer based on a prior transaction and Create and manage Recurring Payments.

Configure webhooks

You can get details about recurring payments in the AUTHORISATION and RECURRING_CONTRACT webhooks.

AUTHORISATION webhook

To receive the recurring.recurringDetailReference and the recurring.shopperReference in the additionalDetails of the AUTHORISATION webhook:

1. Log in to your Customer Area with your company-level account.
2. Go to Developers > Additional data.
3. Under Payment, select Recurring details.

RECURRING_CONTRACT webhook

Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks.

For instructions, see non-default event codes and additional settings.

Make a recurring payment

You can make recurring payments once you've enabled recurring payments on your PayPal account, and configured webhooks. To do this:

1. Create a shopper token.
2. Use the token to make future payments for the shopper.

Create a token

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

• storePaymentMethod: true
• shopperReference: Your unique identifier for the shopper.
• When making a zero-auth transaction with amount.value: 0, you must also include shopperEmail .

When the payment has been settled, you receive a webhook containing:

• eventCode: RECURRING_CONTRACT
• originalReference: The pspReference of the initial payment.
• pspReference: This is the token that you need to make recurring payments for this shopper.

Make a payment with a token

To make a payment with the token, include in your /payments request:

• paymentMethod.storedPaymentMethodId: The pspReference from the RECURRING_CONTRACT.
  You can also get this value by using the /listRecurringDetails endpoint.
• shopperReference: The unique shopper identifier that you specified when creating the token.
• shopperInteraction: ContAuth.
• recurringProcessingModel: CardOnFile, Subscription or UnscheduledCardOnFile.

For more information about the shopperInteraction and recurringProcessingModel fields, refer to Recurring transaction types.

Set up PayPal Seller Protection

If you participate in the PayPal Seller Protection program, make sure that you submit the following fields in your payment requests:

• deliveryAddress
• shopperName

The details provided in these fields will populate the Ship to section of the PayPal checkout.
We recommend that you check that your setup is working correctly with a test payment. Make sure that you submit the correct fields, and that the test payment is marked as eligible for PayPal Seller Protection in the transaction details.

Test and go live

Test your integration

When you are done setting up your integration, use your PayPal developer sandbox accounts to test the PayPal Smart Payment Buttons payment flow. There are two types of accounts that you'll use to test how your integration handles the flow:

• Business: used to simulate your role as a merchant when testing payments.
• Personal: used to simulate the role of a shopper when testing payments.

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

Before you go live

Create a live account

For live operations, you will need another PayPal Business account. To create one:

1. Go to the PayPal website, select Sign Up and follow the instructions.
   We strongly recommend that you use a generic company email address for your live PayPal Business account instead of a personal email address. This is to prevent having to configure a new account for your business in the future, should the personal email address no longer be in use for any reason. The email address for your live PayPal Business account will also be displayed on the payment receipt the shopper receives from PayPal.
2. After you create your live Business account, make sure to activate it.

To set up your live PayPal Business account:

1. Log in to your live PayPal Business account.
2. Grant third-party access on your live account.
3. Retrieve your live PayPal Merchant ID.

Add PayPal to your live Customer Area

1. Add PayPal to your live Customer Area. Provide:
   • Your email address. Use your live PayPal Business email address.
   • Your account ID. Use your live PayPal Merchant ID.
   • Whether you want to enable authorisation first, and capture the payment later. By default, payments will be captured immediately after authorisation. Check this box only if payments should not be captured immediately.

In the live environment, note that PayPal will only be available if:

• The shopper is logged in to their PayPal account.
• The shopper has at least one valid payment method on their PayPal account.

See also