JPM Payments Notifications (Webhooks)

Guide a merchant through receiving JPM webhook events. This is a sibling to jpm-merchant-integrations — it handles the inbound webhook path, not request/response REST. APIs that send notifications (Disputes, Account Updater card-registration mode, Online Payments capture/refund events, etc.) live in jpm-merchant-integrations; this skill handles receiving them.

Step 1 — Confirm prerequisites

The merchant should already have:

• Validated credentials and a working getAccessToken() (same auth module as jpm-merchant-integrations).
• A way to host a public HTTPS endpoint that JPM can POST events to. This is the hard prerequisite — JPM webhooks cannot reach a localhost dev server. Options: a deployed staging environment, a reverse proxy (ngrok / Cloudflare Tunnel) for development, or a dedicated webhook receiver in CAT infra.
• TLS at the endpoint with a publicly trusted certificate (self-signed will not work).

If auth isn't set up yet, point the merchant at jpm-integrations-get-started → jpm-oauth first and exit.