> For the complete documentation index, see [llms.txt](https://docs.safle.com/safleid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.safle.com/safleid/safle-wallet/transaction-processing-on-multiple-chains.md).

# Transaction processing on multiple Chains

**Send funds to a SafleID**

Safle users can send funds to other safle users without having to know about the recipients public address directly to their SafleID’s. This removes the need to share long alphanumeric public addresses and thus reduces the chances of error.

### User flow

1. User selects network and sender wallet
2. Client calls change network method of vault SDK

   <pre class="language-javascript" data-overflow="wrap" data-full-width="true"><code class="lang-javascript">await vault.changeNetwork(chain)
   </code></pre>

   * `chain` : Name of chain from the supported chains
3. Enters recipients SafleID
4. Client calls safle-identity-wallet SDK to get public address for the corresponding safleID.\ <mark style="background-color:yellow;">`💡`</mark><mark style="background-color:yellow;">This SDK abstracts the safleID smart contracts to enable a seamless development of client applications. More details</mark> [<mark style="background-color:yellow;">here</mark>](https://github.com/getsafle/safle-identity-wallet)

   <pre class="language-javascript" data-overflow="wrap" data-full-width="true"><code class="lang-javascript">const address = safle.getAddress()
   </code></pre>
5. Client app build a raw transaction with the user’s input
6. User proceeds to sign transaction. Enters vault pin to proceed
   1. Application calls vault method to sign raw transaction and enters pin

      <pre class="language-javascript" data-overflow="wrap" data-full-width="true"><code class="lang-javascript">const signedTransaction = await vault.signTransaction(rawTx, pin, chain);
      </code></pre>

      Returns the signed transaction string

      * `chain` - The chain for which the transaction is to be signed.
      * `rawTx` - The raw transaction object to be signed
      * `pin` - The pin to access the vault's private functions.
7. Signed transaction broadcasted by Client Application

   ![](https://prod-files-secure.s3.us-west-2.amazonaws.com/11344230-d69e-4a21-96e6-a71b74945f9f/14ac3b5e-a7b7-42d0-ad92-1dcebf421902/Transact_to_SafleID_\(1\).svg)

   <figure><img src="/files/Dst0BU6mD40nSioUmjOz" alt=""><figcaption></figcaption></figure>

### **Send funds to public address:**

#### User flow

1. User selects network and sender wallet
2. Client calls change network method of vault SDK

   <pre class="language-javascript" data-overflow="wrap" data-full-width="true"><code class="lang-javascript">await vault.changeNetwork(chain)
   </code></pre>

   * `chain` : Name of chain from the supported chains
3. Enters recipients public address
4. Client app build a raw transaction with the user’s input
5. User proceeds to sign transaction. Enters vault pin to proceed
   1. Application calls vault method to sign raw transaction and enters pin

      <pre class="language-javascript" data-overflow="wrap" data-full-width="true"><code class="lang-javascript">const signedTransaction = await vault.signTransaction(rawTx, pin, chain);
      </code></pre>

      Returns the signed transaction string

      * `chain` - The chain for which the transaction is to be signed.
      * `rawTx` - The raw transaction object to be signed
      * `pin` - The pin to access the vault's private functions.
6. Signed transaction broadcasted by client application<br>

   <figure><img src="/files/k1uhAK5LDmONDxQqFxWV" alt=""><figcaption></figcaption></figure>