记录一次Figma订阅被多扣费的教训

最近在创业做项目,做软件设计的时候会用到国外知名设计软件Figma,但是因为初次使用踩了下订阅费用的坑,记录一下防止以后再踩坑

昨天(2025-12-3)银行信用卡收到一条92美元扣费提示震惊了我

我记得之前一个月Pro会员是20美元呀,貌似查看最新的还降价了,Pro变成一个月16美元了,被刺的感觉,恨呀!

于是我在邮箱就查看了下邮件

通过邮件获取到了发票

看完发票后才逐渐知道事情的端倪

Figma设计软件订阅费逻辑如下

    1. Pro-rated Professional Full seats (Nov 9 -- Dec 3, 2025)
      1. 11 月 9 日 开始使用了 2 个专业完整席位。
      1. 因为不是整月使用(仅使用了约 24 天),所以按比例计费。
      1. 单价 16.00/月→按比例折算后,2个席位共32.00。
    1. Professional Full seats (Dec 3, 2025 -- Jan 3, 2026)
      1. 从 12 月 3 日起,3 个专业完整席位的订阅。
      1. 每月单价 20.00,因此3个席位×20 = $60.00。
      1. 未来一个周期(12 月 3 日到次年 1 月 3 日)的预付费。

合计:$92.00

其实项目主要是我在设计,一个小伙伴通过设计生成代码,还是有个小伙伴只是看一看设计效果。

可是我是Figma新手没有注意到一些细节,后续邀请进入的小伙伴全是Full角色,所以就导致203=60美元的预付,上个月不是完整的月份按照比率折算的两个席位162=32美元。

我邀请的时候完全没有提醒相关扣费事宜,扣费的时候直接算总账,这个点不得不说还是平台鸡贼呀。

按照合理的设置方法应该是我的角色是Full(全功能),一个小伙伴是Dev(开发),另一个小伙伴是View(仅查看),按照最新资费标准这样一个月就是16+12=28美元,折合成197.79人民币

为了防止再被坑我还是先取消订阅吧,听说淘宝上有更便宜Figma套餐的,后面有时间研究一下

点击continue

填写取消原因

复制代码
  I recently signed up for a Figma Team plan as a new user and unintentionally assigned "Full" seats to all three team members due to unfamiliarity with how Figma's billing and seat types work. In reality, we only need one "Full" seat, one "Dev" seat, and the third member doesn't require access at all.

I've since corrected the team setup by removing one member and downgrading another to a "Dev" seat, but the platform had already charged me in advance for the full upcoming billing cycle (December 3 -- January 3) based on the initial incorrect configuration.

When I requested a refund for the overcharged amount, I was informed that Figma does not offer refunds under any circumstances. Since I've already paid for services I didn't intend to use---and won't be able to recover those costs---I've decided to cancel my subscription entirely to avoid further unexpected charges.

This experience has been frustrating, especially as a new user trying to set things up correctly. I hope Figma will consider more flexibility in such cases in the future.

取消成功

我还抱有一丝官方良心发现退我多余的钱的想法,我在官网尝试了向客服反馈问题,貌似是AI自动回复

复制代码
  Hello,

I would like to request a refund. Yesterday, the platform charged me in advance for the upcoming billing cycle (from December 3 to January 3 of next year). As a new Figma user, I wasn't fully aware of how the platform works, which led to all three members of my Figma Team being assigned the "Full" seat type. However, we actually only need one "Full" seat, one "Dev" seat, and the third member doesn't require a seat at all and can be removed from the team entirely.

I've already removed one member from the team and changed another member's role to "Dev," so now only I remain on the "Full" seat. Could you please refund the overcharged amount?

Thank you very much!

我又尝试通过邮件向平台沟通,希望后续能有个好的解决把

相关推荐
猿究院_夏燊1 小时前
Spring Bean 生命周期
java·后端·spring
Wang's Blog2 小时前
Java 项目实战: 交友项目:登录链路回顾与今日任务地图
java·开发语言·状态模式·交友
Chenyu_3102 小时前
DPDK、TC 和 XDP:Linux 高性能网络到底在优化什么
linux·服务器·网络·缓存
信誓旦旦的程序猿2 小时前
【Python量化实战宝典 #08】可转债与债券接口手册:转股价·溢价率·纯债价值(Python 可跑)
java·python·股票数据api·股票数据api接口·股票api数据接口·股票量化数据api·股票量化数据接口
Lethehong2 小时前
Oracle 加个字段,目标库就报错?KFS 用“先拆后组“打通异构 DDL
数据库·oracle
砚底藏山河2 小时前
python量化:行情数据回溯
java·开发语言·python·金融·maven
Jlzn88882 小时前
华东电芯分选通道数怎么配才不堵线
java·人工智能·架构·自动化·制造
Web极客码3 小时前
锁定真正的磁盘卡顿:我用 OpenCode 配合 eBPF 诊断 NVMe 队列深度延迟与 I/O 写放大
数据库·oracle
香吧香3 小时前
GRPC连接机制---长连接分析
java·网络与传输协议
我是人✓3 小时前
SpringBoot项目的五种创建方式
java·spring boot·后端