Skip to main content
Managed Payments generates reports through the core Circle Reports API (/v1/reports). The following report types cover Managed Payments activity only. They’re separate from the Circle Mint camt053 daily statement, which isn’t available on Managed Payments keys.

Report types

Use camt_managed for CAMT.053 statements on Managed Payments. The Circle Mint camt053 type isn’t valid on Managed Payments keys. It covers Circle Mint accounts, not Managed Payments. See CAMT.053 daily statements for the ISO 20022 XML structure, which camt_managed shares.

Request and download a report

  1. Request the report with POST /v1/reports, passing reportType, date in YYYY-MM-DD format, and timeframe where the type supports it. Circle interprets date in your entity’s reporting timezone, not UTC. For example, a Circle SG entity uses Singapore Time (SGT). Circle generates Managed Payments reports on a schedule:
    • If the report is available, the response is 200 OK with the report id and a pre-signed downloadUrl.
    • If the report is still being generated, the response is 202 Accepted with a report id and no downloadUrl.
  2. If the response was 202 Accepted, poll GET /v1/reports/{id} until status is ready and a downloadUrl is present.
  3. Download the file from downloadUrl before the time given by expiresAt. Call GET /v1/reports/{id} again to get a fresh URL after it expires. You can also request the report again. Requests are idempotent, so the same parameters return the same report.
expiresAt uses different formats across endpoints. Create (POST /v1/reports) and get-by-ID (GET /v1/reports/{id}) responses return it as an ISO 8601 timestamp, as in the preceding example. The list endpoint (GET /v1/reports) returns it as epoch milliseconds.