---
title: "Ask the gateway what became of an in-progress charge"
description: "Runs the same settlement poll the billing clock runs, scoped to ONE transaction, and books whatever the gateway reports."
canonical_url: "https://twominutebilling.com/help/developers/api-reference/payment-methods/ask-the-gateway-what-became-of-an-in-progress-ch"
---
# Ask the gateway what became of an in-progress charge

> Runs the same settlement poll the billing clock runs, scoped to ONE transaction, and books whatever the gateway reports.

<api-operation method="POST" path="/v1/businesses/{biz}/transactions/{txn}/sync">
<template v-slot:docs="">

⚠️ NOT `/v1/transactions/{txn}/reconcile`, and the difference matters: that route takes an `outcome` in the body — an operator ASSERTING what happened, the last resort for a charge the gateway can no longer answer for. This one asserts nothing. Targeting bypasses the rail grace window and the recently-asked deferral, because both are the CLOCK's economy: they stop a cron spending gateway calls on rows that will not have changed, and an operator pressing this has already decided the call is worth making. `outcome` is what the pass did with the gateway's answer — `settled`, `failed`, `still_pending`, or `unsupported` when the adapter cannot be asked at all, which is never guessed at.

## Path parameters

<table>
<thead>
  <tr>
    <th>
      Parameter
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Required
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        biz
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      <strong>
        yes
      </strong>
    </td>
    
    <td>
      Business id (biz_…)
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        txn
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      <strong>
        yes
      </strong>
    </td>
    
    <td>
      The transaction's id (txn_…).
    </td>
  </tr>
</tbody>
</table>

## Headers

<table>
<thead>
  <tr>
    <th>
      Parameter
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Required
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        Idempotency-Key
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      no
    </td>
    
    <td>
      Safely retry writes — repeats return the original response. If a write FAILED after it had already taken effect, that failure is what repeats: the key is spent, and a new attempt needs a new key.
    </td>
  </tr>
</tbody>
</table>

## Status codes

<table>
<thead>
  <tr>
    <th>
      Status
    </th>
    
    <th>
      Meaning
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        200
      </code>
    </td>
    
    <td>
      What the gateway said, and the transaction as it now stands
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        403
      </code>
    </td>
    
    <td>
      Requires the ops permission
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        404
      </code>
    </td>
    
    <td>
      No such transaction
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        409
      </code>
    </td>
    
    <td>
      The transaction is not in progress, so there is nothing to ask about
    </td>
  </tr>
</tbody>
</table>
</template>

<template v-slot:request="">

```bash [Request]
curl -X POST "$TMBILLING_URL/v1/businesses/biz_XXXXXXXXXXXX01/transactions/txn_XXXXXXXXXXXX01/sync" \
  -H "Authorization: Bearer $TMBILLING_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"
```

</template>

<template v-slot:response="">
<code-group>

```json [200 OK]
{}
```

```json [403 Forbidden]
{
  "error": {
    "type": "permission_error",
    "message": "Requires the ops permission"
  }
}
```

```json [404 Not Found]
{
  "error": {
    "type": "invalid_request_error",
    "message": "No such transaction"
  }
}
```

```json [409 Conflict]
{
  "error": {
    "type": "conflict_error",
    "message": "The transaction is not in progress, so there is nothing to ask about"
  }
}
```

</code-group>
</template>
</api-operation>


## Sitemap

See the full [sitemap](https://twominutebilling.com/sitemap.md) for all pages.