Introduction

This guide explains how to configure PayPal Complete Payments services in Intershop Commerce Management (ICM). This guide is intended for administrators who manage payment services for an ICM channel.

The PayPal Complete Payments Connector provides the following payment services:

• PayPal

• PayPal Express Checkout

• Credit Card

• Apple Pay

• Google Pay

You configure each required payment service separately. All services use the shared PayPal Common Configuration.

References

• Guide - PPCP Onboarding

Initial Considerations

The payment services require a configured PayPal Common Configuration service. See Guide - PPCP Onboarding.

Configure the payment services within the service configuration of the channel that uses the payment method. Configuring a service does not necessarily make it available in the storefront. PayPal must also enable the payment methods for the merchant, depending on the contract.

Prerequisites

Before you configure a payment service:

• Complete the merchant onboarding in the PayPal Common Configuration.

• Use only one active PayPal Common Configuration for the channel.

• Confirm that you are working in the intended Sandbox or Production environment.

• Confirm that PayPal has enabled the required payment method for the merchant account.

PayPal controls merchant eligibility and payment method availability. A valid service configuration in ICM therefore does not guarantee that customers can use the payment method in the storefront.

Open the Integration tab of the PayPal Common Configuration. ICM then loads the latest configuration from PayPal.

Configuring a Payment Service

Configure each payment service in the channel that uses the corresponding payment method.

1. Open the organization in ICM.

2. Open the required channel.

3. Go to Services.

4. Create or open the required PayPal payment service.

5. Configure the settings described in this guide.

6. Activate the service.

7. Save the configuration.

8. Complete the payment method setup for the storefront.

Repeat these steps for each required PayPal payment service.

Configuration Settings

The following table explains the available settings. ICM displays only the settings supported by the selected service.

Selecting the Capture Mode

Enable Auto Capture when authorization and capture occur as one operation.

Disable Auto Capture when you want to capture the payment later. For example, capture the payment after shipment. You must then trigger capture. As long as ICM is the leading system for order handling this can be done through the payment management functions in ICM. ICM supports full and partial refunds after capture.

Allowing Address Updates

Enable Allow PayPal Address Update when buyers can select or update an address at PayPal.

PayPal can return the selected address to ICM during checkout. This option has limitations when an order uses multiple shipping addresses or shipping buckets.

Test the required address scenarios before enabling the option in Production.

Configuring Digital Goods

Enable Digital Goods for payment services that process baskets with digital products.

The connector supports payments for digital goods. The current Intershop Progressive Web App (PWA) does not fully support every digital goods scenario. Verify the complete checkout and fulfillment process before using this option in Production.

Transferring Order Details

The Transfer Order Details setting provides these options:

PayPal processes monetary values with two decimal places. ICM can calculate prices and discounts with greater precision.

These differences can produce a rounding mismatch. PayPal can reject an order when the detailed values do not match the total.

The connector validates the detailed values before transmission. If the values do not match, the connector automatically sends only the total amount. This fallback allows the buyer to continue the checkout.

Configuring 3-D Secure

The 3-D Secure settings apply only to Credit Card.

PayPal performs the 3-D Secure authentication and returns the result to ICM. ICM does not change this result. The selected rule set determines whether ICM continues with payment authorization.

Select one of these rule sets:

• Recommended Rules: The connector applies its predefined evaluation rules.

• Advanced Rules: You define which unsuccessful or incomplete authentication outcomes ICM accepts.

Accepting an outcome allows ICM to continue with authorization. The card issuer can still decline the authorization.

Use Recommended Rules unless your organization has defined specific risk requirements. Coordinate Advanced Rules with your fraud and risk management team.

Understanding Liability

A successful 3-D Secure authentication can transfer fraud-related chargeback liability to the card issuer.

PayPal returns one of these liability results:

• Possible: Liability can transfer to the card issuer.

• No: Liability remains with the merchant.

• Unknown: PayPal cannot determine liability because authentication is unavailable or incomplete.

The advanced settings mainly cover cases without a confirmed liability shift. Accepting such an outcome can leave chargeback liability with the merchant.

Advanced 3-D Secure Rules

The following table explains the outcomes displayed in ICM:

The Authentication System Error outcome combines PayPal responses with different recommendations. Some responses permit authorization. Other responses require another authentication attempt. Accept this outcome only when your risk policy permits both cases.

For the response values and recommendations, see PayPal Documentation | 3D Secure Response Parameters.

Verifying the Configuration

Verify each service in the same environment as its PayPal Common Configuration.

1. Confirm that the service is active.

2. Confirm that the payment method appears in the intended storefront.

3. Place a test order.

4. Verify the authorization and capture behavior.

5. Verify the order details displayed at PayPal.

6. For Credit Card only: Test the required 3-D Secure outcomes.

7. Verify a refund after successful capture.

Sandbox and Production use separate PayPal accounts, permissions, capabilities, and transaction data. Repeat the configuration and verification for each environment.