Skip to content

Suggested

API Dashboard

RecipesCapture and reconcile

Capture and reconcile

Capture a created payment and mirror the final state in your system.

Creating a payment only records the instruction. Capture tells Conomy to commit the movement and start provider processing. Reconciliation is the step where your system mirrors the final state from webhooks or reads.

Attention

Do not treat CAPTURED as final success. It means the movement was committed. Use terminal states such as SETTLED, FAILED, EXPIRED, UNSETTLED, or refund events to close your business workflow.

01
Create payment

Receive the payment ID.

02
Authorize if needed

Some rails reserve funds before capture.

03
Capture

Commit the movement.

04
Read state

Fetch payment state when the user returns.

05
Mirror final event

Use webhooks as the durable source of truth.

Request
POST /sandbox/payments/{PAYMENT_ID}/captured HTTP/1.1
Host: api.conomyhq.com
x-api-key: {YOUR_API_KEY}
Authorization: Bearer {ACCESS_TOKEN}
conomyhq-api-version: 24-04-2025
User-Agent: MyApp/1.0
Content-Type: application/json
Accept: application/json

{}
Response
{
  "id": "<PAYMENT_ID>",
  "status": "CAPTURED",
  "capturedAt": "2026-05-18T10:00:00Z"
}

Use this when the customer returns to your product or an operator opens a transaction detail page.

Request
GET /sandbox/payments/{PAYMENT_ID} HTTP/1.1
Host: api.conomyhq.com
x-api-key: {YOUR_API_KEY}
Authorization: Bearer {ACCESS_TOKEN}
conomyhq-api-version: 24-04-2025
User-Agent: MyApp/1.0
Accept: application/json
Response
{
  "id": "<PAYMENT_ID>",
  "externalId": "order-1001",
  "type": "PURCHASE",
  "status": "SETTLED",
  "product": "CLP:CLP",
  "purchaseAmount": "49990",
  "purchaseCurrency": "CLP",
  "currency": "CLP",
  "capturedAt": "2026-05-18T10:00:00Z",
  "settledAt": "2026-05-18T10:02:11Z"
}

Use payment.id as your transaction key and store the latest known state. If the same webhook arrives twice, update the same row and return 2xx.