# Transaction statuses

> What each Paystack transaction status means and how to handle it in your integration.

A transaction status tells you where a payment attempt ended up, but not every status should trigger the same business action. In practice, your integration should treat status handling as a decision layer: some statuses mean you should wait, some mean you should prompt the customer to try again, and only one means you should fulfill the transaction.

<table>
<thead>
  <tr>
    <th>
      Status
    </th>
    
    <th>
      Meaning
    </th>
    
    <th>
      Action to take
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        success
      </code>
    </td>
    
    <td>
      The payment was completed successfully.
    </td>
    
    <td>
      Deliver value, mark the payment as paid, and store the confirmed record.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        failed
      </code>
    </td>
    
    <td>
      The payment attempt did not succeed. Check <code>
        data.gateway_response
      </code>
      
       for the reason.
    </td>
    
    <td>
      Do not fulfill. Show the customer an error or offer another payment attempt.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        abandoned
      </code>
    </td>
    
    <td>
      The customer left the flow or never completed the required action.
    </td>
    
    <td>
      Do not fulfill. Let the customer restart the payment if needed.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        ongoing
      </code>
    </td>
    
    <td>
      The customer is in the middle of completing an action, such as entering an OTP or making a transfer.
    </td>
    
    <td>
      Wait for a webhook or verify again later.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        pending
      </code>
    </td>
    
    <td>
      The transaction is still being processed, common with channels like bank transfer or USSD.
    </td>
    
    <td>
      Keep monitoring; do not deliver value yet.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        processing
      </code>
    </td>
    
    <td>
      Same as <code>
        pending
      </code>
      
      , for Direct Debit transactions.
    </td>
    
    <td>
      Keep monitoring; do not deliver value yet.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        queued
      </code>
    </td>
    
    <td>
      The transaction is queued for batch processing. This applies to bulk charges only.
    </td>
    
    <td>
      Wait for a later status update before taking any fulfillment action.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        timeout
      </code>
    </td>
    
    <td>
      Returned by the Charge API when a charge attempt fails.
    </td>
    
    <td>
      Do not fulfill. Show <code>
        data.message
      </code>
      
       to the customer and start a new charge if they want to retry.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        reversed
      </code>
    </td>
    
    <td>
      A completed payment was returned, refunded, or charged back.
    </td>
    
    <td>
      Reconcile your records and reverse the value you delivered if your business flow requires it.
    </td>
  </tr>
</tbody>
</table>

Only `success` means you should deliver value. A customer reaching a callback URL, seeing a pending screen, or starting a transfer is not enough on its own. `abandoned` usually means the customer exited the flow without paying, while `pending` means the customer may still complete the payment through an asynchronous channel.

When you verify a transaction, check both `status` and `amount`. A successful status confirms that money moved, but the amount confirms that the customer paid the exact value your system expects to receive.
