Set up future payments with Naver Pay

Learn how to save Naver Pay to charge your customers later.

Checkout

Direct API

Save Naver Pay payment details using Checkout, our fully hosted checkout page.

Learn how to set up a subscription with Naver Pay to create recurring payments after saving a payment method in Checkout.

Set up Stripe Server-side

First, you need a Stripe account. Register now.

Use our official libraries for access to the Stripe API from your application:

Command Line

Select a language

Ruby

Python

PHP

Java

Node.js

.NET

No results

# Available as a gem
sudo gem install stripe

Gemfile

Select a language

Ruby

Python

PHP

Java

Node.js

.NET

No results

# If you use bundler, you can add this line to your Gemfile
gem 'stripe'

Get permission to save Naver Pay as a payment method Server-side

You need permission to save your customer’s payment method for future use. Creating an agreement (sometimes called a mandate) up front allows you to save your customer’s payment details and charge them when they’re not actively using your website or app.

Add terms to your website or app that state how you plan to save your customer’s payment method details, and let them opt in. If you plan to charge your customer when they’re offline, make sure that your terms also include the following:

The customer’s permission for you to initiate a payment or a series of payments on their behalf for specified transactions
The anticipated frequency (one-time or recurring) and timing of payments
How you determine the payment amount
Your cancellation policy (if you’re setting up the payment method for a subscription service)

Make sure that you keep a record of your customer’s written agreement to these terms, and only submit charges in accordance with the agreed terms.

Create or retrieve a customer Server-side

To reuse a Naver Pay payment method for future payments, attach it to an object that represents your customer.

Use the Accounts v2 API to represent customers

The Accounts v2 API is generally available for Connect users, and in public preview for other Stripe users. If you’re part of the Accounts v2 preview, you need to specify a preview version in your code.

To join the Accounts v2 preview, go to Account previews and features in your Dashboard and enable Reusable payment methods for Global Payouts.

For most use cases, we recommend modeling your customers as customer-configured Account objects instead of using Customer objects.

Create a customer-configured Account or Customer when your customer creates an account with your business, or when saving a payment method. Associate the object’s ID with your own internal representation of a customer.

Create a new customer or retrieve an existing one to associate with this payment.

Command Line

Select a language

cURL

Stripe CLI

Ruby

Python

PHP

Java

Node.js

.NET

No results

Create a Checkout Session Server-side

Your customer must authorize you to use their the related setting account for future payments through Stripe Checkout. This allows you to accept future Naver Pay payments. Add a checkout button to your website that calls a server-side endpoint to create a Checkout Session.

index.html

<html>
 <head>
 <title>Set up payment</title>
 </head>
 <body>
 <form action="/create-checkout-session" method="POST">
 <button type="submit">Set up payment</button>
 </form>
 </body>
</html>

Create a Checkout Session in setup mode to collect the required information. After creating the Checkout Session, redirect your customer to the URL in the response.

Command Line

Select a language

cURL

Stripe CLI

Ruby

Python

PHP

Java

Node.js

.NET

No results

Test your integration

While testing your Checkout integration, select Naver Pay and click Continue to Naver Pay. You’ll be redirected to a Stripe-hosted page where you can choose to authorize or fail the payment setup. Learn more about testing redirect-based payment methods.