docs: mi/170/add-use-cases (#524)

* docs: mi/170/add-use-cases

Added use case section to overview page.  Will link to remaining guides as they become available.

* docs: mi/170/add-use-cases

- Revised texts for peer-to-peer payments, e-commerce, and Web Monetization use cases, borrowing heavily from the use cases section from Rafiki docs.

- Added a BNPL use case

* docs: mi/170/add-use-cases

* docs: mi/170/add-use-cases

Added link to e-commerce example using the Open Payments SDK

* docs: mi/170/add-use-cases

Reran prettier even though I had it run the first time.

* docs: mi/170/add-use-cases

Updated peer-to-peer payments text.

* mi/170/add-use-cases

* docs: mi/170/add-use-case

docs/src/content/docs/introduction/overview.mdx

@@ -67,3 +67,35 @@ When an ASE adopts the Open Payments standard, clients (applications and other p
 - ASEs and clients to create and deploy custom integrations to communicate with one another
 
 Open Payments aims to simplify and democratize payments by providing a standardized, easy-to-integrate solution. This reduces development effort and enhances financial inclusion by making payment solutions more affordable and accessible to all.
+
+## Use cases
+
+Open Payments facilitates various use cases including:
+
+### Peer-to-peer payments
+
+A peer-to-peer payment is a type of payment made directly from one person to another via a linked funding source. When ASEs implement the Open Payments standard, applications can call the Open Payments APIs to facilitate peer-to-peer payments. Having a standard means app developers can avoid building custom integrations for each ASE. Plus, app users can hold funding accounts with different Open Payments-enabled ASEs and even use different Open Payments-enabled applications to make peer-to-peer payments.
+
+A peer-to-peer payment can be one-time or recurring. For more information on building an Open Payments client that supports either type, refer to the [one-time payment](/guides/make-onetime-payment) and [recurring payments](/guides/make-recurring-payments) guides.
+
+### E-commerce platforms
+
+Suppose a merchant accepts Open Payments as a payment method. Their customers can then pay using their wallet address instead of entering a credit card number and other personal details on the merchant’s site. Open Payments allows an ASE's account holders to use their wallet addresses for one-time and recurring purchases, such as subscriptions. Refer to the following resources for more details:
+
+- [One-time payment guide](/guides/make-onetime-payment)
+- [Recurring payments guide](/guides/make-recurring-payments)
+- <LinkOut href='https://github.com/interledger/open-payments/tree/main/packages/open-payments#example'>
+    E-commerce example using the Open Payments SDK
+  </LinkOut>
+
+### Buy Now and Pay Later (BNPL)
+
+Buy Now and Pay Later (BNPL) plans allow customers to pay for high-priced purchases over time. A customer is relieved from making a large payment at once by splitting up payments at scheduled intervals. Developers can build Open Payments applications that support BNPL plans through recurring payments. For more details, refer to the [recurring payments guide](/guides/make-recurring-payments).
+
+### Web Monetization
+
+The <LinkOut href='https://webmonetization.org'>Web Monetization</LinkOut> is a new
+standard and API that allows website visitors to pay an amount they choose to a
+participating website with little to no interaction using Open Payments as the
+payment method. The site and the site visitor must have an Open Payments-enabled
+wallet address to receive and send payments.