PayPal – Automation Step

Overview #

The PayPal step sends a WhatsApp “Request Payment” template that contains a PayPal payment link. You choose an approved payment template, bind its custom fields either dynamically (from contact/custom fields) or statically, and optionally set the payment amount and currency.

This step requires a valid PayPal integration on your account.

---

Prerequisites #

• PayPal integration configured (account → Integrations → PayPal)
  • The step shows a warning and a Configure button if PayPal is not set up
• At least one approved WhatsApp template in the subcategory “Request Payment”

If the integration is missing or misconfigured, configure it first; otherwise the step may not be able to generate a working payment link.

---

How to Add the Step #

1. In the automation builder, click "Add Action" or the "+" button
2. Choose "PayPal"

---

Configure the Step #

The configuration has two parts: pick the template, then fill its fields.

1) Select a “Request Payment” Template #

• Click the template picker and select an approved template
• The picker filters templates to the Request Payment sub‑category
• After selection, a message preview appears with a payment amount placeholder and the message body/buttons

2) Fill Template Fields #

For each example/custom field exposed by the selected template (e.g., Amount, Link):

• Choose the value source:
  • Dynamic – Populate from contact or custom fields at send time
  • Static – Type a fixed value
• When a field is set to Static, an input appears

Special behavior:

• Amount (static): you can set an amount and select a currency (e.g., EUR, USD). The preview shows “amount currency” (e.g., 100,00 EUR).
• Link: this field is generated by the integration and is not editable in the step UI.

Validation:

• The step becomes submittable when a template is selected
• If any field is set to Static, it must have a non‑empty value

---

What Gets Sent #

• A WhatsApp template message of type “Request Payment”
• Template variables are resolved:
  • Dynamic variables are pulled from the contact/custom fields you chose
  • Static variables are taken from your inputs
• The PayPal payment link is injected automatically into the Link field by the integration

---

Best Practices #

• Keep templates concise: Clearly show amount, what it’s for, and next steps
• Prefer dynamic amounts: Pull from fields like ORDER_TOTAL or OUTSTANDING_BALANCE
• Choose the correct currency: Ensure your amount/currency pair matches your business rules
• Confirm payment: Use a Webhook step after to verify status and write an ID to a custom field
• Tag progress: Add tags such as payment_requested, payment_paid for analytics
• Handle declines: Add a follow‑up If/Else and reminder flow on non‑payment

---

Interactions With Other Steps #

• Send Webhook – Verify payment, fetch transaction details, store IDs
• Populate Contact Field – Save payment IDs/status to custom fields
• Update Ticket / Open Ticket – Escalate or resolve based on payment result
• If / Else – Branch on PAYMENT_STATUS or timeouts
• Start Automation – Kick off fulfillment once paid

---

Troubleshooting #

Warning: PayPal integration not configured #

• Click Configure to open the integration page and set PayPal email/credentials

Template not listed #

• Ensure the template is approved and categorized under Request Payment

Cannot edit the Link field #

• Expected: link is generated by the integration; only Amount and other informative fields are editable

Amount formatting looks off #

• For Static amounts, enter numeric value matching your locale format and select the correct currency

Payment not recorded #

• Add a Webhook step to your PSP/PayPal backend to confirm transaction status and then update custom fields/tickets

---