#73 feat: shoprenter based payments

Based on the docs which is created in issue 72, create an implementation plan for integrating the shoprenter payment api.

The shoprenter payment api must be only used with shoprenter stores. Other stores can not be billed by shoprenter payment api.

@fszontagh I'm starting work on this issue now! I'll create a comprehensive implementation plan for integrating the ShopRenter Payment API based on the documentation from issue #72. The plan will ensure the payment API is exclusively used with ShopRenter stores and includes proper validation, security measures, and integration with our existing architecture.

✅ Implementation Plan Complete!

I've created a comprehensive implementation plan for integrating the ShopRenter Payment API into ShopCall.ai.

📄 Document Created

File: docs/shoprenter_payment_implementation_plan.md

Commit: 04aeba7 - View commit

🎯 Key Highlights

Critical Requirement (ENFORCED!)

⚠️ The ShopRenter Payment API can ONLY be used with ShopRenter stores.

The implementation plan includes strict validation at multiple levels:

• ✅ Frontend payment page rendering
• ✅ Backend payment creation endpoint
• ✅ Subscription management endpoints
• ✅ Webhook handlers

Any attempt to use ShopRenter Payment API with non-ShopRenter stores (Shopify, WooCommerce, etc.) will be rejected with clear error messages.

📋 Plan Contents

1. Architecture Overview

• Complete system flow from store connection to recurring billing
• Integration with existing ShopRenter OAuth implementation
• Payment webhook event handling

2. Database Schema

Two new tables:

• shoprenter_payment_plans - Subscription plans and status tracking
• shoprenter_payment_transactions - Payment history and invoice tracking

Updates to existing stores table for subscription management.

3. Backend Implementation

New Supabase Edge Functions:

• shoprenter-payment-create - Create payment plans
• shoprenter-payment-cancel - Cancel subscriptions
• shoprenter-payment-status - Check payment status
• shoprenter-payment-webhook - Handle payment events

Plus shared Payment API client library with built-in store validation.

4. Store Validation Logic

async function validateStoreForShopRenterPayment(storeId: string) {
  const store = await getStore(storeId);
  
  if (store.platform_name !== 'shoprenter') {
    throw new Error(
      'ShopRenter Payment API can only be used with ShopRenter stores'
    );
  }
  
  return true;
}

This validation is applied to every payment-related operation.

5. Payment Flow

1. Merchant connects ShopRenter store (already implemented ✅)
2. Merchant selects subscription plan
3. Backend validates platform = 'shoprenter' (CRITICAL!)
4. Create payment plan via ShopRenter Payment API
5. ShopRenter handles billing (automatic recurring charges)
6. Webhooks notify ShopCall.ai of payment events
7. Subscription status updated automatically

6. Security Measures

• ✅ HMAC signature validation for webhooks
• ✅ Store ownership verification
• ✅ Platform validation on every request
• ✅ Secure token management
• ✅ GDPR-compliant data handling

7. Testing Strategy

• Unit tests for store validation logic
• Integration tests for payment flow
• Webhook handler tests
• Manual end-to-end testing
• Security audit procedures

8. Deployment Timeline

7-week implementation plan:

• Week 1: Planning ✅ (Complete!)
• Week 2-3: Backend development
• Week 4: Frontend integration
• Week 5: Testing & QA
• Week 6: Deployment
• Week 7: Launch

🔑 Requirements Before Implementation

1. Request Payment API Credentials from ShopRenter Partner Support:

   • SHOPRENTER_PAYMENT_API_KEY
   • SHOPRENTER_PAYMENT_SECRET

2. Request Payment API Scopes in app registration:

   • payment:read
   • payment:write
   • billing:read
   • billing:write

3. Set up test environment with test ShopRenter store (already available)

📚 Complete Documentation

The implementation plan includes:

• ✅ Executive summary and objectives
• ✅ Background and context (leveraging existing ShopRenter integration)
• ✅ Critical requirements (platform validation)
• ✅ Complete database schema with migration script
• ✅ Full backend implementation with code examples
• ✅ Payment flow diagrams and user journey
• ✅ Store validation enforcement strategy
• ✅ Security considerations
• ✅ Comprehensive testing strategy
• ✅ 7-week deployment plan
• ✅ Timeline and milestones
• ✅ References and resources

🚀 Next Steps

1. Review this implementation plan with the team
2. Request Payment API credentials from ShopRenter (partnersupport@shoprenter.hu)
3. Approve database schema and create migration
4. Begin Phase 2 (Backend development)

💡 Key Benefits

✅ Native billing for ShopRenter merchants (billed through ShopRenter account) ✅ Simplified checkout (no separate payment details needed) ✅ Unified invoicing (all invoices in ShopRenter admin) ✅ Automatic VAT handling (Hungarian tax compliance) ✅ Better conversion rates (trust and familiarity) ✅ Platform-specific pricing (can offer different plans for ShopRenter stores)

The implementation plan is ready for review and provides a complete roadmap for integrating ShopRenter Payment API while ensuring it's exclusively used with ShopRenter stores. 🎉