展示HN：统一支付沙盒 – Stripe/Razorpay集成的用户验收测试环境
嘿，HN！<p>我正在探索一个面向开发者的SaaS想法：
一个统一的支付网关用户验收测试（UAT）环境——本质上是一个沙盒模拟器，让开发者可以在不创建多个沙盒账户或处理网关间不一致/虚假行为的情况下集成支付。<p>问题<p>如果你曾经集成过支付，你会知道：<p>Stripe有出色的测试工具<p>Razorpay表现尚可<p>Paytm/PayU等差异很大<p>许多银行的UAT行为不可预测<p>Webhook的到达方式各异，有些延迟，有些不稳定<p>测试争议/退款/结算几乎是不可能的<p>对于构建复杂流程的开发团队来说，他们最终不得不编写内部模拟，维护这些模拟，仍然会遗漏边缘案例。<p>想法（SaaS）<p>一个统一的支付沙盒模拟器，能够：<p>为多个网关提供模拟API<p>Stripe<p>Razorpay<p>Paytm<p>PayU<p>Cashfree<p>Worldline<p>Visa/Mastercard令牌化模拟<p>UPI支付服务提供商模拟器<p>模拟现实场景<p>捕获<p>退款<p>部分退款<p>拒付<p>争议<p>结算延迟<p>失败的支付<p>KYC验证<p>随机化的Webhook延迟/跳过<p>网络故障模拟<p>3-D安全/一次性密码模拟页面<p>UPI超时/待处理状态<p>托管仪表板<p>查看模拟交易<p>触发生命周期事件（手动或定时）<p>再次触发Webhook<p>创建自定义网关配置<p>定义“规则”以模拟：失败率%、延迟、Webhook顺序、重试<p>对于工程团队<p>一个URL中的私有UAT环境<p>不再需要创建10个沙盒账户<p>CI友好的“无头支付”流程<p>在本地添加模拟支付网关→在预发布环境中切换到真实支付网关<p>自动合同测试<p>定价思路<p>免费层→每月100笔测试交易
每月29美元→小团队
每月99美元→初创公司
每月499美元→企业/白标<p>向HN提问<p>你会使用这个吗？
还有什么缺失的？
支付团队会信任第三方模拟器吗？
哪些网关或场景最重要？<p>乐意回答问题。
查看原文
Hey HN!<p>I'm exploring an idea for a developer-focused SaaS:
A unified UAT environment for payment gateways — essentially a sandbox simulator that lets developers integrate payments without creating multiple sandbox accounts or dealing with inconsistent/mock behaviors across gateways.<p>The Problem<p>If you’ve ever integrated payments, you know:<p>Stripe has excellent test tooling<p>Razorpay is decent<p>Paytm/PayU/etc vary a lot<p>Many banks don’t have predictable UAT behavior<p>Webhooks arrive differently, some delayed, some flaky<p>Testing disputes/refunds/settlements is nearly impossible<p>For dev teams building complex flows, they end up writing internal mocks, maintaining them, and still missing edge cases.<p>The Idea (SaaS)<p>A unified Payment Sandbox Simulator that:<p>Mock APIs for multiple gateways<p>Stripe<p>Razorpay<p>Paytm<p>PayU<p>Cashfree<p>Worldline<p>Visa/Mastercard tokenization mock<p>UPI PSP simulators<p>Simulate real-world scenarios<p>Captures<p>Refunds<p>Partial refunds<p>Chargebacks<p>Disputes<p>Settlement delays<p>Failed payouts<p>KYC verification<p>Randomized webhook delays/skips<p>Network downtime simulation<p>3-D Secure / OTP mock pages<p>UPI timeouts / pending states<p>Hosted dashboards<p>View mock transactions<p>Trigger lifecycle events (manually or timed)<p>Trigger webhooks again<p>Create custom gateway profiles<p>Define “rules” to simulate: failure %, latency, webhook disorder, retries<p>For engineering teams<p>Private UAT environment in one URL<p>No more creating 10 sandbox accounts<p>CI-friendly “headless payment” flows<p>Add Mock PG in local → swap to real PG in staging<p>Automatic contract testing<p>Pricing thought<p>Free Tier → 100 test transactions/mo
$29/mo → small teams
$99/mo → startups
$499/mo → enterprise / white-label<p>Ask to HN<p>Would you use this?
What’s missing?
Would payments teams trust a 3rd-party simulator?
Which gateways or scenarios matter most?<p>Happy to answer questions