hustlexp-revenue-fixer

Fix Stripe platform fees and escrow calculations in HustleXP revenue services.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill hustlexp-revenue-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hustlexp-revenue-fixer
Source: https://github.com/Sebdysart/omni-link-hustlexp/tree/main/skills/hustlexp-revenue-fixer
Command: npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill hustlexp-revenue-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses critical bugs in HustleXP's revenue collection system, ensuring accurate platform fee collection, correct escrow calculations, and proper logging of all financial transactions.

Core Features & Use Cases

  • Platform Fee Correction: Fixes issues where Stripe platform fees (application_fee_amount) are not collected.
  • Escrow Calculation Accuracy: Ensures fees are calculated on the correct amounts, including surge premiums.
  • Revenue Logging: Corrects missed revenue logs for subscription renewals and other financial events.
  • Financial Invariant Checks: Enforces critical financial rules to maintain system integrity.

Quick Start

Use the hustlexp-revenue-fixer skill to fix the application_fee_amount not being collected on PaymentIntent creation.

Frequently Asked Questions about hustlexp-revenue-fixer

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

FAQPage Schema
How do I fix missing Stripe platform fees on PaymentIntent creation?

To fix missing Stripe platform fees, you must ensure the `application_fee_amount` is correctly collected during PaymentIntent creation. This involves modifying backend service files like StripeService.ts to enforce accurate platform fee collection and maintain financial invariants.

Why are my escrow fee calculations incorrect for surge premiums?

Escrow fee calculations are incorrect when fees are not applied to the correct transaction amounts, such as surge premiums. Correcting this requires updating EscrowService.ts to accurately calculate fees on the full amount and ensure financial invariants are met.

How do I log unlogged subscription renewals in a revenue collection system?

Logging unlogged subscription renewals requires correcting the backend revenue logging logic to capture all financial events. This ensures that subscription renewals and other transactions are properly recorded to maintain system integrity and accurate revenue tracking.

What are financial invariant checks in a Stripe and escrow revenue system?

Financial invariant checks are rules that enforce critical financial integrity, ensuring accurate platform fee collection, correct escrow calculations, and proper logging. They are enforced by modifying backend services like StripeService.ts and EscrowService.ts to prevent revenue loss.

Does this revenue fixer handle unfunded self-insurance pools and XP tax paths?

Yes, this revenue fixer handles unfunded self-insurance pools and unreachable XP tax paths. It corrects these issues by modifying backend service files to ensure all financial invariants are met and platform revenue is accurately collected.

Can I use this to fix missing tip platform cuts in my finance application?

Yes, you can use this to fix absent tip platform cuts. It addresses this issue alongside missing Stripe platform fees and escrow calculation errors by updating backend service files to ensure all platform cuts are accurately calculated and collected.