Save PayPal for purchase later with the JavaScript SDK

Save payment methods to charge payers after a set amount of time. For example, you can offer a free trial and charge payers after the trial expires. Payers don't need to be present when charged. No checkout required.

To save PayPal Wallets, payers need to log in to your site, make a purchase, and remain on your site when transactions take place.

Customers with a PayPal Wallet can:

Review PayPal transactions and transaction history
Review, add, or remove funding sources
Review and cancel recurring payments
Hold a balance in their PayPal account
Use PayPal to send and receive money
Withdraw money to a linked bank account
Use PayPal to transact with merchants

Use cases

Businesses save payment methods if they want customers to:

Check out without re-entering a payment method
Pay after use, for example, ride-sharing and food delivery

Know before you code

To save payment methods, you must be able to identify payers uniquely. For example, payers create an account and log in to your site.
Complete the steps in Get started to get the following sandbox account information from the Developer Dashboard:
- Your sandbox account login information
- Your access token

This integration requires a PayPal Developer account.
This integration must include a server-side call to exchange a setup token for a payment method token.

How it works

PayPal encrypts payment method information and stores it in a digital vault for that customer.

The payer saves their payment method.
For a first-time payer, PayPal creates a customer ID. Store this within your system for future use.
When the customer returns to your website and is ready to check out, pass their PayPal-generated customer ID to the JavaScript SDK. The customer ID tells the JavaScript SDK to save or reuse a saved payment method.
The payer completes a billing agreement.
The JavaScript SDK populates the checkout page with each saved payment method. Each payment method appears as a one-click button next to other ways to pay.

The checkout process is now shorter because it uses saved payment information.

1. Check eligibility

Go to paypal.com and sign in with your business account.
Go to Account Settings > Payment Preferences > Save PayPal and Venmo payment methods.
In the Save PayPal and Venmo payment methods section, select Get Started.
When you submit profile details, PayPal reviews your eligibility to save PayPal Wallets and Venmo accounts.
After PayPal reviews your eligibility, you'll see a status of Success, Need more information, or Denied.

2. Set up account to save payments

Set up your sandbox and live business accounts to save payment methods:

Log in to the Developer Dashboard.
Under REST API apps, select your app name.
Under Sandbox App Settings > App Feature Options, check Accept payments.
Expand Advanced options. Confirm that Vault is selected.

To go live, you'll need to be vetted to save PayPal Wallets. You can start the vetting process from the Developer Dashboard.

Only your sandbox business account is enabled to save payment methods. Your developer account remains unaffected.
You'll complete production onboarding when you're ready to go live.

Tip: When prompted for data such as a phone number for a sandbox business request, enter any number that fits the required format. Since this is a sandbox request, the data doesn't have to be real.

PayPal requires Risk Data Acquisition (RDA) to reduce fraud. You must implement risk data collection for all customer-initiated transactions (CIT) that use PayPal and Venmo Payment Tokens. Payment attempts that are missing RDA data are likely to be declined due to insufficient risk identifiers. Use the PayPal FraudNet and Magnes libraries to collect and pass RDA data during payment processing.

3. Generate user ID token for payer

The PayPal OAuth 2.0 API has a response_type parameter. Set the response_type to id_token to retrieve a unique ID token for a payer.

First-time payer

A payer wants to save a payment method for the first time. Modify the POST request to generate id_token for the payer.

Returning payer

A payer wants to use a saved payment method.

Use the saved PayPal-generated customer ID in the POST body parameter target_customer_id. The target_customer_id is a unique ID for a customer generated when the payment_source is saved to the vault. The target_customer_id is available when capturing the order or retrieving saved payment information.

Note: Use the customer identifier generated by PayPal, not the identifier that you use to identify the customer in your system.

Sample server-side user ID token request

curl -s -X POST https://api-m.sandbox.paypal.com/v1/oauth2/token \
 -u CLIENT-ID:CLIENT-SECRET \
 -H 'Content-Type: application/x-www-form-urlencoded' \
 -H 'PayPal-Partner-Attribution-Id: BN-CODE' \
 -H 'PayPal-Auth-Assertion: AUTH-ASSERTION-JWT' \
 -d 'grant_type=client_credentials' \
 -d 'response_type=id_token'

Modify the code

Copy the code sample and modify it as follows:

Change CLIENT-ID to your client ID.
Change CLIENT-SECRET to your client secret.
For a returning payer, change the CUSTOMER-ID to the PayPal-generated customer ID.
Change BN-CODE to your PayPal Attribution ID to receive revenue attribution. To find your BN code, see Code and Credential Reference.
Change AUTH-ASSERTION-JWT to your PayPal-Auth-Assertion token.

A successful request returns fields including an access_token, id_token, and the number of seconds the access_token token is valid.

The id_token:

Uniquely identifies each payer.
Expires in a few minutes because it's meant to be used during checkout. Generate new tokens if the current tokens expire.

Tip: Each buyer session is unique. Set up your server to generate a new client token each time payment fields render on your page.

4. Pass user ID token to JavaScript SDK

Pass the id_token into the JavaScript SDK through the data-user-id-token.

<script src="https://www.paypal.com/sdk/js?client-id=CLIENT-ID&merchant-id=MERCHANT-ID" data-user-id-token="ID-TOKEN"></script>

Modify the code

Copy the code sample and modify it as follows:

Change CLIENT-ID to your client ID.
Change MERCHANT-ID to your merchant ID.
Change ID-TOKEN to the id_token from the previous step.

5. Add PayPal button

Include client-side callbacks to:

Manage interactions with APIs
Manage payer approval flows
Handle any events that lead to cancellation or error during payer approval

<div id="DIV-ID"></div>
<script>
    window.paypal.Buttons({
        createVaultSetupToken: async () => {},
        onApprove: async ({ vaultSetupToken }) => {},
        onError: (error) => {}
    }).render("YOUR-DIV-ID");
</script>

Modify the code

Copy the code sample and modify it as follows:

Replace DIV-ID with a div id of your choice.
Replace YOUR-DIV-ID with the div id you created.

6. Create setup token

You request a setup token from your server. Pass the setup token from your server to the SDK with the createVaultSetupToken callback.

The createVaultSetupToken callback:

Calls the server endpoint you created to generate and retrieve the setup token.
Makes a request to your server endpoint.

Then, your server uses its access token to create and return the setup token to the client.

Any errors that occur while creating a setup token show up in the onError callback provided to the card fields component.

Supported callback

Callback, Returns, Description
Callback	Returns	Description
`createVaultSetupToken`	Setup token (string)	The merchant's server must receive this callback. Create a setup token for cards from the merchant server. The SDK then saves the payment method and updates the setup token with payment method details.

Client-side code sample

window.paypal.Buttons({
  createVaultSetupToken: async () => {
    // The merchant calls their server API to generate a setup token
    // and return it here as a string
    const result = await fetch("example.com/create/setup/token", {
      method: "POST"
    })
    return result.token
  }
})

Server-side code sample

Set up your server to call the Payment Method Tokens API. The button that the payer selects determines the payment_source sent in the following sample.

This SDK uses the Payment Method Tokens API to save payment methods in the background. Use the following request to add attributes needed to save a PayPal Wallet:

Note: The return_url and cancel_url values are required, but can have filler values such as in the following sample.

curl -v -k -X POST https://api-m.sandbox.paypal.com/v3/vault/setup-tokens \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -H 'PayPal-Partner-Attribution-Id: BN-CODE' \
  -H 'PayPal-Auth-Assertion: AUTH-ASSERTION-JWT' \
  -H 'PayPal-Request-Id: REQUEST-ID' \
  -d '{
          "payment_source": {
              "paypal": {
                  "usage_type": "PLATFORM",
                  "experience_context": {
                    "return_url": "https://example.com/returnUrl",
                    "cancel_url": "https://example.com/cancelUrl"
                  }
              }
          }
      }'

Modify the code

Change ACCESS-TOKEN to your sandbox app's access token.
Change BN-CODE to your PayPal Attribution ID to receive revenue attribution. To find your BN code, see Code and Credential Reference.
Change AUTH-ASSERTION-JWT to your PayPal-Auth-Assertion token.
Change REQUEST-ID to a set of unique alphanumeric characters such as a time stamp.
In the createVaultSetupToken, call the endpoint on your server to create a setup token with the Payment Method Tokens API. createVaultSetupToken returns the setup token as a string.

Response

Return the id to your client to call for the payer approval flow if the payment_source needs payer approval.

Note: The setup token is generated with an empty paypal object in the payment_source. The Buttons script uses this token to securely update the setup token with payment details.

Payer approval

If payer approval is required, the client SDK calls the payer approval flow. The approval flow takes the payer through PayPal Checkout.

7. Create payment token

You can store a Merchant Customer ID aligned with your system to simplify the mapping of customer information within your system and PayPal when creating a payment token. This is an optional field that will return the value shared in the response.

Use an approved setup token to save the payer's payment method to the vault. Then, copy the sample request code to generate a payment token:

Supported callback

Callback, Returns, Description
Callback	Returns	Description
`onApprove`	`{ vaultSetupToken: string }`	The merchant gets the updated `vaultSetupToken` when the payment method is saved. The merchant must store the `vaultSetupToken` token in their system.

Client-side sample request

Modify the following request to match your server endpoint and payload:

window.paypal.Buttons({
    onApprove: ({ vaultSetupToken }) => {
    // Send the vaultSetupToken to the merchant server
    // for the merchant server to generate a payment token
        return fetch("example.com/create/payment/token", { body: JSON.stringify({ vaultSetupToken }) })
    },
})

Sample API request and response

curl -v -k -X POST https://api-m.sandbox.paypal.com/v3/vault/payment-tokens \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -H 'PayPal-Partner-Attribution-Id: BN-CODE' \
  -H 'PayPal-Auth-Assertion: AUTH-ASSERTION-JWT' \
  -H 'PayPal-Request-Id: REQUEST-ID' \
  -d '{
         "payment_source": {
              "token": {
                  "id": "4G4976650J0948357",
                  "type": "SETUP_TOKEN"
              }
          }
      }'

Modify the code

Copy the code sample and modify it as follows:

Change ACCESS-TOKEN to your sandbox access token.
Change BN-CODE to your PayPal Attribution ID to receive revenue attribution. To find your BN code, see Code and Credential Reference.
Change AUTH-ASSERTION-JWT to your PayPal-Auth-Assertion token.
Change REQUEST-ID to a unique alphanumeric set of characters such as a time stamp.
Use the token as the payment source and complete the rest of the source object for your use case and business.
Use your setup token ID to pass in the payment source parameter and type as the SETUP_TOKEN.

Step result

A successful request results in the following:

An HTTP response code of 200 or 201. Returns 200 for an idempotent request.
ID of the payment token and associated payment method information.
HATEOAS links:

Rel, Method, Description
Rel	Method	Description
`delete`	`DELETE`	Make a DELETE request to delete the payment token.
`self`	`GET`	Make a GET request to this link to retrieve data about the saved payment method.

8. Integrate back end

The following sample shows a complete back-end integration to save PayPal for purchase later:

import "dotenv/config";
import express from "express";
const { PORT = 8888 } = process.env;
const app = express();
app.set("view engine", "ejs");
app.use(express.static("public"));
// Create setup token
app.post("/create/setup/token", async (req, res) => {
  try {
     // Use your access token to securely generate a setup token
     // with an empty payment_source
    const vaultResponse = await fetch("https://api-m.sandbox.paypal.com/v3/vault/setup-tokens", {
        method: "POST",
        body: JSON.stringify({ payment_source: { paypal: { usage_type: "MERCHANT" } } }),
        headers: {
            "Authorization": "Bearer ${ACCESS-TOKEN}",
            "PayPal-Request-Id": Date.now(),
            "PayPal-Partner-Attribution-Id": "BN-CODE",
            "PayPal-Auth-Assertion": "AUTH-ASSERTION-JWT"
        }
    })
    // Return the reponse to the client
    res.json(vaultResponse);
  } catch (err) {
    res.status(500).send(err.message);
  }
})
// Create payment token from a setup token
app.post("/create/payment/token/:setupToken", async (req, res) => {
  const { setupToken } = req.params;
  try {
    const paymentTokenResult = await fetch(
        "https://api-m.sandbox.paypal.com/v3/vault/payment-tokens",
        {
          method: "POST",
          body: {
              payment_source: {
                  token: {
                      id: setupToken,
                      type: "SETUP_TOKEN"
                  }
              }
          },
          headers: {
            "Authorization": "Bearer ${ACCESS-TOKEN}",
            "PayPal-Request-Id": Date.now(),
            "PayPal-Partner-Attribution-Id": "BN-CODE",
            "PayPal-Auth-Assertion": "AUTH-ASSERTION-JWT"
          }
        })
    const paymentMethodToken = paymentTokenResult.id
    const customerId = paymentTokenResult.customer.id
    await save(paymentMethodToken, customerId)
    res.json(captureData);
  } catch (err) {
    res.status(500).send(err.message);
  }
})
const save = async function(paymentMethodToken, customerId) {
    // Specify where to save the payment method token
}
app.listen(PORT, () => {
  console.log('Server listening at http://localhost:${PORT}/');
})

9. Integrate front end

The following sample shows how a full script to save PayPal might appear in HTML:

<div id="paypal-buttons-container"></div>
<script src="https://www.paypal.com/sdk/js?client-id=CLIENT-ID&merchant-id=MERCHANT-ID" data-user-id-token="ID-TOKEN"></script>
<script>
    window.paypal.Buttons({
        createVaultSetupToken: async () => {
                // The merchant calls their server API to generate a setup token
                // and return it here as a string
                const result = await fetch("example.com/create/setup/token", {
                  method: "POST",
                })
                return result.token
        },
        onApprove: async ({ vaultSetupToken }) => {
            return fetch("example.com/create/payment/token", { body: JSON.stringify({ vaultSetupToken }) })
        },
        onError: (error) => {
            console.log("An error occurred: ", error)
        }
    }).render("#paypal-buttons-container");
</script>

10. Test your integration

Render a PayPal Button with callbacks defined.
Select the button and complete the pop-up flow to approve saving the PayPal Wallet.
On your server, save the vaultSetupToken and the PayPal-generated customer.id. Associate these tokens with the designated payer.
Make a call on your server to swap your setup token for a payment token from the Payment Method Tokens API.
Save or use an existing customer.id depending on whether the payer is a first-time payer or returning payer:

1. For a first-time payer, save the PayPal-generated customer.id. The customer.id identifies the payer and their saved payment methods.
2. For a returning payer, use the PayPal-generated customer.id to swap the setup-token for a payment-token.
Save the payment-token for future use.

Optional: Show saved payment methods

We recommend creating a page on your site where payers can see their saved payment methods as in the following example:

Next steps

Go live

Move from PayPal's production environment to go live.

To save PayPal Wallets, payers need to log in to your site, make a purchase, and remain on your site when transactions take place.

Customers with a PayPal Wallet can:

Review PayPal transactions and transaction history
Review, add, or remove funding sources
Review and cancel recurring payments
Hold a balance in their PayPal account
Use PayPal to send and receive money
Withdraw money to a linked bank account
Use PayPal to transact with merchants

Use cases

Businesses save payment methods if they want customers to:

Check out without re-entering a payment method
Pay after use, for example, ride-sharing and food delivery

Know before you code

To save payment methods, you must be able to identify payers uniquely. For example, payers create an account and log in to your site.
Complete the steps in Get started to get the following sandbox account information from the Developer Dashboard:
- Your sandbox account login information
- Your access token

This integration requires a PayPal Developer account.
This integration must include a server-side call to exchange a setup token for a payment method token.

How it works

PayPal encrypts payment method information and stores it in a digital vault for that customer.

The payer saves their payment method.
For a first-time payer, PayPal creates a customer ID. Store this within your system for future use.
When the customer returns to your website and is ready to check out, pass their PayPal-generated customer ID to the JavaScript SDK. The customer ID tells the JavaScript SDK to save or reuse a saved payment method.
The payer completes a billing agreement.
The JavaScript SDK populates the checkout page with each saved payment method. Each payment method appears as a one-click button next to other ways to pay.

The checkout process is now shorter because it uses saved payment information.

1. Check eligibility

Go to paypal.com and sign in with your business account.
Go to Account Settings > Payment Preferences > Save PayPal and Venmo payment methods.
In the Save PayPal and Venmo payment methods section, select Get Started.
When you submit profile details, PayPal reviews your eligibility to save PayPal Wallets and Venmo accounts.
After PayPal reviews your eligibility, you'll see a status of Success, Need more information, or Denied.

2. Set up account to save payments

Set up your sandbox and live business accounts to save payment methods:

Log in to the Developer Dashboard.
Under REST API apps, select your app name.
Under Sandbox App Settings > App Feature Options, check Accept payments.
Expand Advanced options. Confirm that Vault is selected.

To go live, you'll need to be vetted to save PayPal Wallets. You can start the vetting process from the Developer Dashboard.

Only your sandbox business account is enabled to save payment methods. Your developer account remains unaffected.
You'll complete production onboarding when you're ready to go live.

3. Generate user ID token for payer

The PayPal OAuth 2.0 API has a response_type parameter. Set the response_type to id_token to retrieve a unique ID token for a payer.

First-time payer

A payer wants to save a payment method for the first time. Modify the POST request to generate id_token for the payer.

Returning payer

A payer wants to use a saved payment method.

Note: Use the customer identifier generated by PayPal, not the identifier that you use to identify the customer in your system.

Sample server-side user ID token request

curl -s -X POST https://api-m.sandbox.paypal.com/v1/oauth2/token \
 -u CLIENT-ID:CLIENT-SECRET \
 -H 'Content-Type: application/x-www-form-urlencoded' \
 -H 'PayPal-Partner-Attribution-Id: BN-CODE' \
 -H 'PayPal-Auth-Assertion: AUTH-ASSERTION-JWT' \
 -d 'grant_type=client_credentials' \
 -d 'response_type=id_token'

Modify the code

Copy the code sample and modify it as follows:

Change CLIENT-ID to your client ID.
Change CLIENT-SECRET to your client secret.
For a returning payer, change the CUSTOMER-ID to the PayPal-generated customer ID.
Change BN-CODE to your PayPal Attribution ID to receive revenue attribution. To find your BN code, see Code and Credential Reference.
Change AUTH-ASSERTION-JWT to your PayPal-Auth-Assertion token.

A successful request returns fields including an access_token, id_token, and the number of seconds the access_token token is valid.

The id_token:

Uniquely identifies each payer.
Expires in a few minutes because it's meant to be used during checkout. Generate new tokens if the current tokens expire.

Tip: Each buyer session is unique. Set up your server to generate a new client token each time payment fields render on your page.

4. Pass user ID token to JavaScript SDK

Pass the id_token into the JavaScript SDK through the data-user-id-token.

<script src="https://www.paypal.com/sdk/js?client-id=CLIENT-ID&merchant-id=MERCHANT-ID" data-user-id-token="ID-TOKEN"></script>

Modify the code

Copy the code sample and modify it as follows:

Change CLIENT-ID to your client ID.
Change MERCHANT-ID to your merchant ID.
Change ID-TOKEN to the id_token from the previous step.

5. Add PayPal button

Include client-side callbacks to:

Manage interactions with APIs
Manage payer approval flows
Handle any events that lead to cancellation or error during payer approval

<div id="DIV-ID"></div>
<script>
    window.paypal.Buttons({
        createVaultSetupToken: async () => {},
        onApprove: async ({ vaultSetupToken }) => {},
        onError: (error) => {}
    }).render("YOUR-DIV-ID");
</script>

Modify the code

Copy the code sample and modify it as follows:

Replace DIV-ID with a div id of your choice.
Replace YOUR-DIV-ID with the div id you created.

6. Create setup token

You request a setup token from your server. Pass the setup token from your server to the SDK with the createVaultSetupToken callback.

The createVaultSetupToken callback:

Calls the server endpoint you created to generate and retrieve the setup token.
Makes a request to your server endpoint.

Then, your server uses its access token to create and return the setup token to the client.

Any errors that occur while creating a setup token show up in the onError callback provided to the card fields component.

Supported callback

Callback, Returns, Description
Callback	Returns	Description
`createVaultSetupToken`	Setup token (string)	The merchant's server must receive this callback. Create a setup token for cards from the merchant server. The SDK then saves the payment method and updates the setup token with payment method details.

Client-side code sample

window.paypal.Buttons({
  createVaultSetupToken: async () => {
    // The merchant calls their server API to generate a setup token
    // and return it here as a string
    const result = await fetch("example.com/create/setup/token", {
      method: "POST"
    })
    return result.token
  }
})

Server-side code sample

Set up your server to call the Payment Method Tokens API. The button that the payer selects determines the payment_source sent in the following sample.

This SDK uses the Payment Method Tokens API to save payment methods in the background. Use the following request to add attributes needed to save a PayPal Wallet:

Note: The return_url and cancel_url values are required, but can have filler values such as in the following sample.

curl -v -k -X POST https://api-m.sandbox.paypal.com/v3/vault/setup-tokens \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -H 'PayPal-Partner-Attribution-Id: BN-CODE' \
  -H 'PayPal-Auth-Assertion: AUTH-ASSERTION-JWT' \
  -H 'PayPal-Request-Id: REQUEST-ID' \
  -d '{
          "payment_source": {
              "paypal": {
                  "usage_type": "PLATFORM",
                  "experience_context": {
                    "return_url": "https://example.com/returnUrl",
                    "cancel_url": "https://example.com/cancelUrl"
                  }
              }
          }
      }'

Modify the code

Change ACCESS-TOKEN to your sandbox app's access token.
Change BN-CODE to your PayPal Attribution ID to receive revenue attribution. To find your BN code, see Code and Credential Reference.
Change AUTH-ASSERTION-JWT to your PayPal-Auth-Assertion token.
Change REQUEST-ID to a set of unique alphanumeric characters such as a time stamp.
In the createVaultSetupToken, call the endpoint on your server to create a setup token with the Payment Method Tokens API. createVaultSetupToken returns the setup token as a string.

Callback, Returns, Description
Callback	Returns	Description
`onApprove`	`{ vaultSetupToken: string }`	The merchant gets the updated `vaultSetupToken` when the payment method is saved. The merchant must store the `vaultSetupToken` token in their system.

Client-side sample request

Modify the following request to match your server endpoint and payload:

window.paypal.Buttons({
    onApprove: ({ vaultSetupToken }) => {
    // Send the vaultSetupToken to the merchant server
    // for the merchant server to generate a payment token
        return fetch("example.com/create/payment/token", { body: JSON.stringify({ vaultSetupToken }) })
    },
})

Sample API request and response

curl -v -k -X POST https://api-m.sandbox.paypal.com/v3/vault/payment-tokens \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -H 'PayPal-Partner-Attribution-Id: BN-CODE' \
  -H 'PayPal-Auth-Assertion: AUTH-ASSERTION-JWT' \
  -H 'PayPal-Request-Id: REQUEST-ID' \
  -d '{
         "payment_source": {
              "token": {
                  "id": "4G4976650J0948357",
                  "type": "SETUP_TOKEN"
              }
          }
      }'

Modify the code

Copy the code sample and modify it as follows:

Change ACCESS-TOKEN to your sandbox access token.
Change BN-CODE to your PayPal Attribution ID to receive revenue attribution. To find your BN code, see Code and Credential Reference.
Change AUTH-ASSERTION-JWT to your PayPal-Auth-Assertion token.
Change REQUEST-ID to a unique alphanumeric set of characters such as a time stamp.
Use the token as the payment source and complete the rest of the source object for your use case and business.
Use your setup token ID to pass in the payment source parameter and type as the SETUP_TOKEN.

Step result

A successful request results in the following:

An HTTP response code of 200 or 201. Returns 200 for an idempotent request.
ID of the payment token and associated payment method information.
HATEOAS links:

Rel, Method, Description
Rel	Method	Description
`delete`	`DELETE`	Make a DELETE request to delete the payment token.
`self`	`GET`	Make a GET request to this link to retrieve data about the saved payment method.

8. Integrate back end

The following sample shows a complete back-end integration to save PayPal for purchase later:

import "dotenv/config";
import express from "express";
const { PORT = 8888 } = process.env;
const app = express();
app.set("view engine", "ejs");
app.use(express.static("public"));
// Create setup token
app.post("/create/setup/token", async (req, res) => {
  try {
     // Use your access token to securely generate a setup token
     // with an empty payment_source
    const vaultResponse = await fetch("https://api-m.sandbox.paypal.com/v3/vault/setup-tokens", {
        method: "POST",
        body: JSON.stringify({ payment_source: { paypal: { usage_type: "MERCHANT" } } }),
        headers: {
            "Authorization": "Bearer ${ACCESS-TOKEN}",
            "PayPal-Request-Id": Date.now(),
            "PayPal-Partner-Attribution-Id": "BN-CODE",
            "PayPal-Auth-Assertion": "AUTH-ASSERTION-JWT"
        }
    })
    // Return the reponse to the client
    res.json(vaultResponse);
  } catch (err) {
    res.status(500).send(err.message);
  }
})
// Create payment token from a setup token
app.post("/create/payment/token/:setupToken", async (req, res) => {
  const { setupToken } = req.params;
  try {
    const paymentTokenResult = await fetch(
        "https://api-m.sandbox.paypal.com/v3/vault/payment-tokens",
        {
          method: "POST",
          body: {
              payment_source: {
                  token: {
                      id: setupToken,
                      type: "SETUP_TOKEN"
                  }
              }
          },
          headers: {
            "Authorization": "Bearer ${ACCESS-TOKEN}",
            "PayPal-Request-Id": Date.now(),
            "PayPal-Partner-Attribution-Id": "BN-CODE",
            "PayPal-Auth-Assertion": "AUTH-ASSERTION-JWT"
          }
        })
    const paymentMethodToken = paymentTokenResult.id
    const customerId = paymentTokenResult.customer.id
    await save(paymentMethodToken, customerId)
    res.json(captureData);
  } catch (err) {
    res.status(500).send(err.message);
  }
})
const save = async function(paymentMethodToken, customerId) {
    // Specify where to save the payment method token
}
app.listen(PORT, () => {
  console.log('Server listening at http://localhost:${PORT}/');
})

9. Integrate front end

The following sample shows how a full script to save PayPal might appear in HTML:

<div id="paypal-buttons-container"></div>
<script src="https://www.paypal.com/sdk/js?client-id=CLIENT-ID&merchant-id=MERCHANT-ID" data-user-id-token="ID-TOKEN"></script>
<script>
    window.paypal.Buttons({
        createVaultSetupToken: async () => {
                // The merchant calls their server API to generate a setup token
                // and return it here as a string
                const result = await fetch("example.com/create/setup/token", {
                  method: "POST",
                })
                return result.token
        },
        onApprove: async ({ vaultSetupToken }) => {
            return fetch("example.com/create/payment/token", { body: JSON.stringify({ vaultSetupToken }) })
        },
        onError: (error) => {
            console.log("An error occurred: ", error)
        }
    }).render("#paypal-buttons-container");
</script>

10. Test your integration

Render a PayPal Button with callbacks defined.
Select the button and complete the pop-up flow to approve saving the PayPal Wallet.
On your server, save the vaultSetupToken and the PayPal-generated customer.id. Associate these tokens with the designated payer.
Make a call on your server to swap your setup token for a payment token from the Payment Method Tokens API.
Save or use an existing customer.id depending on whether the payer is a first-time payer or returning payer:

1. For a first-time payer, save the PayPal-generated customer.id. The customer.id identifies the payer and their saved payment methods.
2. For a returning payer, use the PayPal-generated customer.id to swap the setup-token for a payment-token.
Save the payment-token for future use.

Optional: Show saved payment methods

We recommend creating a page on your site where payers can see their saved payment methods as in the following example:

Next steps

Go live

Move from PayPal's production environment to go live.

Save PayPal for purchase later with the JavaScript SDK

Go live

On this page

On this page

On this page

If you accept cookies, we’ll use them to improve and customize your experience and enable our partners to show you personalized PayPal ads when you visit other sites. Manage cookies and learn more

Save PayPal for purchase later with the JavaScript SDK

Go live

On this page

On this page