Skip to main content
A webhook tells your system that something changed in Mojo Payments, as it happens, so you don’t have to keep asking. Each notification names the record and what happened to it. Your system then reads the record through the API, so it always gets the current version, even from a late or repeated notification. Integrations via iPaaS.com as a partner use webhooks this way. Any other system can too.

Set one up in the portal

Owners and Admins do this in Settings → Webhooks (under Developers).
  1. Select Set up for iPaaS.com, or Add another endpoint for any other system.
  2. Enter the URL your system gave you. Webhooks are sent over https only, to public addresses.
  3. Add any Headers your system needs, such as the AuthKey iPaaS.com issues. Values are kept encrypted. A credential is never shown again, only the last four characters of a long one: any header named like a key, token, secret, password, signature or cookie (such as AuthKey), or one you tick Secret for. Other values stay visible, so you can check and change them.
  4. Under What it hears about, tick the scopes it needs, or Everything.
  5. Leave the Body as Standard, or write your own template (below).
  6. Select Create webhook. If your system checks signatures, copy the signing secret now: it’s shown only once.
The Webhooks page: an iPaaS.com endpoint that's on, with its history of delivered notifications, and a second endpoint that's off.

Settings → Webhooks, an endpoint's history open (portal as of October 2026)

The new webhook form: name, URL, an AuthKey header, every scope ticked, and the standard body.

Setting up a webhook for iPaaS.com (portal as of October 2026)

Each endpoint has Send test, a History of the last 30 days with Send again for anything that failed, and New signing secret. Turn it off with the On box to pause it; notifications waiting to be sent are then skipped. Your system can also set itself up with an API key instead: see Set up webhooks from your system.

What a notification looks like

Mojo Payments sends a POST with a JSON body:
These headers come with every notification, with any headers of your own: Answer with any 2xx status within 15 seconds. Anything else, or no answer, is tried again after 1, 2, 4 and more minutes, then every 6 hours, 12 times in all (about a day). After that it shows as failed in the endpoint’s History, where you can send it again. Redirects aren’t followed: use the final address.

Scopes

A payment on an invoice is part of the invoice, so it’s sent as invoice/updated; it’s also a card transaction, so cardTransaction/created follows within a minute. Declined card transactions and authorizations that are never captured aren’t sent. See Card transactions. Reading a record needs an API key with the matching permission, such as payments.view (Authentication).

Your own body

For a system that expects another shape, choose My own template and write the JSON it wants. These placeholders are filled in, JSON-escaped, so put quotes around them yourself: For example, a list of notifications:

Check the signature

If your system checks where a notification came from, compute an HMAC-SHA256 of the Mojo-Webhook-Timestamp header, a dot and the raw body, keyed with the endpoint’s signing secret (whsec_…). Compare it, as lowercase hex, with what follows v1= in Mojo-Webhook-Signature, and ignore notifications more than a few minutes old.
New signing secret replaces the secret at once; update your system straight after.