The Settings / Payouts links and the Home payouts widget in the Partner Dashboard have moved to the Dev Dashboard. Existing Partners keep their settings as-is, so no action is required.
Settings and payout information were accessed through the Settings and Payouts links and the Home payouts widget.
Select an organization → everything is consolidated in Organization settings. Business information, payouts, billing, and even Partner API clients are managed here.
| Item | Before | After |
|---|---|---|
| Entry point for settings and payouts | Partner Dashboard Settings / Payouts links | Dev Dashboard Organization settings |
| Home payout widget | Was on the Partner Dashboard Home | Moved to the Dev Dashboard |
| Partner API clients | Not specified | Organization settings > Users > Security |
| Business verification for new Partners | Not specified | Completed in Organization settings during setup |
| Existing payout and billing settings | — | Migrated automatically Unchanged; no action needed |
Payout and billing settings have already been migrated and remain as they are. Only where you access them has changed.
Complete business verification in Organization settings. Required documents and review times aren't specified.
Go to the Dev Dashboard, not the Partner Dashboard.
Choose the Partner organization you want to manage.
Details, Payouts, Billing, and Security are all here.
Partner API client management has also moved under Organization settings. Update the screen paths in any runbooks for creating or checking clients.
Your Partner ID is shown in Organization details. Note the new location when you need the ID for support requests or integration setup.
Existing payout and billing settings have already been migrated and remain unchanged. No re-registration or re-authentication is said to be required.
This update only covers where things are in the admin UI. No changes to Partner API endpoints or permissions are described.
This announcement covers settings, payouts, billing, and API clients.For other Partner Dashboard features, refer to the official migration guideand update the screenshots and screen paths in your internal docs all at once to be safe.