Skip to content

Add guide for supporting payments from and to C accounts#2092

Merged
briwylde08 merged 6 commits intomainfrom
c-account-support-exchanges
Dec 5, 2025
Merged

Add guide for supporting payments from and to C accounts#2092
briwylde08 merged 6 commits intomainfrom
c-account-support-exchanges

Conversation

@brunomlr
Copy link
Copy Markdown
Contributor

@brunomlr brunomlr commented Dec 4, 2025

Introduces documentation explaining how to send and receive payments to and from C-Accounts on the Stellar network. Covers differences in protocol, handling memos, using Horizon and RPC APIs, and provides code example references for developers integrating C-Account support.

Introduces documentation explaining how to send and receive payments to and from C-Accounts on the Stellar network. Covers differences in protocol, handling memos, using Horizon and RPC APIs, and provides code example references for developers integrating C-Account support.
@stellar-jenkins
Copy link
Copy Markdown


To enable support for deposits coming from C addresses, nothing needs to change in the information displayed to customers or the deposit accounts used by the exchange. Wallets will still use the G account and memo provided to send a payment to the exchange's G address including the memo with the unique ID.

That's the main difference between receiving from customers using G or C accounts: instead of looking at the memo field to identify the individual account, you'll look at the muxed ID. Everything else stays the same.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably introduce the term "muxed ID" somewhere before using it

@stellar-jenkins
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@tomerweller tomerweller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. This is awesome.

On muxed/memo ids I think we do a good job in explaining how to receive payments, but wallets might need some guidance on how to send.

If the wallet is presented with an address plus a memo id, what is it expected to do? Send a payment and add a memo id? make a payment to a muxedaccount? invoke a sac transfer with a muxedaccount? How does that change for contract account senders vs. classic senders?

Similar, but what is a client expected to do when presented with an M address?

@stellar-jenkins
Copy link
Copy Markdown

* Include section about Sending payments from C-accounts that require a memo
* Introduce memo limitations before presenting alternative methods
@stellar-jenkins
Copy link
Copy Markdown

@stellar-jenkins
Copy link
Copy Markdown

@stellar-jenkins
Copy link
Copy Markdown

@briwylde08 briwylde08 merged commit b41298c into main Dec 5, 2025
10 checks passed
@briwylde08 briwylde08 deleted the c-account-support-exchanges branch December 5, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants