You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/100-swap-api/5-payments-through-swap.md
+17-23
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ The Jupiter Swap API can be utilized such that you, a merchant can allow your cu
13
13
14
14
## Use Case
15
15
16
-
Let’s set the stage. You are selling a **jupcake!!!** to your customer and merchant might only accept in 1 USDC, but Alice only has 1 SOL for various reasons. Well, you’re at the right place! By using the Swap API, merchant can let customer pay in SOL while merchant still receive USDC in order to complete the payment for a jupcake.
16
+
Let’s set the stage. You are selling a **jupcake!!!** to your customer and merchant might only accept in 1 USDC, but your customer only has 1 SOL. Well, you’re at the right place! By using the Swap API, merchant can let customer pay in SOL while merchant still receive USDC in order to complete the payment for a jupcake.
Before we start getting a quote and swap transaction, for example sake, we will need to prepare your and Alice's accounts. In production scenario, you will need to dynamically pass this in and allow users to sign in their device interfaces.
38
+
Before we start getting a quote and swap transaction, for example sake, we will need to prepare both merchant and customer accounts. In production scenario, you will need to dynamically pass this in and allow users to sign in their device interfaces.
41
39
40
+
:::note
42
41
Do note that you will need to have already set up:
43
-
- A wallet in your machine to simulate yourself as the customer as the customer is the signer of the transaction (similar to how we set up in [Environment Setup](/docs/environment-setup)).
42
+
-**A wallet in your machine to simulate yourself as the customer as the customer is the signer of the transaction** (similar to how we set up in [Environment Setup](/docs/environment-setup)).
44
43
-`trackingAccount` is an additional Solana Account you can pass in to track only Jupiter transactions easily.
Copy file name to clipboardExpand all lines: docs/101-ultra-api/README.md
+1
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ The Jupiter Ultra API is the *only* API you ever need to experience or build the
19
19
|**Blazing fast**| 95% of all swaps are executed under 2 seconds via our proprietary transaction sending engine. |
20
20
|**MEV-protected**| The lowest incidence of MEV attacks across all existing applications, by far. |
21
21
|**Real-Time Slippage Estimator**| Intelligently derives the best possible slippage to use at the time of execution, balancing between trade success and price protection. |
22
+
|**Gasless Support**| Enables gasless transactions for users with certain tokens and trade sizes, you can identify this via the secondary signer in the transaction. |
22
23
|**One-stop shop**| Retrieve the user's balances, get a quote, execute the trade, and get the results of the trade, all within Ultra API without touching a single RPC or any other external API. |
23
24
|**World class support**| We handle the complexities of RPC connections, transaction landing, slippage protection and more. |
inputOrOutput:"In", // either "In" or "Out" mint, note that price-based orders auto withdraws the output tokens to the user's wallet every time the order is executed
Copy file name to clipboardExpand all lines: docs/600-routing/dex-integration.md
+1-10
Original file line number
Diff line number
Diff line change
@@ -25,16 +25,7 @@ As Solana grows and more DEXes are built, we have to be more cautious in the DEX
25
25
-**Traction**: We look at the traction of the DEX to ensure it has market demand and is well-used.
26
26
-**Team and backers**: This is a good indicator of the quality of the DEX if they are backed by or built by reputable or verifiable entities.
27
27
28
-
## Integration Guidelines
29
-
30
-
### Markets API
31
-
- This API should track all markets/pools that is listed or delisted, this will allow us to automatically track new markets as you add them to your DEX.
32
-
33
-
### Rust SDK
34
-
-[Your SDK should implement the following interface](#).
35
-
- We are soon migrating to a Rust SDK and so are asking all integrated DEXes to create a Rust SDK version or give access to the code for us to include.
36
-
37
-
## AMM Interface
28
+
### AMM Interface
38
29
39
30
To facilitate integration of your DEX into the Jupiter Core Engine:
40
31
- Provide a DEX SDK that works with the [Jupiter AMM Interface](https://docs.rs/crate/jupiter-amm-interface).
0 commit comments