Here's a scenario that happens more often than it should. A transaction processes successfully on Startbutton. Your system is supposed to receive a webhook notification and update your order status, trigger a fulfillment flow, or log the payment in your database. Then, you encountered an issue where your server was briefly down, or the payload wasn't acknowledged or the webhook fired at the wrong time.

The transaction is fine, the money moved, but your system doesn't know that, and now you have a data gap that's blocking your reconciliation, your fulfillment, or your customer communication.

Until now, the only way to fix this was to contact Startbutton support, explain the transaction, and wait for someone on our end to manually trigger the resend. Depending on queue times, that could mean delays in your data reconciliation and extra back-and-forth that neither side needed.

We've changed that. Merchants can now resend missed webhooks directly from the Startbutton dashboard.

Who This Is For

This feature is built for any Startbutton merchant whose systems depend on webhook notifications to stay in sync with payment activity — including:

• Developers and technical teams managing webhook integrations for collections, payouts, and subscription renewals who need to recover missed payloads quickly

• Operations teams reconciling transaction data when a webhook gap has caused a mismatch between Startbutton records and internal systems

• Finance teams whose reconciliation workflows depend on real-time webhook data and can't afford to wait on a support ticket to close a gap

• Platform and marketplace operators where missed webhook notifications create downstream errors in order management, fulfillment, or vendor payout flows

• Any merchant who has ever had to contact support just to get a webhook resent for a specific transaction

What You Can Resend

The resend webhook feature works across all transaction types that generate webhook notifications on Startbutton, including:

• Collections — payment received notifications

• Payouts — transfer completion notifications

• Conversions — currency conversion settlement notifications

• Disputes — dispute status update notifications

• Subscription renewals — recurring billing confirmation notifications

One important detail worth knowing: when you resend a webhook, the system sends the latest state of the transaction — not the original payload. If a payout moved from PENDING to SUCCESSFUL between the original webhook and the resend, your system will receive the current SUCCESSFUL status. This means resending a webhook doesn't just recover a missed notification — it ensures your system gets accurate, up-to-date transaction data.

How to Resend a Webhook

There are two ways to trigger a webhook resend on Startbutton, depending on whether you're working from your transaction list or know the reference directly.

Method 1: From Your Transaction List

This is the most common path — you're reviewing your transaction history, you spot the entry for the missed webhook, and you trigger the resend directly from there.

Step 1: Log in to your Startbutton dashboard

Sign in with your account credentials and navigate to your main dashboard.

Step 2: Go to your Transactions list

Navigate to the Transactions section where your full payment activity is listed.

Step 3: Find the transaction with the missed webhook

Locate the specific transaction for which you need to resend the webhook. You can use your existing filters — date range, transaction type, status — to find it quickly.

Step 4: Click "Resend Webhook"

In the action options for that transaction — alongside the existing View and Refund options — you'll see a Resend Webhook button. Click it.

Step 5: Confirm the success notification

Once the resend is triggered successfully, you'll see a confirmation notification on your dashboard:

"Webhook successfully resent for transaction [Reference]."

Your endpoint will receive the webhook payload with the latest transaction state. Dismiss the notification, and you're done.

If the resend fails — for example, if there's an internal error or the transaction reference can't be located — you'll see a clear error message directing you to contact support. In practice, this path handles the vast majority of missed webhook scenarios without any issues.

Method 2: From the Webhook Utility Section

If you already know the transaction reference and want to trigger a resend without searching your transaction list, use the dedicated webhook utility in your dashboard settings.

Step 1: Log in to your Startbutton dashboard

Sign in and navigate to your dashboard.

Step 2: Go to Settings

From your main navigation, open the Settings menu.

Step 3: Find the Webhook utility section

Inside Settings, locate the dedicated webhook utility — a simple interface with a single input field.

Step 4: Enter your transaction reference

Type or paste the transaction reference for the webhook you need to resend into the Transaction Reference field.

Step 5: Click "Resend Webhook"

Hit the Resend Webhook button. The system validates the reference, confirms it belongs to your merchant account, and triggers the resend.

Step 6: Confirm the success notification

You'll see the same confirmation notification as Method 1 once the resend is successfully triggered.

What Happens Behind the Scenes

When you trigger a webhook resend, a few things happen automatically that are worth understanding:

Your ownership is verified. The system confirms that the transaction reference you're resending belongs to your merchant account before triggering anything. You can only resend webhooks for your own transactions.

The latest transaction state is sent. As mentioned above, the resend delivers the current state of the transaction — not a replay of the original payload. If anything changed between the original webhook and the resend, your system receives the updated information.

Every resend is logged. The system records each resend attempt — who triggered it, when, and which transaction — so there's a complete audit trail of webhook resend activity on your account.

Rate limiting applies. To prevent abuse, resends are limited to a maximum of three retries per transaction. This is more than sufficient for the vast majority of missed webhook scenarios.

Your existing webhook configuration is unchanged. This feature doesn't modify how automatic webhooks work. Every transaction continues to fire webhooks automatically as it always has. The resend capability is purely additive — it gives you a recovery tool for the cases where the automatic delivery didn't land.

A Few Scenarios Where This Saves Time

Server downtime during a high-volume period
Your endpoint goes down during a busy payment window. Several webhooks don't land. When your server comes back up, you identify the gaps in your transaction records, locate the affected transactions in your dashboard, and resend each webhook in sequence. Your system is back in sync in minutes — no support queue.

Subscription renewal sync failure
A subscription renewal processes successfully but your billing system doesn't update the customer's status because the webhook wasn't received. You resend the webhook from the transaction list, your system picks up the SUCCESSFUL renewal status, and the customer's account updates automatically.

Payout status mismatch
A payout moved from PENDING to SUCCESSFUL but your vendor management system still shows it as pending because the status-change webhook was missed. You resend from the dashboard — the system delivers the current SUCCESSFUL state — and your records update correctly. Reconciliation gap at month-end
Your finance team identifies a handful of transactions in Startbutton's records that don't appear as completed in your internal system. Rather than raising a support ticket for each one, you resend the webhooks directly from the transaction list and your system closes the gaps.

Quick Reference

Things Worth Knowing

Works in both Sandbox and Production. The webhook resend feature is available in both environments, as long as a webhook URL is already configured for your account. This means you can test the resend flow in Sandbox before relying on it in Production.

The button appears for all relevant transaction types. You don't need to navigate to a specific section for collections versus payouts. The Resend Webhook option appears in the transaction list action menu for any transaction type that generates webhook notifications.

This doesn't change your automatic webhook delivery. Every transaction still fires its webhook automatically when it processes. The resend feature is a recovery tool — not a replacement for the standard flow.

You don't need to contact support for this anymore. That's the point. If you catch yourself drafting a support message that begins with "can you please resend the webhook for..." — use the dashboard instead.