Payment · Capture · Completed
Receive a verified PAYMENT.CAPTURE.COMPLETED event for the connected PayPal REST app. Approved orders and pending captures do not start this workflow.
Workflow template
Keep a Slack channel informed when PayPal reports a completed payment capture. Send its ID, gross amount, currency and capture time without copying payer details or purchase contents.
How it works
Receive a verified PAYMENT.CAPTURE.COMPLETED event for the connected PayPal REST app. Approved orders and pending captures do not start this workflow.
Post the capture ID, status, original gross amount and currency, capture creation time and webhook event ID as plain text in your chosen Slack channel.
The result
PayPal capture completed Capture ID: FICTIONAL-CAPTURE-42 Status: COMPLETED Gross amount: 49.90 EUR Capture created (UTC): 2026-09-19T09:00:00Z Webhook event ID: WH-FICTIONAL-CAPTURE-42 Capture-event notification; not a receipt or settlement confirmation.
Fictional payment data. Channel readers can see the included capture metadata; payer names, addresses, payment instruments and purchase contents stay in PayPal.
Before activation
Connect the REST app that receives your completed captures. Use a Sandbox app for testing, and wait until the trigger connection is ready before creating a fictional payment.
Connect Slack, select a channel where FastHook can post and review who can read it. Keep plain-text formatting and link/media previews disabled.
Activate the workflow, complete a fictional Sandbox capture and compare the resulting Slack message with the PayPal capture ID, amount, currency and timestamp. An order approval alone is not enough.
Amounts keep their original meaning. The gross amount is copied as a decimal string in its original currency, without division by 100 or currency conversion. Capture creation time is not settlement time.
Only capture metadata is posted. Payer names, email and postal addresses, payment instruments and purchase descriptions are not copied. Choose a Slack channel whose members are allowed to see the remaining capture metadata.
Notifications are not a payment ledger. Existing captures are not imported. Refunds, reversals, disputes and later changes do not update the message. This workflow does not create payments, capture money or issue refunds.
Separate captures can create separate messages. One order can have more than one capture. Manual reruns or ambiguous Slack posting failures can duplicate a notification. Formatting and link/media previews are disabled.
No. The trigger requires PAYMENT.CAPTURE.COMPLETED for the connected REST app. Pending captures, authorizations and legacy sale events are not included.
No. It contains the capture ID, completed status, gross amount, currency, capture creation time and webhook event ID. Payer details and purchase contents are not copied.
Yes. Connect a PayPal Sandbox app and complete a fictional Sandbox payment. Wait for the trigger to be ready first, and verify the Slack result against that Sandbox capture.
No. This is a one-way completed-capture notification. Refunds, reversals, disputes and later changes do not update it, and the message is not a receipt, settlement confirmation or accounting ledger.