Charge lifecycle

Charge lifecycle

A charge is asynchronous. After you create it (POST /crypto/v2/synthetics/charge), the synthetic waits for the payer's deposit and then executes the remaining stages automatically. Track the outcome through the SYNTHETIC_STATUS_UPDATE webhook or by polling the synthetic.

Prerequisites

  • A configured webhook endpoint for SYNTHETIC_STATUS_UPDATE. See Webhooks.
  • A created charge via POST /crypto/v2/synthetics/charge.

Statuses

StatusTerminalDescription
STARTINGNoJust created; the first stage has not started yet
ACTIVENoAt least one stage is in progress
WAITINGNoWaiting for the next stage's execution time
PAUSEDNoManually paused
COMPLETEDYesAll stages completed successfully
CANCELLEDYesCancelled

The typical flow is STARTING → ACTIVE → COMPLETED.

[STARTING] ──► [ACTIVE] ──► [COMPLETED]
                  │           (terminal)
                  ▼
              [CANCELLED]
               (terminal)

Stages

Stage typeRequiredDescription
DEPOSITYesWaits for the payer's deposit. Always the first stage and the trigger.
ORDERNoConverts the entryAsset into the exitAsset. Added only when they differ.
WITHDRAWNoSettles the proceeds to the destination. Added only when a destination was provided.

Confirmation

Once the payer pays, the synthetic advances and you receive a SYNTHETIC_STATUS_UPDATE webhook with the status change. This is the recommended way to follow a charge in real time. Treat COMPLETED as success and CANCELLED as a terminal close point.

SYNTHETIC_STATUS_UPDATE payload example

A completed ARS → USDT charge (paid via QR, settled to a crypto wallet):

{
  "event": "SYNTHETIC_STATUS_UPDATE",
  "data": {
    "id": "6a1eee5f36723d2aa07a9442",
    "numberId": "37771",
    "externalId": "ext-charge-003",
    "userId": "6a1241e189b656b5cbd6ae65",
    "userNumberId": "100102635",
    "userExternalId": "your-external-id",
    "status": "COMPLETED",
    "type": "CHARGE",
    "details": {
      "depositAddresses": {
        "QR3": {
          "type": "QR",
          "code": "00020101021243480011dev.manteca...",
          "url": "https://widget.manteca.dev/qr?code=00020101021243480011dev.manteca...",
          "expiresAt": "2026-06-02T11:58:19.134-03:00"
        }
      },
      "entryAsset": "ARS",
      "entryAmount": "7461.40",
      "exitAsset": "USDT",
      "exitAmount": "10.00000000",
      "paymentPrice": "746.14",
      "priceExpireAt": "2026-06-02T12:14:18.342-03:00"
    },
    "currentStage": 4,
    "stages": {
      "1": { "stageType": "DEPOSIT", "asset": "ARS", "thresholdAmount": "7461.40", "detectedAmount": "7461.40" },
      "2": { "stageType": "ORDER", "side": "BUY", "type": "MARKET", "asset": "USDT", "against": "ARS", "assetAmount": "10.00000000", "price": "746.14" },
      "3": { "stageType": "WITHDRAW", "asset": "USDT", "amount": "10.00000000", "destination": { "network": "POLYGON", "address": "0x4cD0820ca71Bda1A6cEfe1A6D5a2F6E50D4370f2" } }
    },
    "payload": { "description": "Invoice #42", "metadata": "order-42" },
    "creationTime": "2026-06-02T11:53:19.146-03:00",
    "updatedAt": "2026-06-02T11:53:52.432-03:00"
  }
}

If you cannot receive webhooks, poll GET /crypto/v2/synthetics/{syntheticAnyId}, which returns the same synthetic object found in the webhook's data.


Monitoring

EntityPrimary webhookTerminal statusesPrimary query
SyntheticSYNTHETIC_STATUS_UPDATECOMPLETED, CANCELLEDGET /crypto/v2/synthetics/{syntheticAnyId}

Integration recommendations

  1. Treat the webhook as the primary signal; re-fetch the synthetic by ID before closing your record.
  2. Use externalId to correlate the charge with your system.
  3. Present details.depositAddresses to the payer right after creation, and respect the lock validity (priceExpireAt / the lock's expireAt).
  4. Treat COMPLETED as success and CANCELLED as terminal; stop polling on either.


Did this page help you?