> For the complete documentation index, see [llms.txt](https://loop-crypto.gitbook.io/old-loop-crypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://loop-crypto.gitbook.io/old-loop-crypto/learn/core-components/collecting-authorization.md).

# Collecting authorization

Companies can collect authorization from EOAs and multisig wallets. This is done via [hosted checkout page](/old-loop-crypto/technical-docs/archeticture/collecting-authorization/checkout-page.md) or [widget](#checkout-widget) for inbound payments or through our authorization widget for outbound payments. 

#### **Hosted checkout page** 

Loop provides a custom [hosted checkout page](/old-loop-crypto/technical-docs/archeticture/collecting-authorization/checkout-page.md) for each item with the type of "subscription, donation, fee, or one-time payment". This page is useful for companies accepting crypto payment and can be used as a [payment link](/old-loop-crypto/technical-docs/archeticture/collecting-authorization/checkout-page.md) or in a “[pay with crypto](/old-loop-crypto/technical-docs/archeticture/collecting-authorization/checkout-page/add-pay-with-crypto-button.md)” button. 

#### Checkout widget

For those that prefer, Loop provides checkout widget that can be integrated in the context of your company's website or application, to enable your customers to pay with crypto. The modal allows end users to give Loop authorization to enable autopay.

## Outbound payments or dApp integration

#### Authorization widget  

For applications that do not require a checkout page (i.e. display item's details), Loop provides a [widget](#modal) that allows users to easily provide authorization and can be embedded anywhere in an application. Like the checkout page, the modal uses information configured at the item level but only displays the `accepted tokens`.