Mint cAROUSD

Minting converts public stablecoin into cAROUSD at 1:1; after a mint, value that used to be visible on-chain becomes an encrypted balance. Minting requires a custodial wallet: AroPay signs the on-chain calls with the wallet’s key.

Prerequisites

A custodial wallet with ETH for gas (faucet covers this).
In backed mode, the wallet must also hold enough public stablecoin to deposit. In float mode the operator mints directly, so a stablecoin balance in your wallet is not required. See mint modes.

Make the call

curl -s "$BASE/mint" \
  -H "Authorization: Bearer $KEY" \
  -H "content-type: application/json" \
  -d "{\"walletId\":\"$WALLET\",\"amount\":\"100\"}"

{
  "ok": true,
  "data": {
    "transaction": {
      "id": "cktxn0002…",
      "type": "MINT",
      "status": "QUEUED",
      "amount": "100.00",
      "token": "cAROUSD",
      "txHash": null,
      "explorerUrl": null,
      "error": null,
      "errorCode": null,
      "walletId": "ckwlt0001…",
      "createdAt": "2026-08-13T09:40:00.000Z",
      "updatedAt": "2026-08-13T09:40:00.000Z"
    }
  }
}

amount is a required decimal string in human units. The call returns 201 as soon as the request is validated and queued; a background worker encrypts, signs, and submits the mint (PENDING, txHash set) and confirmation usually lands within a minute. Poll GET /transactions/{id} until the status is CONFIRMED or FAILED.

What happens on-chain

Backed mode
Float mode

Your wallet approves the commitment contract to spend the stablecoin.
The wallet calls commitDeposit: stablecoin is locked in the commitment, and the equivalent cAROUSD is minted to the wallet as an encrypted amount.

Every cAROUSD in circulation is collateralized by stablecoin held in the contract.

The operator calls confidentialMint for your wallet with the encrypted amount. Your stablecoin balance is untouched; the operator’s float backs redemptions instead.

Either way, the encryption of the minted amount happens server-side, in the background worker: you send "100", AroPay produces the FHE ciphertext and proof after the request has already returned.

Verify

curl -s "$BASE/balances?walletId=$WALLET" -H "Authorization: Bearer $KEY" \
  | jq '.data.balances[0] | {normal: .normal.amount, confidential: .confidential.amount}'

In backed mode you’ll see normal decrease and confidential increase by the minted amount; in float mode only confidential moves.

Common failures

Problems with the request itself fail the POST; problems executing on-chain fail the transaction row later (status: "FAILED", with error and errorCode). Either way, a failed mint moved no funds.

Response	Meaning
`400 validation_error` / `invalid_amount`	Missing or malformed `amount`.
`400 wallet_not_custodial`	`walletId` refers to an external (watch-only) wallet.
`400 insufficient_stable` (backed mode)	The wallet’s public stablecoin balance is below `amount` at request time.
`404 not_found`	Unknown wallet.
`503 fhe_*` / `stable_misconfigured`	Platform configuration problem; nothing was queued.
`FAILED` with `errorCode: "insufficient_stable"`	Backed mode: the balance dropped below `amount` (e.g. a competing transfer) before the worker submitted.
`FAILED` with `errorCode: "mint_failed"`	The on-chain call reverted. In float mode this usually means the operator is missing `ROLE_MINTER`; in backed mode, the stablecoin may not be allow-listed on the commitment. Platform-side; see Troubleshooting.

The first confidential operation after a deployment restart fetches FHE keys and can be noticeably slower. Don’t tune timeouts to that first call.

Next: send a private transfer or redeem back to stablecoin.

Get started

Core concepts

Guides

Security & access

Support

Prerequisites

Make the call

What happens on-chain

Verify

Common failures

​Prerequisites

​Make the call

​What happens on-chain

​Verify

​Common failures

Prerequisites

Make the call

What happens on-chain

Verify

Common failures