Vendor onboarding

Connect a Git provider

Visit Git integrations. Pick GitHub or GitLab and walk through the connect flow on the provider. For GitHub you install the Packagento app on the account or organisation that owns the repositories you want to publish; for GitLab you authorise Packagento as an OAuth application with read access to your projects. Your credentials are stored encrypted.

Connecting a Git provider lets Packagento read the repositories the connection grants it access to, including private ones, and avoids the rate limits that anonymous access would hit during busy periods.

Connect Stripe

From your vendor dashboard, click "Connect Stripe". Stripe Connect Express collects your business identity, payout bank details, and the tax information Stripe needs for your country. Onboarding usually takes 5 to 15 minutes; some markets ask for additional verification documents before payouts can begin.

You can save paid and subscription packages before Stripe is connected, and they appear in the marketplace once your application is approved. However, buyers cannot complete a paid checkout against a vendor whose Stripe onboarding is not finished, so payment for those packages is held back until Stripe is fully connected. Free packages can be purchased as soon as your application is approved.

Add your first package

Go to My packages and click "Add". A wizard opens with the repositories visible to your Git connection. Tick the ones you want to publish (or paste a name and URL manually for a repo that is not listed), then for each row set:

• Composer name, vendor/package, normally read directly from the repo's composer.json.
• Source URL, the repository the package is built from (filled in for you when picked from the list).
• Pricing, free, one-time, or subscription (see Pricing). For paid and subscription packages you set a price per Magento edition (Open Source, Adobe Commerce, Adobe Commerce on Cloud); subscriptions also have an optional renewal price.

The package goes through a one-time review by Packagento before it is visible to buyers; see Quality and review for what we look at.

Push a tag, watch it ingest

Tag a release in your repo (git tag v1.0.0 && git push --tags). Packagento picks it up, fetches your composer.json, README, and CHANGELOG, runs the automated checks, packages an installable archive, and makes the release available to buyers.

Watch progress in the activity feed on your vendor dashboard. If a release fails the checks, you receive an email with the reason and can ship a fix by pushing a new tag.