User
Merchant
Document status: reference notes
Service terms: awaiting publication
These notes provide service information for reviewing an asset service. DTCC Trading focuses on Stellar tokenization and multichain interoperability. A service also needs an identified operator, a defined scope, clear permissions, reliable records, and applicable terms. These topics help a prospective user assess the documentation. This page does not offer an exchange, confirm a supported pair, authorize custody, or establish a DTCC Trading agreement.
Use the version and date of a service document to distinguish current arrangements from earlier descriptions. Keep the document reference with any record that relies on its contents.
DOCUMENT STATUS AND SERVICE SCOPE
Operative DTCC Trading asset-service terms are not published here. This reference does not request acceptance, waive rights or select a dispute forum. It identifies information that a verified service document would need to supply.
1. Eligibility information
An eligibility section identifies who a service is intended for and which conditions apply to access. Age, location, capacity and any authority to act for an organization belong in that section. These notes set no eligibility threshold and cannot confirm that a particular person or entity can use a DTCC service.
2. Defining the service
A service description separates the action being offered from the surrounding interface. For tokenization or a network connection, identify the asset, the participating systems and these distinct roles:
who can hold or control the relevant assets;
who operates the account, wallet or access interface;
who supplies information and explains its intended use;
who defines the asset, its rights and the conditions under which those rights can be exercised.
An embedded interface can involve several organizations. Read the role of each one separately: the website host, service operator, asset issuer and network need not be the same party.
3. Understanding an asset action
3.1 Before an instruction
Describe a proposed action from its starting state to its intended outcome. Identify the source asset and network, the destination asset and network, and any service between them. Record the address or account format, required identifiers and the evidence expected at completion. For a representation on another network, examine the custody, issuance or redemption step separately. A matching token name alone does not establish that these steps are available or equivalent.
3.2 Reading a quoted value
A number needs a unit, a source and an observation time. Distinguish a reference value from an executable quote, then read any stated validity period and the event that fixes the final amount. This page supplies no rate, price-lock condition or guarantee that a proposed exchange can be completed.
3.3 Cost details
Keep different cost categories separate when reviewing a service:
Service charges: identify the amount or calculation method, its currency, the party charging it and the action to which it applies;
Network costs: identify the relevant network action and whether a stated amount includes that cost or treats it separately. No DTCC fee is specified here.
3.4 Amount constraints
An amount limit needs a stated unit and a defined scope. Check whether it applies to a single instruction, an account or a period of time. Read what the service documentation says about an amount outside that range, including any handling costs. No minimum, maximum or refund formula is set by this reference.
3.5 Confirming an outcome
Separate an instruction from evidence that it completed. A page message, a service record and a network transaction may describe different stages. Identify the record that confirms the requested change, then check its asset, network, amount and destination. Do not infer a reversal or recovery capability from the presence of a support link or a familiar interface.
4. Information to review
A clear review keeps the following details tied to the same proposed action:
the stated purpose of the action and the service documentation that explains its permitted use;
the exact asset identifiers, network names and destination details shown in the applicable instructions;
the parties involved and any eligibility or access conditions described for the relevant service;
the origin and intended destination of the assets, the authority to give the instruction, and the records needed to connect that instruction with its outcome;
the source and version of any verification, screening or additional-information requirement;
the channel through which a documented request can be checked before information or assets are sent.
5. Access and review processes
5.1 Describing a review
A description of a compliance or access review should identify its scope and the party responsible for it. Read which information is considered, when the review occurs and which document explains the process. These notes do not confirm a DTCC screening provider, monitoring system or regulatory status.
5.2 Pending and restricted actions
A pending status can have several meanings. The service record should distinguish an instruction awaiting information from one that was declined, completed or otherwise closed. Check the stated next step and any available reference number. A label alone does not establish who holds assets, what action is possible or when the status will change.
5.3 Regional availability
Read regional availability alongside the exact service and legal entity to which it applies. A country appearing in an illustration or an educational example is not evidence of access. This page does not publish a DTCC regional eligibility list.
5.4 Reviewing use restrictions
Where a service publishes restrictions, review the following sources of context:
the activity described in the relevant service document;
the parties identified in the proposed instruction;
the asset and network involved in the action;
the source of any additional access condition;
the record explaining a restriction and any stated review process;
the official source for updates, rather than assumptions based on a similar service.
6. Asset and network context
Review each of these topics separately when assessing a digital asset service:
Valuation: identify whether an amount is a network balance, a reference conversion or an offered price. Keep its source and time with the figure.
Destination: verify the network and asset identifier with the address. An address that looks familiar is not evidence of compatibility.
Availability: distinguish a functioning interface from evidence that the underlying service and required network connection are available.
Execution: identify the conditions and records that establish an outcome; a displayed estimate does not prove completion.
Applicable requirements: use current official material for the relevant service and location. A general asset description does not resolve a particular legal question.
Record keeping: retain the asset, amount, date and relevant references. These notes do not determine the tax treatment of an activity.
7. Reading service commitments
7.1 Stated service qualities
A service commitment needs a defined scope and conditions. Read statements about availability, information quality or performance together with their exceptions and measurement method. An illustration or example does not establish a contractual assurance.
7.2 Responsibilities and limits
A responsibility section explains which party undertakes an obligation and how the document treats an unmet obligation. These notes do not allocate liability or limit anyone's rights. In an applicable service document, distinguish the following topics:
the reference value and the conditions for a final amount;
the information supplied and the party that verifies it;
the network record and the service completion record;
the process for a restricted action and any required follow-up;
the role of each external system used to deliver the service.
A stated financial limit must be read with its definition, period and applicable conditions. No liability cap, calculation period or measure of compensation is established on this page.
8. Changes and service continuity
When a service changes, distinguish a revised document from a technical change or a change in available assets. Record when the change takes effect and what it means for existing instructions. The applicable documentation should address pending actions and any required next step. This reference does not promise completion, reversal, notice periods or continued availability for an unconfigured service.
9. Questions and dispute information
9.1 Identifying the process
A process for questions or disputes begins with the responsible entity and an authenticated contact channel. The relevant document may explain how to provide a case reference, which information is needed and what happens next. These notes appoint no arbitrator, require no confidential proceeding and select no place or language for resolving a dispute.
9.2 Scope of any procedure
Read the scope of a procedure before relying on its name. Identify the parties and issues it covers, any stated prerequisites and the source of the procedure. Do not infer an agreement from a page heading. This reference creates no waiver, collective-action restriction, court submission or separate right to relief.
10. Privacy context
10.1 Distinguishing the participating services A website, an embedded application and an asset service can have different roles in handling information. Read the notice associated with each relevant service. Identify the responsible entity, the information involved and its stated purpose before drawing conclusions from the interface. This reference does not assign privacy responsibility to an unnamed partner or describe an approved DTCC data-sharing arrangement.
A notice about one organization does not explain another organization's practices. Match the entity and service named in the notice to the activity under review.
10.2 Describing information flows When reviewing a service, distinguish these information topics without assuming that DTCC collects either category:
asset identifiers, network addresses and transaction references that may appear in an instruction or its completion record;
information that a particular service document identifies for an access or verification process, together with its purpose and the party responsible for that process.
A role in handling information needs to be supported by the applicable notice and actual service arrangement. This page does not designate a data controller or processor, approve marketing use or confirm an operational processing activity.
10.3 Requests concerning personal information An applicable privacy notice should explain the requests it covers and how they can be made through a verified channel. Keep the relevant service, responsible entity and information involved clear when reviewing that process. These notes do not determine which statutory rights apply to a person, set response deadlines or name a supervisory authority for DTCC Trading.
A retention statement needs to identify the information covered, the basis for keeping it and the event from which a period is measured. No retention period or exception is adopted here. Avoid carrying a period from an unrelated service into a DTCC record.
For privacy-contact information, use an authenticated source for the responsible entity. A verified DTCC channel is not published here. Do not use a copied or inferred address to send personal information.
10.4 Related document information Read the separate privacy document information for the topics awaiting an approved DTCC privacy notice.
11. Applicable legal scope
11.1 Identifying the relevant document Identify the legal entity, service and users described by a document before considering its scope. A location mentioned in an unrelated source does not establish the law governing a DTCC service. These notes choose no governing law, waive no conflict rules and do not require anyone to submit to a named court or venue.
11.2 Reading regional distinctions Where an approved document distinguishes regions, read each provision with its stated conditions and the service it covers. This page does not assign different governing laws to different users or publish a regional contractual arrangement.
A document may refer to rules outside the document itself. Such a reference needs the correct authority, jurisdiction and current source. This page does not interpret mandatory legal protections, resolve their application to an individual or state that a contractual clause overrides them. Questions of legal effect require the applicable facts and qualified advice.
12. Document relationships
Document set. Identify the complete set of documents relevant to a service and how they refer to one another.
Clause relationships. Read how connected provisions work together before relying on an isolated sentence.
External events. Check the documented treatment of service interruptions without assuming an exemption from responsibility.
Party roles. Distinguish an operator, issuer, customer and integration provider; a technical connection alone does not establish an agency or partnership.
Other parties. Identify whose interests a provision addresses without inferring rights for an unnamed party.