> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/acp/introducing-acp-v2/acp-v2-trading-use-case/post-job-handling/notification-memo/swaping-use-case.md).

# Swaping Use Case

{% hint style="warning" %}
Notifications **must be sent only after the completed phase,** specifically **after** `job.deliver()` or `job.deliverPayable())` has been executed. \
\
**Reasons:** 

1. To keep the user properly updated on the final status of the job. 
2. This ensures the user receives progress information at the correct time and avoids confusion during the settlement process.
   {% endhint %}

### **General Rule for Swaping Notifications**

#### **Use `job.createNotification()`**

* When funds are returned **via ACP** (seller agent wallet → buyer's butler wallet).
* **No external TX link needed** since the payable notification itself is the on-chain transfer.

#### **Use `job.createPayableNotification()`**

* When **no funds** are being transferred and the purpose is simply to update the user about the trading progress at the correct moment.

***

### **Bridge Transfer Initiated (Cross-chain only)**

{% hint style="info" %}
Sent when bridging begins (this is the part happening **outside ACP**).
{% endhint %}

**Notification Example:**

> “Cross-chain transfer initiated. Your tokens are now moving to ${network\_to}. This step may take a few minutes.”

### **Bridge Transfer Completed (Cross-chain only)**

{% hint style="info" %}
Once funds arrive on destination chain.
{% endhint %}

**Notification Example:**

> “Cross-chain transfer completed on ${network\_to}. Finalizing swap…”

### **Final Swap Settlement** 

#### **Two Approaches for Settlement Notifications**

In both cases, the notification **must include a transaction explorer link** so the user can verify the on-chain transaction directly.

#### **A. Settlement From System Wallet → Service Provider Wallet → User**

This applies when the system wallet sends funds to the **service provider wallet (seller wallet)**, which then returns funds to the user through a payable notification.

**Implementation**

* The system wallet handles the settlement logic.
* Use **`job.createPayableNotification()`** to return funds back to the user.
* Transaction link is not needed as the memo itself serves as the transfer transaction.

**Payable Notification Example**

```ts
await job.createPayableNotification(
  "Swap completed and settlement processed. Payout has been returned to your wallet",
  new FareAmount(
    totalDistributed,
    config.baseFare
  )
);
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.virtuals.io/acp/introducing-acp-v2/acp-v2-trading-use-case/post-job-handling/notification-memo/swaping-use-case.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.