Skip to main content
COP By prepares settlement orders that start with USDC on Arc and end with COPm at an EVM address on Celo.
An organization must activate and fund its Arbitrum settlement account before creating an order. COP By uses that account to receive the CCTP mint and execute the route to Celo.

Product rules

The Circle forwarding fee is charged in addition to the principal. The quote returns both circleUpfrontFeeUsdc and totalDebitUsdc. Squid costs remain included in the route output and are not presented as a separate customer fee.

Create a quote

sendAmountUsdc is the exact principal covered by the Circle quote. The user debit is:
copAmountMin is the binding delivery floor. Create the order before expiresAt; otherwise request a new quote.

Create an order

Use a unique Idempotency-Key for every logical order. Retrying the same key and quote returns the same order. Reusing the key for a different quote returns IDEMPOTENCY_CONFLICT.
Creating an order does not move funds. Its execution response contains the Arc calls for the user’s wallet:
  • Use atomicBatch.calls with wallet_sendCalls when the wallet supports batching. This gives the user one confirmation.
  • Otherwise, submit sequential.calls in order. The plan omits approve when the existing USDC allowance covers totalDebitUsdc.
After the burn confirms on Arc, report its transaction hash to COP By. The burn is verified against the order and immediately triggers settlement. A scheduled worker retries pending orders as a fallback.
COP By then waits for Circle Forwarding to mint USDC to the organization settlement account on Arbitrum, obtains a fresh Squid route, and verifies the final COPm transfer on Celo. Poll the order until it reaches DELIVERED.

Read an order

Orders are isolated by organization. An API key cannot read an order owned by another integration.

Errors

Settlement errors include lifecycle context instead of a generic message:
SETTLEMENT_ACCOUNT_INACTIVE means the organization must activate and fund its settlement account before creating an order. A route above the 4% guard returns SLIPPAGE_LIMIT_EXCEEDED; COP By does not proceed to burn. If an order becomes STUCK, continue polling it and contact support with the order ID; automated refunds are not part of this release.

Settlement boundary

COP By considers a settlement delivered only after COPm is verified at the requested Celo address. Depositing those COPm into Neeru or another protocol is outside this settlement order and requires a separate integration.

Errors and lifecycle

Handle quote expiry, intake pauses, stuck orders, and safe retries.

API reference

Inspect settlement request and response schemas.