Financial Plugins
Financial plugins are treated as sensitive integrations. They are reviewed as company relationships, not self-serve marketplace submissions.
Applications are currently closed. The financial/payment plugin category cannot be self-registered in the Developer Portal at this time. Payment integrations are by invitation and signed contract only, provisioned directly by Happa rather than through the self-serve marketplace flow.
What counts as a financial plugin
- Payment collection, checkout, payout, settlement, or refunds.
- Wallet, stored value, lending, escrow, or remittance workflows.
- Any plugin that handles regulated financial data, KYC, or merchant onboarding.
Approval standard
Financial plugins are only ever established as a direct relationship with a real company that Happa can verify, contract with, and review operationally. There is no individual or hobbyist path into this category, and none is planned.
| Requirement | What Happa expects |
|---|---|
| Legal entity | Registered company name that matches your contracts and compliance records. |
| Business contact | A monitored business email address, not a personal inbox. |
| Country of operation | Primary jurisdiction for the service and the merchants you plan to support. |
| Use case | A clear explanation of what money movement or financial workflow the plugin performs. |
| Operational review | Evidence that your support, incident, and dispute processes are defined. |
How to start a conversation
- Do not attempt to register a financial/payment plugin in the Developer Portal; that category is closed and the submission will be rejected.
- Email support@koola.app directly with your company details and the exact payment or financial use case.
- Happa reviews the relationship, not a marketplace submission: legal entity, licensing, and operational readiness are assessed before any technical integration begins.
- If accepted, Happa moves the integration into a contract and a controlled, first-party launch process.
- Only integrations provisioned this way can ever be enabled for production use.
Current platform rule: the Happa marketplace remains open for general hosted plugins (events, attendees, tickets, profile, polls). Financial and payment plugins are not part of the self-serve marketplace at all; they are established directly with Happa under tighter operational control.
Scope and data expectations
- Request only the minimum scopes needed for your workflow.
tickets.readexposes aggregate ticket counts and revenue totals only. It does not include buyer PII or wallet credentials.- Webhook payloads and installation tokens must be stored and transmitted securely on your infrastructure.
- You must maintain your own audit trail for payment decisions, disputes, and merchant actions.
What approval does not mean
- It does not grant unrestricted marketplace access without continued oversight.
- It does not shift regulatory, fraud, or settlement liability away from the provider.
- It does not allow plugins to bypass Happa admin controls for sensitive rollout decisions.
Interested in a payment partnership? Email support@koola.app directly with your company details and financial use case. There is no portal registration step for this category.