Case study
Finqu Partner Portal
A self-service console for partners and developers, covering onboarding, app and theme lifecycle, OAuth clients, and seller payouts.
overview
A self-service console for partners and developers
The Partner Portal is the self-service console for third-party and internal developers. A partner applies, reaches an approved status, sets up their brand and contacts, and then works with apps, themes, and the API clients that connect them to the platform.
It is the supply side of the marketplace. Listings and prices sync outward and entitlement webhooks come back, while the purchase record stays in Marketplace.
workflow
App and theme lifecycle
- 01Apply
Partnership application and approved developer status.
- 02Build
Create an app or theme and issue the OAuth clients it needs.
- 03Version
Cut a version and submit it for review.
- 04Publish
Price it and publish, with share tokens for unlisted work.
- 05Get paid
Stripe Connect onboarding for payouts to the seller.
engineering
What the portal handles
- Partner onboarding, status workflow, brand profile, and contacts
- App and theme creation, versioning, review submission, and publishing
- Per-theme signing key pairs and structure validation on publish
- Partner-issued OAuth clients and merchant client relationships
- Stripe Connect onboarding and payout status for independent sellers
- Merchant ownership transfer through time-limited verification tokens
Next step
Interested in this kind of work?
I'd be happy to talk through the decisions behind this case or the kind of problem your team is working on.