Connecting your store and payment provider is how UMAP360 learns about real money: orders placed, payments captured, and refunds issued. Once Shopify and Razorpay are connected, your revenue and recovery numbers stop being estimates and start reflecting what actually happened — tied back to the customers who bought.

Why connect these first

Most of UMAP360's value comes from knowing who bought what, and for how much. Connecting your store and payments early means:

  • Real revenue, not guesses — orders and payments flow in directly from the source.
  • Recovery numbers you can trust — abandoned-checkout and win-back campaigns are measured against actual purchases.
  • Customers, not anonymous rows — orders and payments are matched to the people in your account, so spend and behaviour line up.

Where to start

If you only connect two things to begin with, make them your store and your payment provider. That's the fastest path to live revenue data. See the connecting your data overview for the bigger picture.

Connect Shopify (your store)

Shopify sends UMAP360 your orders and customers as they happen, so new and updated orders show up without you exporting anything.

To connect:

  1. Go to Connectors and click Shopify.
  2. Enter your Shopify store URL.
  3. In your Shopify admin, open Settings → Notifications → Webhooks and add webhooks for Order creation, Order updated, Customer creation, and Customer update, using the webhook URL UMAP360 provides.
  4. Back in UMAP360, click Verify Connection.

Grab the URL on the final step

UMAP360 generates your unique webhook URL — with a copy button — on the last step of the setup, after you click Connect. Copy it there and paste it into Shopify.

Once connected, UMAP360 brings in new and updated orders and customer profile updates. Product and refund events from Shopify aren't used, so you don't need to add those webhook topics.

Connect Razorpay (your payments)

Razorpay sends UMAP360 your payments, refunds, and subscription activity as events occur — so captured payments and refunds are reflected quickly in your numbers.

To connect:

  1. Go to Connectors and click Razorpay.
  2. In your Razorpay Dashboard, open Settings → Webhooks and add a new webhook with the URL UMAP360 provides. Select these events: payment.captured, payment.failed, refund.created, and subscription.activated.
  3. Enter your Razorpay Webhook Secret in UMAP360.
  4. Click Verify Connection.

As with Shopify, your unique webhook URL appears — with a copy button — on the final step after you click Connect.

Once connected, UMAP360 imports payment events, transaction details, subscription status, and refund data.

Webhook secret keeps it secure

The webhook secret lets UMAP360 confirm that incoming events genuinely came from Razorpay. Enter it exactly as shown in your Razorpay Dashboard, or verification will fail.

What you'll see once connected

After either connector is set up, its card on the Connectors page shows you at a glance how things are flowing:

What you seeWhat it tells you
StatusConnected, disconnected, or in an error state
Last SyncWhen data most recently came through
Data FlowRecords received in the last 24 hours
ErrorsA count of any sync problems

New orders and payments arrive on their own as they happen — there's nothing to refresh or pull manually. Your credentials are stored securely and encrypted.

If something looks off

  • Card shows "Disconnected" — reopen the connector and re-verify; double-check the webhook URL was pasted correctly in Shopify or Razorpay.
  • Data isn't arriving — confirm the webhook URL in the third-party platform matches the one UMAP360 gave you, and review the connector's errors for details.
  • Duplicate orders or payments — make sure you don't have the same event configured under more than one webhook.

For more, see connector health and troubleshooting.

Next steps

Last updated 2026-06-11

We use cookies for analytics — to understand how visitors use UMAP360 and improve the product. Essential cookies (session, forms) always run; analytics cookies wait for your call. See cookie policy.