From 335edeb7372edd572608cda41ceb4a64da771d50 Mon Sep 17 00:00:00 2001 From: Hamed Panjeh Date: Wed, 13 Dec 2023 15:56:31 -0300 Subject: [PATCH] Update readme --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6766389..44fc598 100644 --- a/README.md +++ b/README.md @@ -85,11 +85,12 @@ enum WalletEnums: string } ``` -You have complete freedom to name your wallets as per your requirements and even add more wallet types to the Enum list. +**You have complete freedom to name your wallets as per your requirements and even add more wallet types to the Enum list.** -In this particular setup, `wallet_1` (`WALLET1`) is given the highest priority. When an order payment is processed, the system will first attempt to use `wallet_1` to cover the cost. If `wallet_1` does not have sufficient funds, `wallet_2` (`WALLET2`) will be used next. +In this particular setup, `wallet_1` (`WALLET1`) is given the **highest priority**. When an order payment is processed, the system will first attempt to use `wallet_1` to cover the cost. If `wallet_1` does not have sufficient funds, `wallet_2` (`WALLET2`) will be used next. +### Example: If the balance in `wallet_1` is 10 and the balance in `wallet_2` is 20, and you need to pay an order value of 15, the payment process will first utilize the entire balance of `wallet_1`. Since `wallet_1`'s balance is insufficient to cover the full amount, the remaining 5 will be deducted from `wallet_2`. After the payment, `wallet_2` will have a remaining balance of 15." ## Usage, APIs and Operations: