Skip to main content

Requirements checklist

Before you submit, check that the app has all of these:
  • Summary and Description.
  • Logo, as a PNG or JPG file up to 5 MB.
  • Support email.
  • Privacy policy URL and Terms of service URL, both with https.
  • A reason for each requested scope.
  • Redirect URIs that use https. A public app cannot use a loopback address or a private IP address.
  • A webhook endpoint that returns 2xx for a test event.
  • Screenshots (recommended).
  • Handling of customer.data_request, customer.redact, and business.redact, if the app has customers scopes.
  • Working test credentials for the reviewer.
  • A name that does not start with “Dodo”.
If a field is missing, the submit fails and tells you which field a review needs.

Prove your domain

When you prove the domain of your website, the app shows the Verified badge. Without proof, the consent screen says that Dodo Payments did not verify the app and that the app sets its own name.
The domain proof routes are available in the API of the dashboard. Only the owner of the business can use them, and the owner must have two-factor authentication.
1

Set the website URL

Set the Website URL of the app. The domain must be the domain of that website, or a parent of its host.
2

Get the TXT record

Request the proof for your domain. The response has the name and the value of the record.
3

Add the record

Add a TXT record with this name and value to the DNS of the domain.
4

Verify

Ask Dodo Payments to verify the domain. If the record is correct, the app has a verified domain. If it is not correct, the request returns 422. Wait for the DNS change and try again.
If you later change the website to a different host, Dodo Payments clears the verified domain. Prove it again.

Submit

1

Open Make public

Open your app on the Created tab and select Make public.
2

Add the listing details

The wizard asks for the app basics, the listing details, and a reason for each permission.
3

Review and submit

Check the summary and select Submit for review. The toast says that the app is submitted.
Only an owner or an admin can submit.

Review states

A reviewer checks the test credentials, the redirect URIs, the scopes and their reasons, the privacy policy and support URLs, the name and the icon, and that your webhook endpoint returns 2xx for a test event. Scopes for refunds, payouts, balances, and customers are marked for extra attention.

Change a live app

When you edit a live app, these changes go to review:
  • The listing (name, logo, summary, description, website, terms, privacy policy, support email)
  • The permissions and the reasons
  • The redirect URIs
  • The webhooks and the subscribed events
  • Some settings manifest changes. See App Settings.
The live version stays active, with its approved scopes, redirect URIs, and events, until the review approves the change. The page shows Changes in review and the list of the changed parts. If the reviewer rejects the change, the live version does not change. Your next edit starts from the live version and goes to review again.

Scope increases

If you add a scope, existing installs keep their old scopes. Each merchant sees a banner and must approve the new scopes. Calls that need the new scope fail until the merchant approves.

Rejection and resubmission

If the reviewer rejects the app, the page shows The review rejected this app and the reason. Fix the issues, then select Submit again. You get an email about the decision.

Suspension

A reviewer can suspend an app. A suspended app is hidden from the marketplace, its tokens stop working, and its webhooks stop. Contact support to learn more. When the suspension ends, the app returns to its earlier status.

Delete an app

Deleting an app removes it from every business that installed it. Each install gets app.uninstalled. This cannot be undone.

Next steps

Maintain your app

Handle uninstalls and privacy requests.

API reference

The endpoints that an app calls.
Last modified on November 16, 2026