more refinement

Author: alexphelps

content/docs/apps/guides/dispute-service.mdx

@@ -12,14 +12,14 @@ Dispute service apps are integrations that manage the processing of payment disp
 <Callout type="info">
 Dispute Service Apps are [Server to Server Apps](/docs/apps/guides/server-to-server-apps) that use the Oauth flow to obtain API Access and then use the [Admin APIs](/docs/admin-api) and [Webhooks](/docs/webhooks) to subscribe to store event activity.
 </Callout>
-### Disputes
+## Disputes
 
 Disputes are complaints initiated by the customer against the merchant pertaining to their orders and are categorized into two broad groups by type, Alerts and Chargebacks, see below.
 
 - **Alerts** - disputes that are not yet a chargeback, ie TC40, SAFE, and RDR alerts.
 - **Chargeback** - disputes that are registered as a chargeback with the acquiring bank.
 
-### Dispute Flow Overview
+## Dispute Flow Overview
 
 Below is a high-level overview of a typical flow for a dispute service app to handle transaction disputes.
 
@@ -37,17 +37,17 @@ sequenceDiagram
   Dispute Service->>Store: Resolve dispute
 ```
 
-### Dispute Flow Detail
+## Dispute Flow Detail
 
-#### Step 1 - New Transaction Created
+### Step 1 - New Transaction Created
 There are several scenarios that create new payment transactions:
 - Order created - nearly all new orders start with a new payment transaction.
 - Upsell created - adding an upsell creates a new payment transaction.
 - Refund created - refunding a order creates a refund transaction.
 
 Orders typically have many associated transactions for the payments and refunds.
 
-#### Step 2 - `transaction.created` webhook event
+### Step 2 - `transaction.created` webhook event
 Dispute service apps should subscribe to the `transaction.created` webhook event to be notified of all payment transaction events on a store so that your app is aware of new payments, refunds, and can handle disputes properly.
 
 <Callout type="info" title="Use `parent_id` to associate related transactions">
@@ -61,41 +61,41 @@ Your app can also subscribe to `order.created` and `order.updated` events to rec
 Create your webhook after the app is installed using the [webhooksCreate](/docs/admin-api/reference/webhooks/webhooksCreate) Admin API and pass the `transaction.created, order.created, order.updated` to subscribe to these events.
 
 
-#### Step 3 - Dispute service receives transaction dispute
+### Step 3 - Dispute service receives transaction dispute
 
 At this stage, the dispute service is responsible for receiving disputes from their integration partners.
 
-#### Step 4 - Dispute service creates dispute (alert or chargeback) in store
+### Step 4 - Dispute service creates dispute (alert or chargeback) in store
 
 When disputes are identified as belonging to a store, the dispute service should create a new dispute using the [disputesCreate](/docs/admin-api/reference/payments/disputesCreate) Admin API.
 
 
-#### Step 5 - Dispute service matches dispute to transaction
+### Step 5 - Dispute service matches dispute to transaction
 
 Disputes created in the store need to be matched to the transaction in the store to associate it with the order/customer. Disputes can be matched by passing the `transaction` parameter when creating or with update using the [disputesUpdate](/docs/admin-api/reference/payments/disputesUpdate) Admin API. See example below in [Match a Dispute](#matching-disputes).
 
 
-#### Step 6 - Customer is added to block lists
+### Step 6 - Customer is added to block lists
 
 Merchants can configure their store to automatically add customers to block lists when any of their transactions have been disputed to mitigate future risk from the customer and associated payment methods. See [Block Lists](https://docs.29next.com/features/payments/block-lists) guide in our user docs.
 
 
-#### Step 7 - Dispute service creates refund
+### Step 7 - Dispute service creates refund
 
 Depending on the type of dispute, the dispute service may need to create a refund using the [transactionsRefundCreate](/docs/admin-api/reference/payments/transactionsRefundCreate) Admin API to resolve the dispute. See [Create a Refund](#creating-disputes) detail below.
 
 
-#### Step 8 - Cancel Order / Cancel Fulfillment 
+### Step 8 - Cancel Order / Cancel Fulfillment 
 
 If the order is not yet fulfilled, it may be ideal to cancel the order or cancel fulfillment to stop the order from being shipped to the customer. See [Canceling Fulfillment](#canceling-fulfillment) detail below.
 
 
-#### Step 9 - Dispute service resolves dispute
+### Step 9 - Dispute service resolves dispute
 
 Once the dispute is resolved, the dispute service should set the dispute resolution using the [disputesUpdate](/docs/admin-api/reference/payments/disputesUpdate) Admin API. See [Dispute Resolutions](#dispute-resolutions) and [Resolve a Dispute](#resolving-disputes) detail below.
 
 
-### Creating Disputes
+## Creating Disputes
 
 To create a dispute in the store using the [disputesCreate](/docs/admin-api/reference/payments/disputesCreate) Admin API, see example below:
 
@@ -111,7 +111,7 @@ To create a dispute in the store using the [disputesCreate](/docs/admin-api/refe
 }
 ```
 
-### Matching Disputes
+## Matching Disputes
 
 To match a dispute to a transaction, pass the `transaction` id to the [disputesUpdate](/docs/admin-api/reference/payments/disputesUpdate) API. Matching the dispute to the transaction will match the associated order and customer.
 
@@ -122,7 +122,7 @@ To match a dispute to a transaction, pass the `transaction` id to the [disputesU
 }
 ```
 
-### Creating Refunds
+## Creating Refunds
 
 To create a refund for a transaction as part of the dispute resolution process, you can use the [transactionsRefundCreate](/docs/admin-api/reference/payments/transactionsRefundCreate) Admin API.
 
@@ -133,7 +133,7 @@ To create a refund for a transaction as part of the dispute resolution process,
 }
 ```
 
-### Canceling Fulfillment
+## Canceling Fulfillment
 
 It's desirable to cancel fulfillment for orders that have not shipped yet when they are disputed to prevent additional losses for the merchant.
 
@@ -173,7 +173,7 @@ Fulfillment locations need to accept the cancelation request to confirm they wer
 </Tab>
 </Tabs>
 
-### RDR Alerts
+## RDR Alerts
 
 RDR Alerts are automatically refunded with the gateway, dispute services should log an external refund for the transaction using the [transactionsRefundCreate](/docs/admin-api/reference/payments/transactionsRefundCreate) Admin API.
 
@@ -188,7 +188,7 @@ Setting `is_external: true` on a refund will create the refund without attemptin
 ```
 
 
-### Dispute Resolutions
+## Dispute Resolutions
 
 **Alert Resolutions**
 
@@ -207,7 +207,7 @@ Setting `is_external: true` on a refund will create the refund without attemptin
 - `lost` - The chargeback representment process was unsuccessful.
 
 
-### Resolving Disputes
+## Resolving Disputes
 
 To resolve a dispute, update the dispute with the appropriate [resolution](#dispute-resolutions) for the dispute type.
 

content/docs/apps/guides/fulfillment-service.mdx

@@ -14,7 +14,7 @@ Fulfillment service apps are integrations that manage fulfillment of physical pr
 <Callout type="info">
 View a fully functional [Demo Fulfillment Service App](https://github.com/NextCommerceCo/demo-fulfillment-service-app) to see all of the concepts in action with detailed code examples.
 </Callout>
-### Fulfillment Flow Overview
+## Fulfillment Flow Overview
 
 Below is a high-level overview of the fulfillment flow for fulfillment services to accept and process assigned fulfillment orders.
 
@@ -30,36 +30,36 @@ sequenceDiagram
   Carrier->>Customer: Carrier Delivers Ordered Products to Customer
 ```
 
-#### Fulfillment Flow Detail
+### Fulfillment Flow Detail
 
-#### Step 1 - New Order Created
+### Step 1 - New Order Created
 
 All orders start with a customer creating a new order in the Checkout Flow, Admin API, or a recurring Subscription. Orders contain multiple [Fulfillment Orders](#fulfillment-orders), each with the products allocated to the same [Fulfillment Location](#fulfillment-locations) that has the products in stock.
 
-#### Step 2 - Store Creates a Fulfillment Request
+### Step 2 - Store Creates a Fulfillment Request
 
 After a delay period (usually several hours), the store will send a fulfillment request to the [Fulfillment Location](#fulfillment-locations) assigned to the order. Fulfillment Requests can be initiated by dashboard users, background processes, or via the Admin API. See [Fulfillment Locations](#fulfillment-locations).
 
-#### Step 3 - Fulfillment Service Retrieves Assigned Fulfillment Orders
+### Step 3 - Fulfillment Service Retrieves Assigned Fulfillment Orders
 
 In response to receiving a fulfillment request, the fulfillment service needs to retrieve all of their assigned fulfillment orders from the [Assigned Fulfillment Orders](/docs/admin-api/reference/fulfillment/assignedFulfillmentOrdersList) API endpoint. See [Assigned Fulfillment Orders](#assigned-fulfillment-orders).
 
-#### Step 4 - Fulfillment Service Accepts Fulfillment Request
+### Step 4 - Fulfillment Service Accepts Fulfillment Request
 
 For each assigned fulfillment order request in Step 3, the fulfillment service needs to `Accept` or `Reject` the assignment to notify the store the order is expected to be fulfilled or not. See [Accepting Fulfillment Requests](#accepting-fulfillment-requests).
 
-#### Step 5 - Fulfillment Service Processes Fulfillment Order with Carrier
+### Step 5 - Fulfillment Service Processes Fulfillment Order with Carrier
 
 Accepted fulfillment orders are processed by the fulfillment service location to prepare shipment to the customer.
 
-#### Step 6 - Fulfillment Service Creates a Fulfillment
+### Step 6 - Fulfillment Service Creates a Fulfillment
 
 Once an order has been fulfilled, the fulfillment service creates a fulfillment to upload with shipment carrier tracking information and notify the customer their order has shipped. See [Creating Fulfillments](#creating-fulfillments).
 
-#### Step 7 - Carrier Delivers Ordered Products to Customer
+### Step 7 - Carrier Delivers Ordered Products to Customer
 The carrier is responsible for delivering the products to the customer in this stage.
 
-### Fulfillment Orders
+## Fulfillment Orders
 
 A Fulfillment Order represents items in an order that are to be fulfilled from the same location. A single order often contains multiple fulfillment orders, it's important to keep this in mind for your integration.
 
@@ -72,13 +72,13 @@ graph
   FO2-->P2[Product Y Qty 1 <br> Product Z Qty 2]
 ```
 
-### Fulfillment Locations
+## Fulfillment Locations
 
 Fulfillment Services need to create `Locations` which represent their warehouses where physical products are stored and fulfilled from. Product `stockrecords` must be associated with a location for fulfillment.
 
 When new orders are created, the fulfillment orders are assigned to the locations based on [Fulfillment Routing](https://docs.29next.com/features/fulfillment-guide/location-based-routing). The Location Address is also used for Tax calculation. See the [Locations Create](/docs/admin-api/reference/fulfillment/locationsCreate) endpoint to create a location.
 
-#### Location Callback
+### Location Callback
 The location `callback` is a URL the store will send `Fulfillment Request` webhooks to notify them of a new fulfillment assigned. Fulfillment Services need to query their [Assigned Fulfillment Orders](#assigned-fulfillment-orders) to retrieve the fulfillment order details.
 
 <Callout type="warn">
@@ -113,7 +113,7 @@ Fulfullment Requests are sent to the location `callback` + `/fulfillment-order-n
 <Callout type="idea">
 The webhook request has a `X-29Next-Store` header that indicates which store the request is from if you have a global callback url.
 </Callout>
-### Assigned Fulfillment Orders
+## Assigned Fulfillment Orders
 The [Assigned Fulfillment Orders](/docs/admin-api/reference/fulfillment/assignedFulfillmentOrdersList) will return a list of all fulfillment orders assigned to your locations. Your app is recommended to call this API in response to receiving a notification to the location callback, and you may also want to poll this endpoint occasionally (ie once per hour) to ensure you've actioned everything requested.
 
 <Callout type="info">
@@ -145,15 +145,15 @@ Requests to the location callback indicate the request `type` that should be pas
 
 For example, to see new fulfillment requests pending acceptance, pass `assignment_status=fulfillment_requested` to the Assigned Fulfillment Orders API, `fulfillment_requested` was passed as `type` to the callback.
 </Callout>
-### Accepting Fulfillment Requests
+## Accepting Fulfillment Requests
 
 To `Accept` a Fulfillment Request assignment, send a POST request to the [Fulfillment Request Accept](/docs/admin-api/reference/fulfillment/fulfillmentRequestAccept) Endpoint. The Fulfillment Order will show as **Accepted** in the dashboard and the Order will transition fulfillment_status to processing.
 
 ```json title="Example Fulfillment Accept Request"
 POST https://{store}.29next.store/docs/admin-api/fulfillment-orders/{id}/fulfillment-request/accept/
 ```
 
-### Rejecting Fulfillment Requests
+## Rejecting Fulfillment Requests
 
 Your fulfillment service can `Reject` fulfillment order assignments which will prompt the merchant to take action in their store to amend the order. Rejecting fulfillment requests can be for many reasons, such as incorrectly assigned for unavailable products, no stock available, or invalid address. The Fulfillment Service should verify the order details before accepting, by rejecting the fulillment request it will prompt the merchant to correct the order and then send an updated fulfillment request. See possible rejection reasons on in the [Fulfillment Request Reject API docs](/docs/admin-api/reference/fulfillment/fulfillmentRequestReject).
 
@@ -166,7 +166,7 @@ POST https://{store}.29next.store/docs/admin-api/fulfillment-orders/{id}/fulfill
 ```
 
 
-### Cancellation Flow Overview
+## Cancellation Flow Overview
 
 It is common for customers to contact merchants after orders have already been sent to fulfillment service partners for processing. Merchants have the ability to "Request Fulfillment Cancellation" which will send a `cancellation_request` to your [Location Callback](#location-callback). Fulfillment Services are expected to respond to these requests.
 
@@ -178,12 +178,12 @@ sequenceDiagram
   Fulfillment Service App->>Store: Accept/Reject Cancellation Requests
 ```
 
-#### Cancellation Flow Detail
-#### Step 1 - Store Creates Cancellation Request
+### Cancellation Flow Detail
+### Step 1 - Store Creates Cancellation Request
 
 Merchants will trigger a cancellation request which will send a cancellation request to the [Fulfillment Location](#fulfillment-locations) assigned to the order.
 
-#### Step 2 - Fulfillment Service Retrieves Cancellation Requests
+### Step 2 - Fulfillment Service Retrieves Cancellation Requests
 
 In response to receiving a cancellation request, the fulfillment service needs to retrieve all of its assigned cancellation requests from the [Assigned Fulfillment Orders](/docs/admin-api/reference/fulfillment/assignedFulfillmentOrdersList) API endpoint.
 
@@ -192,11 +192,11 @@ In response to receiving a cancellation request, the fulfillment service needs t
 GET https://{store}.29next.store/docs/admin-api/assigned-fulfillment-orders/?assignment_status=cancellation_requested
 ```
 
-#### Step 3 - Fulfillment Service Accepts/Rejects Cancellation Request
+### Step 3 - Fulfillment Service Accepts/Rejects Cancellation Request
 
 At this stage, the Fulfillment Service needs to [Accept](#accepting-cancellation-requests) or [Reject](#rejecting-cancellation-requests) the cancellation request to respond to the merchant's request.
 
-### Accepting Cancellation Requests
+## Accepting Cancellation Requests
 
 To `accept` the cancellation request, send a request to the [Cancellation Request Accept API](/docs/admin-api/reference/fulfillment/cancellationRequestAccept).
 
@@ -206,7 +206,7 @@ POST https://{store}.29next.store/docs/admin-api/fulfillment-orders/{id}/cancell
 ```
 
 
-### Rejecting Cancellation Requests
+## Rejecting Cancellation Requests
 If an fulfillment order is too far along in fulfillment processing, fulfillment service partners can reject cancellation requests.
 
 To `reject` a cancellation request, send a request to the [Cancellation Request Reject API](/docs/admin-api/reference/fulfillment/cancellationRequestReject). If you include a message, it will show in the order timeline events for the merchant to see.
@@ -219,7 +219,7 @@ POST https://{store}.29next.store/docs/admin-api/fulfillment-orders/{id}/cancell
 }
 ```
 
-### Creating Fulfillments
+## Creating Fulfillments
 
 Once you have tracking information for your the outgoing shipment to the customer, create a Fulfillment for the fulfillment order on the [Fulfillments Create](/docs/admin-api/reference/fulfillment/fulfillmentsCreate) API.
 
@@ -237,7 +237,7 @@ POST https://{store}.29next.store/docs/admin-api/fulfillment-orders/{id}/fulfill
 }
 ```
 
-### Sync Product Inventory
+## Sync Product Inventory
 
 Products have "stock records" which represent the available physical stock at a fulfillment location. Often a single product can be stocked at multiple locations, with [Fulfillment Routing](https://docs.29next.com/features/fulfillment-guide/location-based-routing) governing the order fulfillment location assignment.
 
@@ -249,7 +249,7 @@ flowchart TD
     B-->E("Location 3")
 ```
 
-#### Retrieve Stock Records by Location
+### Retrieve Stock Records by Location
 
 Fulfillment services can retrieve all stock records from a store to map with the SKUs at their warehouse. You can also search and filter by product name or SKU, see Admin API docs for [stockrecordsRetrieve](/docs/admin-api/reference/products/stockrecordsRetrieve).
 
@@ -260,7 +260,7 @@ GET https://{store}.29next.store/docs/admin-api/stockrecords/?location_id={id}
 With the list of stock records assigned to your location, you can now update the `num_in_stock` to reflect the current available units.
 
 
-#### Update Number of Units In Stock
+### Update Number of Units In Stock
 
 Fulfillment services are recommended to update the number in stock (`num_in_stock`) at regular intervals so that the store inventory is update to date and accurate.
 
@@ -272,7 +272,7 @@ PATCH https://{store}.29next.store/docs/admin-api/stockrecords/{id}/
 }
 ```
 
-### Moving Fulfillment Orders
+## Moving Fulfillment Orders
 
 
 import MoveFulfillmentOrders from '../../../_snippets/_moving-fulfillment-orders.mdx';

content/docs/apps/guides/server-to-server-apps.mdx

@@ -14,7 +14,7 @@ Server to Server apps don't need to upload any "code" or files to Next Commerce,
 </Callout>
 In this guide, we'll show you how to create your first app to get you up and running and familiar with many of the concepts.
 
-### Preparation
+## Preparation
 
 1. If you haven't done so already, create your [Next Commerce account](https://accounts.29next.com) and complete your [Partner Registration](https://accounts.29next.com/partners/).
 
@@ -26,14 +26,14 @@ import DevelopmentStore from '../../../_snippets/_offer-development-store.mdx';
 <DevelopmentStore name="Development Store Offer" />
 
 
-### Create Your App
+## Create Your App
 
 1. Inside your Partner Account, navigate to Apps and then Create App. Follow the form to create your first app, don't worry about the App name and details, you can change this later.
 
 2. After creating your App, you'll be able to see your App details. Take note of your `Client ID` and `Client Secret` which are used in the [OAuth flow](/docs/apps/oauth) to retrieve an API Access Token during the [App Install flow](/docs/apps/oauth/getting-started).
 
 
-### Configure App Oauth
+## Configure App Oauth
 
 Server-to-Server apps use follow the [OAuth flow](/docs/apps/oauth) to get and Admin API Access Token, let's add the [Oauth 2.0 <debugger/>](https://oauthdebugger.com/) urls to our app to simulate the install flow.
 
@@ -42,7 +42,7 @@ Server-to-Server apps use follow the [OAuth flow](/docs/apps/oauth) to get and A
 2. Install your app on your store using the **Install Link** tool on your App Overview.
 
 
-### Test App On Development Store
+## Test App On Development Store
 
 1. You can now use [Oauth Debugger](https://oauthdebugger.com/) to simulate the Oauth flow.