A payments integration is one connected gateway or shop. Each integration gets one webhook URL — paste it into the provider's dashboard and Norbix verifies the signature and normalizes every event.
Payments → Integrations.
What you can do here
The Payments Integrations list shows columns Integration Name, Gateway, and Enabled. Press Add New Integration to open the provider picker — Stripe, Paddle, Lemon Squeezy, Shopify, WooCommerce, Checkout.com, Authorize.Net, Adyen, Mollie, Braintree, or PayPal — then fill that provider's credential form (see Providers for the exact fields per gateway).
On a saved integration you can:
Test — runs automatically against the gateway's API with the stored credentials; no input needed. You then confirm delivery manually (a webhook round-trip or sandbox charge landed) to get the CONFIRMED badge.
Enable / Disable / Delete the integration. Payments has no "default integration" concept — triggers pick integrations explicitly.
Webhook URL — shown after the first save (the URL contains the integration id): <hub-url>/payments/webhooks/<accountId>/<projectId>/<gateway>/<integrationId>. Paste it into your gateway's webhook settings.
Received webhooks — the last 25 calls the gateway made to this URL, with Received, Event, Status, and Outcome columns and a Refresh button. Every outcome is logged (processed, duplicate, bad signature, unknown event) and kept for 14 days — your first stop when a gateway says it called Norbix.
Example: connecting Stripe
Pick the gateway and fill the form — for Stripe, the signing secret used to verify incoming webhooks:
The New integration form, filled.
After Save you get the integration's webhook URL — paste it into the gateway's own dashboard (for Stripe: Developers → Webhooks) and every event starts flowing in, signature-verified and normalized:
The saved integration with its webhook URL and actions.
Example: connecting PayPal
PayPal asks for your REST app Client ID, Client Secret, Environment, Webhook ID, and an optional Brand Name:
