<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: jione0913</title>
    <description>The latest articles on DEV Community by jione0913 (@jione0913).</description>
    <link>https://dev.to/jione0913</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4254660%2F54c38d31-a060-4d33-8a2d-b4c5dc68fc54.png</url>
      <title>DEV Community: jione0913</title>
      <link>https://dev.to/jione0913</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jione0913"/>
    <language>en</language>
    <item>
      <title>Stripe-based Next.js starter kits don't work in Korea, so I rebuilt the payment layer for Toss</title>
      <dc:creator>jione0913</dc:creator>
      <pubDate>Fri, 20 Nov 2026 01:17:32 +0000</pubDate>
      <link>https://dev.to/jione0913/stripe-based-nextjs-starter-kits-dont-work-in-korea-so-i-rebuilt-the-payment-layer-for-toss-5bba</link>
      <guid>https://dev.to/jione0913/stripe-based-nextjs-starter-kits-dont-work-in-korea-so-i-rebuilt-the-payment-layer-for-toss-5bba</guid>
      <description>&lt;p&gt;I run a small web design studio, and every time a client project needed payments, I hit the same wall: ShipFast, Makerkit, and basically every popular Next.js starter kit out there is built around Stripe. That's fine until you're shipping for a Korean client, where Stripe isn't the default and Toss Payments is what everyone actually integrates with. So the "save weeks with a starter kit" pitch falls apart, and you're back to wiring up payment confirmation from scratch every single time.&lt;/p&gt;

&lt;p&gt;The part that actually takes the time isn't the checkout UI — Toss's widget handles that. It's the server-side confirmation step, and specifically not trusting the client:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When the payment confirmation request comes in, the server re-looks-up the real price of that plan from the database and rejects the request if it doesn't match what the client sent. Opening devtools and editing the amount in the request body doesn't get you a discount.&lt;/li&gt;
&lt;li&gt;Idempotency-Key on the confirm call, so retried/duplicated webhook or client calls can't approve the same payment twice.&lt;/li&gt;
&lt;li&gt;Firestore security rules that only let a server-side function write purchase records at all — not "logged in user," since once you add customer signup, "logged in" stops meaning "admin."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I ended up pulling this out of a client project into a standalone Next.js 16 boilerplate (Firebase Auth + Toss Payments + an admin dashboard) so I'm not rebuilding it for the next one. It's not polished into a SaaS product with a subscription model — it's one-time-payment source code, the same category as ShipFast/Makerkit but for Toss instead of Stripe.&lt;/p&gt;

&lt;p&gt;No sales yet, this is fresh. If you've built something similar for a different regional payment provider (Paystack, Razorpay, whatever your market uses), I'd be curious what you had to rebuild versus what transferred over from the Stripe-first patterns.&lt;/p&gt;

&lt;p&gt;Demo: &lt;a href="https://kr-saas-kit.vercel.app" rel="noopener noreferrer"&gt;https://kr-saas-kit.vercel.app&lt;/a&gt;&lt;br&gt;
Source: &lt;a href="https://jione3.gumroad.com/l/wnmnux" rel="noopener noreferrer"&gt;https://jione3.gumroad.com/l/wnmnux&lt;/a&gt;&lt;/p&gt;

</description>
      <category>nextjs</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
