ridendine-payment-distribution

Split customer payments among chefs, CoCos, drivers, and platform via Stripe Transfers API.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Ritenoob/ridedine --skill ridendine-payment-distribution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ridendine-payment-distribution
Source: https://github.com/Ritenoob/ridedine/tree/main/.claude/skills/ridendine-payment-distribution
Command: npx skills add https://github.com/Ritenoob/ridedine --skill ridendine-payment-distribution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stripe, @supabase/supabase-js, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complex challenge of distributing customer payments across multiple parties (Chef, CoCo, Driver, Platform) in the RidenDine marketplace, ensuring accurate payouts and commission splits.

Core Features & Use Cases

  • Multi-Party Payment Splits: Implements logic to divide customer payments among Chef, CoCo, Driver, and the Platform.
  • Onboarding New Recipients: Provides a framework for integrating new payment recipients like CoCos, Drivers, and Delivery Companies.
  • Commission Calculation: Enables accurate calculation and distribution of platform fees and partner commissions.
  • Payout Debugging: Assists in diagnosing and resolving issues related to missing or incorrect payouts.
  • Use Case: When a customer places an order, this Skill ensures the Chef receives their food cost, the CoCo partner gets their agreed-upon share, the Driver receives their delivery fee, and the Platform retains its commission.

Quick Start

Use the ridendine-payment-distribution skill to implement the multi-party split architecture for a new order.

Frequently Asked Questions about ridendine-payment-distribution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split marketplace payments between multiple parties using Stripe Connect?

Marketplace payment splits distribute customer funds across multiple parties like chefs, drivers, and the platform. This Skill calculates commission splits and uses Stripe's Transfers API to route the correct payout amounts to each recipient automatically.

How do I onboard new payment recipients for marketplace payouts in Supabase?

Onboarding new payment recipients involves integrating new chefs, drivers, or partners into your marketplace. This Skill provides a framework using Supabase Edge Functions to register recipients and prepare them for receiving automated transfers via Stripe Connect.

Why are Stripe Connect payouts missing or calculated incorrectly for my marketplace sellers?

Incorrect marketplace payouts often stem from flawed multi-party split logic or failed transfer API calls. This Skill assists in diagnosing and debugging payout issues by tracing the commission calculation and distribution flow between chefs, CoCos, drivers, and the platform.

Can I use Stripe Transfers API with Supabase Edge Functions for commission distribution?

Yes, Stripe Transfers API integrates directly with Supabase Edge Functions to execute payment distribution. This combination allows you to securely calculate platform fees and partner commissions, then trigger the actual fund transfers to connected marketplace accounts.

What is the best way to calculate platform fees and partner commissions for a marketplace?

Calculating marketplace commissions requires dividing the customer payment accurately among all parties. This Skill implements the multi-party split architecture, ensuring the chef receives food costs, the driver gets delivery fees, and the platform retains its specific commission.

Does this marketplace payment distribution approach handle complex multi-party splits?

Yes, complex multi-party splits are handled by dividing customer payments across chefs, CoCos, drivers, and the platform simultaneously. The Skill manages the entire distribution model, ensuring every recipient gets their agreed-upon share accurately.