# Webhooks vs polling

> When to use each confirmation method and why webhooks are preferred.

After a customer attempts a payment, your integration still needs a dependable way to learn the final result. Paystack supports two confirmation models. With webhooks, Paystack pushes an event to your server as soon as the transaction state changes. With polling, your server keeps asking the verify endpoint for an update until it gets a final answer. Both can work, but they solve different problems. For where confirmation fits in the payment lifecycle, see [Payment flow](/payments/concepts/payment-flow).

Webhooks are the preferred approach because they are event-driven and fit the way payments actually behave. Some channels complete immediately, while others can take time because they depend on an external action such as a bank transfer, USSD approval, or another asynchronous confirmation step. A webhook lets Paystack notify your system when the final state is known, so you do not have to guess when to check again. In production, this reduces latency, avoids unnecessary API requests, and gives you a more reliable source of truth for fulfillment.

Polling the verify endpoint is usually simpler to understand at first because your server stays in control of the loop. That makes it useful as a fallback when you are debugging, handling a one-off manual check, or adding a backup confirmation path. The tradeoff is that polling introduces delay, consumes more requests, and can still miss the moment an asynchronous payment completes unless you keep checking for long enough. It should support your webhook strategy, not replace it.

No matter which approach you use, treat security as part of confirmation. When your server receives a webhook event, [verify the `Paystack-Signature` header](/developer-tools/integration/webhooks#verify-webhook-signatures) with your webhook signing secret before you trust the payload. That check ensures the event really came from Paystack and prevents your system from acting on forged payment notifications.

<table>
<thead>
  <tr>
    <th>
      Dimension
    </th>
    
    <th>
      Webhooks
    </th>
    
    <th>
      Polling
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Timing
    </td>
    
    <td>
      Paystack sends updates as soon as the event happens
    </td>
    
    <td>
      Your server learns the result only when it checks
    </td>
  </tr>
  
  <tr>
    <td>
      Reliability
    </td>
    
    <td>
      Better for production because it follows real payment events
    </td>
    
    <td>
      Depends on your retry interval and how long you keep checking
    </td>
  </tr>
  
  <tr>
    <td>
      Async support
    </td>
    
    <td>
      Strong fit for bank transfer, USSD, and other delayed channels
    </td>
    
    <td>
      Easy to stop checking too early for async payments
    </td>
  </tr>
  
  <tr>
    <td>
      Complexity
    </td>
    
    <td>
      Requires a public endpoint and signature verification
    </td>
    
    <td>
      Simpler to start with, but harder to make efficient at scale
    </td>
  </tr>
</tbody>
</table>

<callout type="info">

Use webhooks as the primary confirmation path in production, and keep the verify endpoint as a fallback for reconciliation, debugging, or recovery flows.

</callout>
