> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. # Receipts and disclosures > Statutory receipt and pre-transaction disclosure requirements you must implement when building on Circle Digital Asset Accounts (DAA). Digital Asset Accounts (DAA) operates under a B2B2C model in which Circle is the licensed money transmitter and you are responsible for surfacing compliance artifacts to your end users. Transactional receipts and pre-transaction disclosures derive from your Definitive Agreement with Circle and from Circle's Money Transmitter Licenses (MTLs) and the New York BitLicense. Circle returns the required content fields on the API response and in the corresponding webhook events. You render and deliver them. ## Obligations at a glance | Area | Circle's obligation | Your obligation | | --------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------ | | [Receipts](#receipts) | Generate receipt content on the API response | Render and deliver the receipt to the end user at transaction completion | | [Disclosures](#disclosures) | Provide approved disclosure text and terms and conditions | Present before transaction initiation and capture consent | ## 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](#required-data-elements) and the [required footer text](#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) **Sender and Recipient names:** Statutory requirements for all transactions, including transfers where the end user is sending funds to their own account. Capture and display them even for self-transfers (for example, "You sent \$100 to your account"). The information does not need to be labeled literally as "Sender" or "Recipient." **Amount fields:** Every receipt must show Amount in USD, Total Transaction Amount (what the sender pays, including any fee or tax), and Total to Recipient (what the recipient receives). When there is no fee, tax, or currency conversion, as with most USDC transfers and no-fee deposits, these will be the same figure. Display each line regardless. Exchange Rate appears only when currencies are converted. Tax Disclosure appears only when a tax is collected. **Timestamps:** Display the precise transaction time to the second (for example, `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 to `complete`. See [Get an account deposit](/api-reference/digital-asset-accounts/all/get-account-deposit) for the full response schema. | Receipt field | API field | Notes | | ------------------------------------ | -------------------------- | ------------------------------------------------------------------------------- | | Unique Transaction / Confirmation ID | `data.id` | UUID of the deposit. | | Transaction Date & Time | `data.createDate` | Date and precise time (to the second) the deposit was credited. | | Sender Name | `data.source.name` | Originating bank and masked account (for example, `WELLS FARGO ****1234`). | | Recipient Name | Account holder on file | The end-user account holder receiving the funds. | | Amount in USD | `data.amount.amount` | USD amount of the deposit. | | Fee (if any) | `data.fee.amount` | Deposit fee, if charged. | | Total to Recipient | `data.amount.amount` | Amount credited to the recipient (Amount minus Fee). | | Total Transaction Amount in USD | `data.amount.amount` + fee | Total value of the transaction (Amount plus Fee). | | Reference | `data.trackingRef` | Wire tracking reference. Falls back to `data.customerExternalRef` if populated. | | Status | `data.status` | `pending`, `complete`, or `failed`. Send the receipt on `complete`. | ### Offramp receipts (bank withdrawal) Send the receipt when the bank withdrawal transitions to `complete`. See [Get an account withdrawal](/api-reference/digital-asset-accounts/all/get-account-withdrawal) for the full response schema. | Receipt field | API field | Notes | | ------------------------------------ | ----------------------- | --------------------------------------------------------------------------------------- | | Unique Transaction / Confirmation ID | `data.id` | UUID of the withdrawal. | | Transaction Date & Time | `data.createDate` | Initiation date and precise time (to the second). Use `data.updateDate` for settlement. | | Sender Name | Account holder on file | The end-user account holder sending the funds. | | Recipient Name | `data.destination.name` | Destination bank and masked account (for example, `COMMERZBANK AG ****3000`). | | Amount in USD | `data.amount.amount` | Principal amount of the withdrawal. | | Fee (if any) | `data.fees.amount` | Withdrawal fee deducted from the amount. | | Total to Recipient | `data.toAmount.amount` | Net amount received by the destination bank (Amount minus Fee). | | Total Transaction Amount in USD | `data.amount.amount` | Total debited from the account (Amount plus Fee). | | Reference | `data.trackingRef` | Bank tracking reference. | | Status | `data.status` | `pending`, `complete`, or `failed`. Send the receipt on `complete`. | ### 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](/api-reference/digital-asset-accounts/all/get-account-transfer) for the full response schema. | Receipt field | API field | Notes | | ------------------------------------ | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | | Unique Transaction / Confirmation ID | `data.id` | UUID of the transfer. | | Transaction Date & Time | `data.createDate` | Date and precise time (to the second) confirmed onchain. | | Sender | Account holder on file or `data.source` | Account holder sending the funds. For inbound deposits, `data.source` is the originating blockchain wallet. | | Recipient | Account holder on file or `data.destination.address` | Account holder receiving the funds. For outbound, `data.destination.address` is the destination wallet. | | Blockchain Network | `data.source.chain` or `data.destination.chain` | The network (for example, Ethereum, Base, Solana). | | Transaction Hash | `data.transactionHash` | Onchain hash. Link to a block explorer so end users can independently verify the transaction. | | Amount in USD | `data.amount.amount` | USDC amount transferred, shown in USD (USDC is 1:1 with USD). | | Network Fee (if any) | `data.fees[0].amount` | Gas or network fee. May be zero for internal transfers. | | Total to Recipient | `data.amount.amount` | Amount received by the recipient. | | Total Transaction Amount in USD | `data.amount.amount` | Total value of the transaction (Amount plus Fee). | ### 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). ```text wrap theme={null} Licensing Information You are receiving this message because you conducted a transaction with Circle Internet Financial, LLC. Circle Internet Financial, LLC (NMLS ID# 1201441) is licensed as a Money Transmitter by the New York State Department of Financial Services and to engage in Virtual Currency Business Activity by the New York State Department of Financial Services. Complaints If you have questions or a complaint, please first contact Circle toll-free at (888) 762-4966 or visit the Circle Support Portal (https://help.circle.com/support) or email customer-support@circle.com. If you have an unresolved question or complaint about our regulated services after contacting us, please direct your complaint to your local regulator. A full list of Circle's licenses and state-specific complaint procedures can be found here (https://www.circle.com/legal/licenses). Statement of Liability Except as set forth in the User Agreement or as required by applicable law, Circle is not responsible for any processing delays that may result in connection with any deposit, withdrawal, or transaction. Refund Policy Once a transaction has been initiated (including, but not limited to, a Digital Currency Transfer), it cannot be reversed. Deposits using a bank account, debit card, or credit card may be reversed or may be subject to a chargeback or related claim. Except as set forth in the User Agreement, all payment transactions processed through the Services are non-refundable. You may have additional refund or charge-back rights under your agreement with the recipient of such funds, your bank, or applicable law. You should periodically review statements from your bank, which should reflect all applicable payment transactions made using that payment method. You can also always access the record of your transactions by logging into your account. Bank Disclosure Circle is not a bank; Circle Digital Asset Accounts is not a bank account, and any funds are not insured by the Federal Deposit Insurance Corporation, the Securities Investor Protection Corporation or by any US or foreign government agency, insurance fund, person or entity. Circle makes no representations or warranties regarding the amount of time needed to complete processing any deposit, withdrawal, or transaction. All rights reserved. © 2026 Circle Internet Financial, LLC © 2026 Circle Internet Singapore Pte Ltd © 2026 Circle Internet Financial Europe SAS PO Box 52235 Boston, MA 02210 User Agreement: https://www.circle.com/digital-asset-account-user-agreement Privacy: https://www.circle.com/en/legal/privacy-policy ``` ## 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](https://www.circle.com/digital-asset-account-user-agreement) and capture explicit acceptance. 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](https://www.circle.com/digital-asset-account-user-agreement). Require an affirmative action such as a checkbox or an "I agree" button. Do not use pre-checked boxes. Call the [Submit an application](/api-reference/end-user-onboarding/submit-application) endpoint with: * `endUserAgreesToTermsOfService`: set to `true` * `endUserIpAddress`: the end user's IP address Record the user ID, timestamp, user agreement version accepted, and IP address in your own records. You must re-present the user agreement and re-collect acceptance whenever the version changes. ### 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. | Disclosure element | Required | Notes | | --------------------------------- | --------------- | ------------------------------------------------------------------------------------------------- | | Transaction Amount | Always | The amount the user is transacting, before fees. | | Transaction Fee | Always | Fee charged for the transaction, if any. | | Transaction Expenses | When applicable | Any additional expenses passed to the user. | | Transaction Charges | When applicable | Any additional charges passed to the user. | | Transaction Exchange Rate | When applicable | Only where a currency or asset conversion occurs. | | Transaction Type and Nature | Always | For example, deposit (onramp), withdrawal (offramp), or transfer. | | Estimated Net Amount to Recipient | Always | Amount the recipient will receive after fees. | | Estimated Settlement Time | Always | Expected time for the transaction to settle. | | Irrevocability Warning | When applicable | Once executed, the transaction may not be undone. Wire and onchain transfers are generally final. | | Other Disclosures | When applicable | Any other disclosures given in connection with the transaction. | | Acknowledgement of Receipt | Always | Capture the customer's acknowledgement that the disclosures were received. | 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.