There is a tutorial on create_send so this post will only highlight memo-related differences.

create_send can contain a memo (reference, note to recipient) to reference a transaction to off-blockchain data such as the sender’s account at a crypto-exchange or member’s account in an online game.

Required non-default inputs to create_send are:

use_enhanced_send: true or false (default: false)

memo_is_hex: true or false

memo: unique content provided by the recipient (note the emphasis)

Knowing this, the operator needs to provide this information to the user and the user has to use the provided memo string in “Memo” field when funding his account.

Let’s say Alice is a gamer known as FragKingLord at her favorite online game provider C-Gaming. She logs in and requests a funding address. The provider generates a funding address mhannsH8oupuQYen3AxbUebhWFVz2c9ams and memo string FragKingLord. She wants to fund her account with 1000 CTOKENs. (Note that it may seem that Alice could later make repeated transactions the same way, but she should not assume the funding address has not changed, so it is a good practice to use a random hex string to not give the user the impression that the funding address and memo are valid for repeated transactions)

Alice next logs in to her Counterparty wallet where she enters the destination address, memo string, and the amount of 1000 CTOKENs. Her wallet creates a transaction that looks like this (source is the wallet address from which she’s sending).

Normally (say, in Counterwallet), the wallet will ask for a confirmation to Send, after which this transaction will be locally (in the wallet) signed with the private key of the source address and then sent to the Bitcoin network.

Once this transaction has received enough confirmations, C-Gaming will credit FragKingLord’s account with 1000 CTOKENs.