{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaf45ozz3bwgjg6j2y3cscyryz5a7d6wxhieshtd5m2vsva2ljcwu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mltf2tlcdsx2"
  },
  "path": "/t/understanding-the-rejecting-conditions-on-a-chatgpt-app-clarification-needed-on-rejection-feedback/1380927#post_2",
  "publishedAt": "2026-05-14T17:49:48.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@ManuelDario"
  ],
  "textContent": "Hey @ManuelDario, that sounds really confusing, especially getting the same rejection twice.\n\nOn the two questions:\n\n1. Developer name\n\nIf you’re registering under a business, it needs to match the verified organization name exactly from your Organization verification. Even small differences like abbreviations or branding vs legal name can trigger that rejection.\n\n2. Tool annotations (for your checkout link case)\n\nBased on what you described, these should line up:\n\n  * readOnlyHint: true\n  * It’s only generating/retrieving a checkout link, no data is created or changed.\n  * destructiveHint: false\n  * No deletion or irreversible actions happening.\n  * openWorldHint: true\n  * It calls an external payment provider, so it’s outside the core environment.\n\n\n\nMake sure to include clear justification for why the hint is set that way based on the tool's actual behavior.\n\nOne more thing on the blocked email\n\nThat part trips people up a lot. You’ll need to reply directly to the original review email thread, not by emailing openai-review@openai.com directly, since that inbox doesn’t accept new messages.\n\nIf you’re still stuck after updating those, share what you changed and we can sanity check it together.\n\n-Mark G.",
  "title": "Understanding the rejecting conditions on a ChatGPT App - Clarification needed on rejection feedback"
}