# Transfer (Updating)

<table><thead><tr><th width="113">Key</th><th width="131.33333333333331">Required</th><th>Description</th></tr></thead><tbody><tr><td>p</td><td>yes</td><td><p>Protocol: <em><code>orc-20</code></em> or <em><code>orc20</code></em> <strong>case-insensitive.</strong> </p><p>For wider adoption, any ordinal tokens supporting ORC-20 implementation (like src-20, xrc-20, including wrapped BRC-20) can be included.</p></td></tr><tr><td>tick</td><td>yes</td><td>Ticker: symbol of ORC-20 in any size, eg. ORC = orc</td></tr><tr><td>id</td><td>yes</td><td><p>Identifier: inscription number.</p><p><strong>Subsequent operations must use inscription number.</strong></p><p>eg. initial ORC-20 deployment doesn't require id; but you must specify inscription number of the deployment for subsequent mint, send, migration, and upgrade.</p></td></tr><tr><td>op</td><td>yes</td><td><p>Operation: send event </p><p>Type of event: eg. deploy, mint, send, cancel.</p></td></tr><tr><td>n</td><td>yes</td><td>Nonce: keep track of each partial transaction</td></tr><tr><td>amt</td><td>yes, when sender is not receiver</td><td>Send Amount: always set amount If sender is not the receiver; default to the remaining balance when sending back to sender. </td></tr><tr><td>msg</td><td>no</td><td>Message: custom text, message, manifesto in any size</td></tr></tbody></table>

**Example:** Send `1000` `orc` (Deploy ID Inscription #2504160) in two partial transactions. Each transaction must have unique nonce.

* **Step 1:** send `1000` (nonce 5) to the receiver address by inscribing send event to receiver

```
{ 
  "p": "orc-20",
  "tick": "orc",
  "id": "2504160",
  "op": "send",
  "n": "5",
  "amt": "1000"
}
```

* **Step 2:** send the remaining balance back to the sender by inscribing send event to sender

```
{ 
  "p": "orc-20",
  "tick": "orc",
  "id": "2504160",
  "op": "send",
  "n": "6"
}
```