Obligations at a glance
Receipts
Send a receipt to the end user when each transaction reaches its final state: an onramp deposit is credited, an offramp withdrawal settles, or an onchain transfer confirms. Deliver each receipt through your channel of choice (for example, email, in-app notification, or both). Each subsection maps the fields you show on the receipt to their location in the API response. Every receipt must also include the required data elements and the required footer text.Required data elements
Every receipt must capture the following data elements to comply with US money transmission laws and Circle’s virtual asset licenses. The internal labeling of these elements is flexible provided the required information is present and clearly conveyed to the end user. Elements marked “if applicable” are omitted only when they do not apply to the transaction type (for example, there is no Blockchain Network or Transaction Hash on a fiat onramp or offramp).- Transaction Date
- Precise Transaction Time
- Sender Name
- Recipient Name
- Blockchain Network (if applicable)
- Unique Transaction / Confirmation ID
- Transaction Hash
- Amount in USD
- Fee Disclosure (if applicable)
- Tax Disclosure (if applicable)
- Transfer / Recipient Amount (Total to Recipient)
- Total Transaction Amount in USD
- Exchange Rate (if applicable)
6:03:47 PM UTC), not the date or minute alone.
Applicability: Each rail subsection lists only the elements that apply to
that transaction type. Blockchain Network and Transaction Hash apply to onchain
transfers only. Exchange Rate and Tax appear only where a conversion or tax
actually occurs.
Onramp receipts (wire deposit)
Send the receipt when the wire deposit transitions tocomplete. See
Get an account deposit
for the full response schema.
Offramp receipts (bank withdrawal)
Send the receipt when the bank withdrawal transitions tocomplete. See
Get an account withdrawal
for the full response schema.
Onchain receipts (deposit or send)
Send the receipt when the onchain transfer reaches a terminal state (confirmed onchain). Determine directionality from the source and destination fields. Inbound transfers (deposits into the account) have a blockchain source. Outbound transfers (sends from the account) have a blockchain destination. See Get an account transfer for the full response schema.Required footer text
Include the following on every receipt, including receipts delivered by email. The footer is organized into named sections so that Circle can update them individually as state-specific regulatory requirements change. Do not modify any of the copy without Circle’s approval. The “User Agreement” and “Privacy” labels in the closing section must link to the URLs shown. Render the links in whatever format your channel supports (HTML anchor, email link, plain-text URL).Disclosures
Disclosures are pre-transaction obligations, distinct from receipts. Present them to the end user before they can open an account or initiate a transaction, and capture affirmative consent.Terms and conditions
Before you open an account or process a first transaction for an end user, present Circle’s Digital Asset Account User Agreement and capture explicit acceptance.1
Present the user agreement
Display the user agreement as a link. Do not paraphrase or summarize the terms.
The preferred consent wording is:
I have read, understand, and agree to the Digital Asset Account User Agreement.
2
Capture consent
Require an affirmative action such as a checkbox or an “I agree” button. Do not
use pre-checked boxes.
3
Register acceptance with Circle
Call the
Submit an application
endpoint with:
endUserAgreesToTermsOfService: set totrueendUserIpAddress: the end user’s IP address
4
Log the consent event
Record the user ID, timestamp, user agreement version accepted, and IP address
in your own records.
Per-transaction disclosures
Before executing any transfer, withdrawal, or onramp, present the written terms below to the end user in a manner that is clear, conspicuous, and legible. Capture the end user’s acknowledgement that they received the disclosures. If a pre-disclosure step already exists in your transaction workflow, these elements do not need to be labeled literally as “pre-transaction disclosures” provided the required information is presented before finalization.
Onramps and offramps do not have a Blockchain Network or Transaction Hash. Apply
the elements above only where they are relevant to the transaction type.
Implementation checklist
Before you enable live transactions for any end user, confirm the following:- Onramp receipt is rendered and delivered on deposit completion.
- Offramp receipt is rendered and delivered on withdrawal completion.
- Onchain transfer receipt is rendered and delivered on confirmation.
- All statutory receipt data elements are captured, including Sender Name and Recipient Name for every transaction (including self-transfers) and the precise transaction time.
- The required modular footer (Licensing information, Complaints, Statement of liability, Refund policy, Bank disclosure, Closing) is included on every receipt.
- Circle’s terms and conditions are surfaced and explicit consent is captured before account opening.
- Pre-transaction disclosures (amount, fees, exchange rate, type, settlement time, irrevocability, acknowledgement of receipt) are shown before each transaction.