Docs - Create Integration Approaches comparison page

[MantisClone]

Problem

Multiple use case pages (Invoicing, Checkout, Payouts, Payroll, Subscriptions) need to explain integration approaches (Payment Widget, Easy Invoice, Fork EasyInvoice, Custom API), but including full comparison on each page creates duplication. Currently linking to non-existent /resources/integration-approaches.

Proposed Solution

Create /resources/integration-approaches.mdx with detailed comparison covering:

Four approaches:

1. Payment Widget Button: shadcn component, React, pre-built UI, wallet connection included (most relevant for Checkout)
2. Easy Invoice: Hosted platform, no-code, ready to use immediately for invoicing and e-commerce
3. Fork EasyInvoice: Clone and customize the open-source application to match your brand and needs
4. Custom API: Full control, white-label, custom implementation using Request Network API

Comparison dimensions:

• Development effort and time to launch
• Customization capabilities
• Fee structures (if different between approaches)
• Currency/chain support differences (if any)
• Maintenance responsibilities
• Technical requirements (React for widget, API keys for all)
• Decision matrix: when to choose each option
• Use case applicability (which approaches work best for which use cases)

Checkout-specific considerations:

• Payment Widget Button is the primary drop-in option for checkout flows
• Easy Invoice e-commerce features (Client ID management for app builder model)
• Fork option allows full checkout customization

Considerations

• Should this be a simple comparison table or detailed guide? (Recommend: simple table + brief descriptions)
• Need to verify if fee structures actually differ between approaches (or if all use same Request Network fees)
• Should include links to each option's documentation
• Will be referenced by all use case pages via Info callout (Invoicing, Checkout, Payouts, Payroll, Subscriptions)
• Consider adding visual decision tree or flowchart for scannability
• Should align with welcome page messaging about integration options
• Checkout use case has unique needs (Payment Widget Button) compared to other use cases

[MantisClone]

Using EasyInvoice directly is not an integration option, but we can still add a link to it to direct viewers to the right place.