Skip to content
Notis

Unified Refund Processing: Auto-Sync Via Webhooks

Your refund processing tool sends data via webhook, and Notis instantly updates Payhip refund records. No manual transfers. No lost refunds. Everything synced automatically.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Webhook Event - Refunded Payment

Tool to process payhip's refunded webhook event. use when handling a payment refund event from payhip.

Why this helps

You process refunds in one tool but Payhip doesn't know about them. Records are out of sync, customers don't see refunds, and you're manually updating both systems.

  • Keep refund records synced across tools automatically
  • Eliminate manual refund logging
  • Reduce errors from duplicate or missed refunds
  • Give customers accurate refund status

Setup

Build it in a few focused steps.

  • 1Connect Payhip to Notis.
  • 2Create an automation: 'When I receive a webhook with refund data, update the refund record in Payhip.'
  • 3Set trigger as Notis Webhook and action as Payhip Refunded Payment.
  • 4Get the unique webhook URL from Notis and add it to your refund tool's webhook settings.
  • 5Send a test refund and verify it syncs to Payhip instantly.

Questions about this workflow

What if a refund is already in Payhip?

Notis will update it instead of creating a duplicate. This prevents double-counting or confusion.

Can I track partial refunds?

Yes, if your refund tool tracks amounts, Notis will sync the full refund amount to Payhip.

What if the webhook has incomplete data?

Notis will log what it can and alert you to missing info so you can manually complete it if needed.

Does this prevent duplicate refunds?

Largely yes. Notis checks if a refund already exists before syncing. This protects you from accidentally refunding twice.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Telegram to Payhip. A trigger fires from one place; an action lands in another.

Telegram triggers

Payhip actions

New Message Received

Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.

TriggerInstant

Webhook Event - Paid

Tool to process payhip's paid webhook event. use when handling a purchase completion webhook from payhip.

ActionInstant

New Channel Post

Triggered when a new post is published to a channel where your bot is an administrator.

TriggerInstant

Webhook Event - Refunded Payment

Tool to process payhip's refunded webhook event. use when handling a payment refund event from payhip.

ActionInstant

Callback Query Received

Triggered when a user taps an inline keyboard button attached to one of your bot's messages.

TriggerInstant

Webhook Event - Subscription Created

Tool to process payhip's subscription.created webhook event. use when handling a subscription start event from payhip.

ActionInstant

Message Edited

Triggered when a message in a chat your bot can see is edited by its sender.

TriggerInstant

Webhook Event - Subscription Deleted

Tool to process payhip's 'subscription.deleted' webhook event. use when handling a subscription cancellation event from payhip.

ActionInstant

New Chat Member

Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.

TriggerInstant

Connect any two apps with Notis in the middle.

Not just Telegram and Payhip. Any combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7 days free trial with 20$ free usage included.
No card. Works with personal or business Payhip.