Payment Webhook Events

Real-Time Webhook Events for Every Payment Action

PayBito payment webhooks send instant HTTP POST notifications to your endpoint when a payment succeeds, fails, or is refunded — across Stripe, PayPal, and crypto transactions — enabling automated workflows without polling the API.

Set Up Webhooks Talk to Sales

Stripe, PayPal & Crypto Instant HTTP POST Domain Whitelisting

Real-Time Event Stream

Webhooks — Incoming Events — trade.paybito.com

Listening

2026-04-01 14:32:07 ➜ payment.success 200 OK

{
"event": "payment.success",
"payment_id": "#2180",
"amount": 149.00, "currency": "USD",
"method": "stripe"
}

2026-04-01 14:33:41 ➜ payment.success 200 OK

{
"event": "payment.success",
"payment_id": "#2182",
"amount": "0.0021 BTC", "network": "NATIVE"
}

2026-04-01 14:35:02 ➜ payment.failed 200 OK

{
"event": "payment.failed",
"payment_id": "#2185",
"reason": "card_declined"
}

API Keys & Webhooks

What It Is

Payment Webhooks: Real-Time Events Without API Polling

A payment webhook is an HTTP callback that PayBito sends to your server endpoint the moment a payment event occurs — success, failure, refund, or status change. Instead of your application repeatedly calling the PayBito API to check payment status, webhooks push the event to you instantly.

PayBito merchants configure webhook endpoints under Developers → Webhooks at trade.paybito.com. Every payment event across Stripe card processing, PayPal REST API, and crypto (Brand Wallet, External Wallets, Guest Checkout) triggers a structured JSON payload to the configured endpoint — covering one-time payments and recurring subscriptions.

Configure webhook endpoints from Developers → Webhooks in the dashboard
Events cover all payment methods: Stripe, PayPal, and 10+ crypto assets
Payload includes payment ID, amount, currency/asset, network, method, and status
Works for both one-time and recurring subscription payment events
Domain Whitelisting restricts checkout embed to authorised domains, securing the event source
Combine with named API keys for authenticated webhook delivery verification

Why Webhooks Beat Polling for Payment Events

Instant Event DeliveryPolling checks payment status on a schedule — webhooks fire the moment the event occurs. A payment.success event reaches your server in milliseconds of blockchain confirmation or card settlement.

Crypto Events Include Blockchain DetailWebhook payloads for crypto payments include the network type (NATIVE, ERC, TRC) and blockchain address — enabling your system to log on-chain references alongside the payment record.

Subscription Renewal EventsRecurring subscription billing generates events on each renewal attempt — success and failure — enabling automated provisioning, access control, and retry logic without manual intervention.

API Keys + Domain Whitelist for SecurityPair webhook endpoints with named API keys (scoped permissions) and Domain Whitelisting to verify that events originate from your authorised PayBito integration — not a spoofed source.

Event Categories

Three Core Payment Event Categories

Every payment action on PayBito generates a structured webhook event — across all payment methods and billing types.

Payment Success Events

Fired when a payment is confirmed and funds are settled — on card approval via Stripe, PayPal transaction completion, or on-chain crypto confirmation.

payment.success subscription.renewed

Stripe card payment approved and settled
PayPal payment completed via REST API
Crypto payment confirmed on-chain (BTC, ETH, USDT, +7 more)
Subscription renewal successful on any method

Payment Failure Events

Fired when a payment attempt is declined, a crypto invoice expires without payment, or a subscription renewal charge fails — enabling automated retry or access revocation workflows.

payment.failed invoice.expired subscription.failed

Stripe card declined or rejected
Crypto invoice expired without payment received
Subscription renewal failed — trigger retry logic
PayPal payment not completed by buyer

Status Change Events

Fired when a payment transitions to a new state — from processing to confirmed, or when a refund or dispute is initiated. Keeps your systems synchronised with PayBito's real-time payment state.

payment.refunded payment.processing

Refund issued and confirmed by processor
Payment entering or exiting Processing state
Event payload includes updated status and timestamp
Enables access control updates on status changes

Implementation

Webhook Endpoint Implementation Examples

PayBito webhooks deliver a standard JSON payload to any HTTP/HTTPS endpoint. Here are example handlers in two common server languages.

Node.js — Express Webhook Handler

// PayBito webhook receiver const express = require('express'); const app = express(); app.post('/webhook', (req, res) => { const event = req.body; switch (event.event) { case 'payment.success': fulfillOrder(event.payment_id); break; case 'payment.failed': notifyBuyer(event.payment_id); break; } res.status(200).send('OK'); });

Python — Flask Webhook Handler

# PayBito webhook receiver from flask import Flask, request, jsonify app = Flask(__name__) @app.route('/webhook', methods=['POST']) def webhook(): data = request.get_json() event_type = data.get('event') if event_type == 'payment.success': fulfill_order(data['payment_id']) elif event_type == 'payment.failed': notify_buyer(data['payment_id']) return jsonify({'status': 'ok'}), 200

Webhook Capabilities

Everything Developers Need for Payment Event Automation

PayBito webhooks are configured from the dashboard without writing any server-side configuration — add your endpoint URL under Developers → Webhooks and receive events for all payment channels immediately.

View Developer Docs

Unified Events Across All Payment Methods

One webhook endpoint receives events for every payment method: Stripe card payments, PayPal REST API, and crypto across BTC, ETH, BCH, LTC, XRP, USDT, DOGE, USDC, HCX, and INR — no separate webhook configurations per channel.

Crypto Events Include Network & Address

Webhook payloads for crypto transactions include the Network field (NATIVE, ERC, TRC) and the blockchain address, allowing your systems to cross-reference on-chain state or trigger network-specific workflows.

Subscription Event Lifecycle

Recurring subscription billing fires events at each renewal: subscription.success enables automated provisioning continuation; subscription.failed triggers retry or access suspension logic without manual monitoring.

Domain Whitelisting for Secure Event Sources

Configure Domain Whitelisting under Developers to ensure your embedded checkout only fires payment events from authorised domains — reducing spoofed event risk by restricting where the checkout can be loaded.

Named API Keys for Webhook Authentication

Generate named API keys under Developers → API Keys to authenticate your webhook receiver. Each key can be individually rotated or deleted without affecting other integrations — enabling safe key rotation workflows.

Test Webhook Events in Sandbox

Test User transactions in the Transactions dashboard isolate sandbox events from live data. Trigger test payment flows to validate your webhook handler logic before going live without affecting production metrics.

Setup Guide

Set Up Payment Webhooks in Five Steps

From dashboard configuration to receiving your first live event — webhook integration takes under 10 minutes.

Connect API Keys

Generate a named API key under Developers → API Keys for your integration.

Add Endpoint URL

Navigate to Developers → Webhooks and enter your HTTPS endpoint URL.

Whitelist Domains

Add your merchant domains under Domain Whitelisting for secure checkout embeds.

Deploy Receiver

Deploy your webhook handler to parse event type and payment ID from the JSON payload.

Go Live

Create a payment link — the first transaction fires a live webhook event to your endpoint.

Platform Comparison

PayBito Webhooks vs Single-Channel Processor Events

Stripe and PayPal webhooks only cover their own transactions. PayBito delivers events for all three payment channels from one endpoint.

Webhook Feature	Stripe Webhooks	PayPal Webhooks	Crypto-Only Platform
Events for All Payment Methods	Card only	PayPal only	Crypto only
Crypto Network in Event Payload			Partial
Subscription Renewal Events		Limited
Domain Whitelisting for Checkout Security	CSP only
Named API Keys (individually rotatable)		Limited	Varies
Sandbox Test Events			Varies
Unified Transaction Log Cross-Reference	Card only	PayPal only	Crypto only

Why PayBito

Payment Event Infrastructure for Multi-Channel Commerce

PayBito's webhook infrastructure is designed for developers building automated workflows across all payment methods — not just one channel.

One Endpoint, Every Channel

Stripe card, PayPal, and crypto events all arrive at the same webhook URL. Your event handler uses a single event.type switch to process all payment outcomes without managing multiple integrations.

Zero Polling Overhead

No scheduled jobs, no cron-based status checks, no rate limit concerns from API polling. Payment events push to your server the moment they occur — reducing infrastructure complexity and latency.

Full Crypto Event Detail

Crypto webhook payloads include the asset (BTC, ETH, USDT, etc.), network (NATIVE/ERC/TRC), and blockchain address — giving your system everything needed to log and verify on-chain settlement without additional explorer calls.

Secure by Default

Named API keys for authentication, Domain Whitelisting to restrict checkout origins, and individually rotatable keys mean your webhook infrastructure maintains a minimal attack surface from day one.

Subscription Lifecycle Automation

Build fully automated subscription SaaS: provision access on renewal.success, suspend on renewal.failed, and retry on the next billing cycle — without any manual monitoring or cron jobs.

Cross-Reference with Transaction Log

Every webhook event carries the Payment ID matching the entry in the Transactions dashboard. Debug failed events by cross-referencing the full transaction record, blockchain address, and status history.

Download the Mobile Apps

Contact Us

Your Name

Phone Number

Your Mail

Your Subject

(Max 120 Character)

Your message

(Max 500 Character)

By checking this box, you agree to receive SMS messages from PayBitoPro. Reply STOP to opt out at any time. Reply HELP for customer care contact information. Message and data rates may apply. Message frequency may vary. Phone numbers collected for SMS consent will not be shared with third parties or affiliates for marketing purposes under any circumstance. Check out our Privacy Policy to learn more.