# PayPal Payments Pro

<!-- meta: type=event-paypal; location=Custom Events; category=Trigger; platforms=Joomla and WordPress (where applicable) -->

## Overview

When it runs: PayPal notifies your site of payment lifecycle events (completed payments, disputes, subscription changes, etc.).

The flow starts with PayPal's notification payload for reconciliation or fulfillment steps.

When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the **Design** tab.

## Why use this node

PayPal Payments Pro is a **trigger** in the **Custom Events** group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.

Typical reasons teams add **PayPal Payments Pro** to a flow:

- Confirm orders when PayPal marks a payment complete
- Notify support when a dispute is opened
- Update subscription state after billing events

## When it runs

PayPal notifies your site of payment lifecycle events (completed payments, disputes, subscription changes, etc.).

## Example workflows

Common patterns on the canvas:

1. **Trigger or Webhook** → upstream steps → **PayPal Payments Pro** → **Send Email** or CMS update
2. **Scheduled trigger** → **PayPal Payments Pro** → **Debug** (while testing) → production action

## How to set it up

Connect PayPal credentials in your CMS plugin and map the fields you need downstream.

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **AI** | Optional assistant for trigger setup (paid plans) |
| **Design** | Trigger configuration, payload schema, and inbound settings |

### System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `_nodeId` | Node ID | `node-id` | No | — | — |
| `inputSchema` | Payment Payload Schema (optional) | `json-schema` (default: `[object Object]`) | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |
| `webhookId` | Webhook ID (optional) | `text` | No | — | Webhook ID from PayPal |
| `clientId` | Client ID (optional) | `text` | No | — | PayPal Client ID |
| `clientSecret` | Client Secret (optional) | `secret-text` | No | — | PayPal Client Secret |
| `verifySignature` | Verify PayPal Signature (optional) | `toggle` (default: `true`) | No | — | — |
| `requireHttps` | Require HTTPS Only (optional) | `toggle` (default: `true`) | No | — | — |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `description` | Description (optional) | `textarea` | No | — | Description of the PayPal payment event |

### CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under **Node Configuration**, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

## Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as
`{{paypal_payments_pro.event}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `event` | object | Inbound webhook event envelope. |
| `data` | object | Inbound event data payload. |

## Related nodes

Other steps in the same area of the palette:

- **Jorchestrator Cron** (`event-jorchestrator`) — Custom Events
- **Stripe** (`event-stripe`) — Custom Events
- **Webhook** (`webhook`) — Custom Events
- **Zapier Webhook** (`event-zapier`) — Custom Events