Apps & Routes

How Icone Pay is organized — and why routes let you change webhook URLs without ever contacting a provider.

Apps

An App represents one business or project. It holds your payment credentials (Moncash, Stripe), your mode (test/live), and the set of enabled payment methods. All routes under an app share the same credentials.

Routes

A Route is a channel within an app. Each route has its own:

  • API key — used to initialize payments for that channel.
  • Webhook URL — where we deliver payment events.
  • Return URL and branding (name, logo) shown on checkout.

Use multiple routes when one business has several storefronts or sites that should each receive events at their own endpoint, while sharing one set of payment credentials.

Why Routes Matter

Some providers (Moncash in particular) require you to register your callback URL with them manually, and to contact support every time it changes. Icone Pay sits in the middle: you register our URL with the provider once, then manage your real webhook and return URLs per route in the dashboard. Change them whenever you like — no provider tickets, no downtime. We receive the provider callback and forward a signed event to your route's current webhook URL.

The forwarding model is provider-agnostic — Moncash, cards and Connect all deliver to your route's webhook the same way.