调至内容部分
创建账户或登录
Stripe 文档徽标
/
询问人工智能
创建账户登录
开始
付款
销售收入
平台和交易市场
资金管理
开发人员资源
API 和 SDK帮助
概览
版本管理
更改日志
    概览
    Clover
    Basil
    Acacia
    先前版本
升级您的 API 版本
升级 SDK 版本
基础功能
SDK
API
测试
Stripe CLI
项目示例
工具
Stripe 管理平台
Workbench
开发人员管理平台
Stripe Shell
Stripe for Visual Studio Code
功能
工作流程
事件接收端
Stripe 健康警报文件上传
AI 解决方案
代理工具包
模型上下文协议构建代理式 AI SaaS 计费工作流
安全与隐私
安全
Stripebot 网络爬虫
隐私
扩展 Stripe
构建 Stripe 应用程序
使用 Stripe 的应用程序
合作伙伴
合作伙伴生态
合作伙伴认证
美国
简体中文
首页开发人员资源ChangelogBasil2025-05-28.basil

Extracts sex and place of birth from government-issued ID documents

What’s new

Adds the sex, unparsed_sex and unparsed_place_of_birth fields to the Verification Report in the document section. If a document doesn’t contain this information, the corresponding value is null. For example, while passports usually include both sex and place of birth, a driver’s license might include sex but have a null value for unparsed_place_of_birth.

We recommend using sex because it’s parsed into an enum; however, you can use unparsed_sex if you need the raw value.

These fields are also available in the Verification Session for the last verification report and in the verified outputs.

Because these fields contain sensitive information, in order to retrieve them you need to use a restricted API key and explicitly expand them. For example, to retrieve the sex and unparsed_place_of_birth fields, follow the steps to retrieve sensitive verification results. The response might look like this:

{ "id": "vs_", "object": "identity.verification_session", ... "verified_outputs": { "first_name": "Jenny", "last_name": "Rosen", ... "sex": "female", "unparsed_place_of_birth": "U.S.A." } }

Impact

Platforms that need sex or place of birth information to fulfill additional KYC requirements, such as reporting them to an external agency, can now retrieve them using the Identity API.

Changes

参数更改资源或 端点
sexunparsed_place_of_birthunparsed_sex已添加
Identity.VerificationReport.documentIdentity.VerificationSession.verified_outputs

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
    • If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-05-28.basil
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

此页面的内容有帮助吗?
是否
  • 需要帮助?联系支持。
  • 查看我们的更改日志。
  • 有问题?联系销售。
  • LLM? Read llms.txt.
  • Powered by Markdoc