feat: update README for payment process clarity and enhance success notification button behavior
This commit is contained in:
12
README.md
12
README.md
@@ -106,10 +106,12 @@ To access admin pages follow these steps:
|
||||
1. Customer adds analysis to cart in **B2B** storefront
|
||||
2. Customer checks out from cart and is redirected to **Montonio**
|
||||
3. Customer pays and is redirected back to **B2B** `GET B2B/home/cart/montonio-callback?order-token=$JWT`
|
||||
- **Medusa** order is created and cart is emptied
|
||||
- email is sent to customer
|
||||
- B2B sends order XML as private message to Medipost.
|
||||
When **Montonio** has confirmed payment, it will call **Medusa** webhook endpoint and **Medusa** will mark order payment as captured.
|
||||
|
||||
- **Medusa** order is created and cart is emptied
|
||||
- email is sent to customer
|
||||
- B2B sends order XML as private message to Medipost.
|
||||
|
||||
When **Montonio** has confirmed payment, it will call **Medusa** webhook endpoint and **Medusa** will mark order payment as captured.
|
||||
|
||||
In background a job will call `POST B2B/api/job/sync-analysis-results` every n minutes and sync private messages with responses from **Medipost**.
|
||||
|
||||
@@ -121,7 +123,7 @@ In local dev environment, you can import products from B2B to Medusa with this A
|
||||
|
||||
- `POST /api/job/sync-analysis-groups-store`
|
||||
- Syncs required data of `analyses`, `analysis_elements` data from **B2B** to **Medusa** and creates relevant products and categories.
|
||||
If product or category already exists, then it is not recreated. Old entries are not deleted either currently.
|
||||
If product or category already exists, then it is not recreated. Old entries are not deleted either currently.
|
||||
|
||||
## Jobs
|
||||
|
||||
|
||||
Reference in New Issue
Block a user