Document status: information only

Commercial terms: awaiting publication

These notes organize the information needed to describe a potential business introduction involving DTCC Trading. They are a document reference, not a referral agreement, application form or offer of compensation. No DTCC referral program or operative commercial terms are published here. An actual arrangement would need identified parties, a defined scope and approved terms that can be read together.

DTCC Trading focuses on Stellar tokenization and multichain interoperability. A business discussion in that context can involve an asset issuer, a service operator or an integration provider. Record which role each participant is considering and the purpose of an introduction. A conversation about a use case does not establish a partnership, commission entitlement or commitment to deliver a product.

Reading this reference does not enroll anyone in a program or create a binding agreement.

Document review

A document presented for acceptance needs an identified author, a clear version and a stated scope. A checkbox, a page visit or an introductory message is not evidence that this reference contains approved DTCC collaboration terms.

Distinguish an individual contact from the organization they represent and the capacity in which they are acting. Record the source of any claimed authority before attributing a statement to an organization. These notes authorize no person to act for DTCC Trading.

Keep an unresolved question visible until an authenticated source provides the needed detail.

Scope, records and decision points

Initial contact.
An introduction is a starting point for a discussion. Identify the parties, the purpose and the source of the information being shared. No review process, application channel, approval criterion or response deadline is established by this page.

Documented status.
A record should distinguish a contact received from a discussion underway and from an agreed arrangement. Read the exact scope of any written confirmation rather than extending it to other activities. Approval of one matter would not, by itself, establish a fee entitlement for another.

Separate decisions.
Keep the key decisions distinct:
the introduction and its purpose
, the scope of a possible working relationship, and
the conditions of any separately documented commercial arrangement. Evidence of a conversation is not evidence that all of these decisions have been made. Record which questions remain open and which source supports each confirmed point.

1. Purpose and context

The purpose of these notes is to help distinguish business context from an operational or commercial promise. Begin with the proposed use case, the people or entities involved and the information they need to evaluate it. A tokenization topic and a network integration topic may require different records even when discussed together.

Keep the scope of a discussion separate from authority, exclusivity and payment. Introducing an organization does not itself establish permission to speak for it, reserve a territory or define a right to compensation. If an arrangement is later documented, its participating entities, services and applicable conditions need to be explicit. These notes grant none of those rights and designate no representative.

2. Terms used in a review

The following descriptions explain review topics. They do not define an operative referral contract:

2.1 Prospective organization. Identify the organization being discussed, its relevant contact and the use case under consideration. A label does not establish customer status or eligibility for a DTCC service.

2.2 Digital property. Record the website, application or platform involved and who controls it. Keep the property's role separate from the identity of any asset issuer or underlying network operator.

2.3 Working relationship. Describe an agreed scope only when there is a source for it. An introduction and an established commercial relationship are different records.

2.4 Introduction record. A useful record identifies who made an introduction, the parties involved, its date and its purpose. Include only information that is appropriate to share through the verified channel. This page provides no submission destination and does not request another person's private details.

2.5 Relevant period. A time period needs a starting event, an ending event and a stated purpose. Distinguish the date of an introduction from the dates of a discussion or agreement. No engagement window or deadline for earning compensation is specified here.

2.6 Commercial conditions. Read the service scope, calculation basis, qualifying events and timing together in an applicable approved document. No commission schedule is set by these notes.

2.7 Qualifying event. Identify the exact event and record that would establish a condition. A technical test or a page registration is not automatically a commercial milestone.

2.8 Compensation record. An amount needs an identified basis and source. These notes neither promise a referral payment nor establish who would be entitled to receive one.

2.9 Activity measure. Define what a total counts, its units and its reporting period before using it in a comparison or calculation.

2.10 Revenue measure. Identify what a reported figure includes and excludes, the entity to which it relates and the records supporting it. A revenue label alone does not establish receipts, profitability or an amount available for distribution.

2.11 Charge measure. Keep a charge, an invoice and a settled payment distinct. Each can refer to a different stage or amount; their relationship needs to be supported by the relevant records.

2.12 Nonpublic information. Business discussions can involve information intended for a limited audience. Identify the source, intended recipient and purpose before sharing it. Do not infer permission from possession of a document or from participation in a conversation. This reference does not create a confidentiality agreement or authorize disclosure of another party's information.

2.13 Attribution reference. A code or link can help connect an event with a source, but its meaning depends on the system and documented rules that use it. No DTCC referral identifier is issued here.

2.14 Associated activity. Keep a technical association separate from a commercial conclusion. A shared link does not, by itself, establish a contractual attribution or fee.

3. Introduction and attribution records

3.1 Recording an introduction.
Identify the intended recipient and authenticated channel before sending a business introduction. State the purpose and the role of each participant clearly. Keep the date, source and scope of the information together so the record can be understood later. Do not treat an unverified address, inherited form or guessed application URL as a DTCC submission channel. This reference does not transmit an introduction.

3.2 Review status. A status should say what has actually been reviewed and which matter remains open. Receipt of information and acceptance of a proposed arrangement are separate events.

3.3 Time and scope.
When timing is relevant, connect each date with its event and the document that gives it meaning. A period counted from an introduction may differ from one counted from an agreement or the start of a service. This page sets no qualifying window, extension rule or deadline for commercial credit. 

3.4 Technical attribution.
Read how a link, code or other identifier is created and what event it records before relying on an attribution claim. Record any limitations, such as whether the reference describes a visit, a registration or a later activity. A technical record cannot supply missing commercial conditions, and these notes do not adopt any tracking system as decisive evidence.

An attribution record should be understandable alongside its source and date. Preserve the reference needed to review a result rather than relying only on a summary label or a number displayed in an interface.

3.5 Changes in a discussion. If the proposed scope or participating parties change, record the change and its source. Do not assume that an earlier introduction automatically applies to a different service, organization or arrangement.

3.6 Overlapping introductions.
Several people may contribute to the same business discussion. A useful record distinguishes the timing, purpose and documented contribution of each introduction without turning a chronological fact into a payment decision. Preserve the evidence for separate contributions and identify the process, if any, described in an applicable agreement for reviewing an overlap.

An unresolved attribution question should remain recorded as unresolved. This reference supplies no allocation formula, decision deadline or dispute outcome. Where a later agreement addresses the issue, read the exact parties and activities covered before using it to interpret an earlier record.

4. Statements and authority

Match a statement to the person or entity making it and the capacity in which they speak. An organizational name in a message does not alone establish authority to make a commitment.

A clear business introduction separates facts, proposals and open questions. Describe the proposed use case without presenting an unconfirmed feature as available. Identify the evidence for any statement about an asset, network connection or service capability. Keep permission to use a name or image distinct from permission to represent an organization. Do not describe an introductory contact as an employee, agent, partner or authorized representative unless that role is confirmed. Where a discussion mentions compensation, record it as a topic requiring an approved agreement rather than treating activity counts as money earned. Keep authentic business activity separate from test events and examples used to explain an interface. Finally, make the source and date of each material statement visible so that another reader can tell what was known at the time. These notes establish no contractual warranties, screening outcome, marketing authorization or eligibility finding for any participant.

5. Commercial record details

5.1 Identifying the scope. Any commercial record needs to name the participating entities and the specific service or activity it covers. Read separate product or service schedules independently; inclusion of one topic in a discussion does not automatically include all DTCC tokenization or interoperability work.

5.2 Conditions and duration. A compensation condition needs an identifiable event, an observation date and a source for its duration. Do not substitute a demonstration, a test transaction or an account label for the event described in an actual agreement.

5.3 Supporting a calculation. Keep the source records, reporting period, units and calculation method together. Distinguish an amount invoiced from an amount received, and a provisional estimate from a reconciled result. Record any adjustments with their reason and the event they relate to, so that a reader can trace the change without guessing. Access to a dashboard does not make its totals a binding calculation basis. These notes do not appoint an accounting system as conclusive, authorize offsets or recoveries, promise access to records, or establish a commission claim against any receipt or activity.

5.4 Timing and thresholds. A payment schedule needs a defined period, a due event and any applicable threshold in a stated currency. This reference sets no monthly cycle, minimum balance, carry-forward rule or payment date.

5.5 Payment information. If an approved arrangement later requires payment details, use its verified process and check the named recipient, currency and network or payment method. Keep an invoice, its approval and its settlement as distinct records. No banking route, token, network, exchange-rate source or time for settlement is selected here. Do not send financial details through a copied or unconfigured form.

6. Responsibility information

6.1 Scope of responsibility. Read an obligation together with the party undertaking it, the activity it covers and any stated conditions. These reference notes do not allocate losses or distinguish recoverable from excluded damages. An example of a business risk is not a contractual release for that risk.

6.2 Stated exceptions. An exception needs to be read with the provision it qualifies and the applicable facts. This page does not determine the legal effect of conduct or adopt a liability exception.

6.3 Financial limits. A financial cap requires a clear calculation basis, period and scope. These notes set no liability ceiling, compensation measure or limit tied to prior fees. An amount from another organization's terms has no role in this reference.

7. Information handling

Before sharing material from a business discussion, identify its source, intended audience and the reason for sharing it. A document marked for a limited audience should be understood in the context of the permissions and arrangements that apply to it.

Different recipients can have different roles in a discussion. Record whether a person is participating as an employee, contractor, adviser or representative, and check the authority for giving that person the information. The fact that a recipient would find material useful does not establish permission to disclose it. Where an applicable agreement describes permitted sharing or a request from an authority, read the actual provision and its conditions. This page does not authorize disclosure, identify approved recipients or adopt a legal exception on behalf of DTCC Trading.

Tie the intended use of shared information to the purpose of the discussion. A copy received for one topic should not be assumed available for unrelated marketing, publication or product claims.

The duration of an information-handling obligation belongs in its applicable document. No continuing term or fixed number of years is set here.

8. Operator role

An operator's role should be described through specific activities and evidence. Distinguish receiving an introduction, evaluating a proposal, providing a service and maintaining commercial records. These are separate responsibilities. This reference does not promise that DTCC will review an introduction, accept a prospect, protect information under an unpublished agreement or make a payment.

9. Introducer role

A person making an introduction should be identifiable in the record, together with the purpose and information they contribute. Keep statements about the proposed service within the evidence available, and separate personal observations from an organization's approved description. Any permission to use branding or to speak for another party needs its own source. This page does not appoint an introducer, grant use of DTCC marks, request invoice details or impose participation duties through an unpublished program.

10. Duration and closure

10.1 Starting point. A documented arrangement needs a clear commencement event and scope. Neither viewing this page nor making a general enquiry starts a term under these notes.

10.2 A change in status. If a discussion or arrangement is suspended or closed, record what changed, who communicated it and which activities are affected. Distinguish a temporary pause from a final decision. This reference prescribes no breach procedure, cure period or immediate termination condition for a DTCC relationship.

10.3 Organizational or service changes. A change of ownership, control or service availability may raise a new scope question. Read the applicable documents and the specific notice; these notes do not automatically transfer or end any arrangement when such a change occurs.

10.4 Closing the record. A clear closure record distinguishes completed activity, pending questions and any continuing matter documented elsewhere. Keep the relevant references so that an earlier contribution can be understood without implying that compensation has been earned. If an approved arrangement specifies consequences for branding, attribution links or payment, review each condition in that arrangement. This page creates no continuing fee entitlement, grace period, automatic cancellation or right to use a party's name after a discussion ends.

A pending payment question requires its actual agreement and records; these notes authorize no withholding or deduction.

11. Independent roles

A business introduction does not, on its own, establish employment, agency, a partnership or a joint venture. Name the role that is actually supported by the relevant documentation. These notes do not appoint a contractor, grant authority to bind DTCC or authorize anyone to enter an agreement on another party's behalf.

12. Dispute costs

A provision about the cost of a dispute needs to identify the process, the parties and the conditions under which it applies. This reference does not assign legal expenses to a party or promise reimbursement. The outcome of a discussion cannot be inferred from a heading about costs.

13. Process and applicable scope

For an actual question about an arrangement, identify its responsible parties and authenticated contact channel first. Read the applicable document for any described review or dispute process, together with the facts and records involved. These notes set no negotiation deadline, select no governing law or court, and contain no agreement to a particular venue. They cannot resolve the legal effect of a separate contract.

14. Documents, changes and transfers

Keep the relevant documents together and identify how they refer to one another. A summary, presentation or conversation can serve a different purpose from an approved agreement. These notes do not replace an existing arrangement or define a complete contractual document set.

When a document changes, retain the version, date and scope needed to understand the revision. Separate an editorial clarification from a change in a condition or responsibility. Read any stated effective date and the treatment of earlier activity in the applicable document. This page does not create an amendment process, treat continued activity as acceptance, or decide the effect of a later document on earlier commercial records.

A transfer of a role or obligation needs to be considered under the relevant arrangement and circumstances. Identify the original party, proposed replacement and exact scope. No permission to assign rights or transfer duties, and no exception for an organizational transaction, is granted by this reference.

15. External events

An interruption record should identify the affected activity, the observed event and the source of the status information. Distinguish a communication delay from an interruption of the underlying service or network. Any contractual treatment of events outside a party's control belongs in the applicable agreement. These notes create no exemption from responsibility, qualifying event list, automatic extension or termination period.

16. Official channels

An official communication needs an authenticated destination and a clear purpose. Identify which entity and arrangement it concerns before sending business or personal information. No DTCC referral, compliance or payment email address is published by these notes; do not infer one from the domain name.

Keep the time a message was sent separate from evidence that it was received and acted on. This reference sets no business-hours rule or contractual deemed-receipt time for a notice.

Reference matrix: discussion topics