Skip to main content
Solved

Refund request

  • April 8, 2026
  • 1 reply
  • 32 views
Vadym_Salii

I submitted a refund request, but no one has responded to it for 2 days. What should I do?
ID: 1832207

Best answer by Celine_

Hey ​@Vadym_Salii , Celine from Figma here, thanks for following up. I understand you’re waiting on an update regarding your refund request here.

I was able to see your case (#1832207) and have added a follow-up note to give it more visibility with the team. Someone should be getting back to you soon, thanks for your patience in the meantime! 🙏🏼

Update: Glad to see that your request has been resolved on our end! Just to give some context for anyone who might run into the same situation: this happened because the users were given edit access, which automatically provisions a full seat (and that’s what triggered the additional charges.)

Sharing also here in case others in the community has similar experience:

If you'd like to prevent additional charges in the future, we recommend using seat approval settings to automatically manage new seat requests. This setting will require Admin approval for a user to be upgraded to a paid seat. Our Help Center article provides step-by-step instructions on how to change the setting.

I’ve gone ahead and marked as solved here, thank you!

    This topic has been closed for replies.

    1 reply

    Celine_
    Figmate
    • Celine_
    • Community Support
    • Answer
    • April 8, 2026

    Hey ​@Vadym_Salii , Celine from Figma here, thanks for following up. I understand you’re waiting on an update regarding your refund request here.

    I was able to see your case (#1832207) and have added a follow-up note to give it more visibility with the team. Someone should be getting back to you soon, thanks for your patience in the meantime! 🙏🏼

    Update: Glad to see that your request has been resolved on our end! Just to give some context for anyone who might run into the same situation: this happened because the users were given edit access, which automatically provisions a full seat (and that’s what triggered the additional charges.)

    Sharing also here in case others in the community has similar experience:

    If you'd like to prevent additional charges in the future, we recommend using seat approval settings to automatically manage new seat requests. This setting will require Admin approval for a user to be upgraded to a paid seat. Our Help Center article provides step-by-step instructions on how to change the setting.

    I’ve gone ahead and marked as solved here, thank you!

      Terms & ConditionsCookie settingsAccessibility statement