How to migrate from NFT checkout to thirdweb Pay

As of today, thirdweb is deprecating Paper's NFT Checkout. All Paper services will shut down on June 24, 2024. After June 24, 2024, payments will no longer be accepted and transactions will no longer be processed.

Much like Paper's NFT Checkouts, thirdweb Pay allows developers to add credit card and debit card purchases for any onchain transaction, including mints and NFT purchases.

We'll show you how you can replace your NFT Checkout with Pay in this step-by-step guide.

Replacing Embedded Elements with thirdweb Pay

1. Note down the contract & mint or purchase function you are calling from your NFT Checkout element.
2. Remove any references to <CheckoutWithCard />or <CheckoutWithEth />
3. If you're using the Paper SDK, uninstall it: npm uninstall paperxyz
4. Install the thirdweb Connect SDK.
   1. If you're using the thirdweb/dev legacy SDK, we encourage you to upgrade to the latest SDK. You can follow this migration guide: https://portal.thirdweb.com/typescript/v5/migrate
   2. If you're not using the thirdweb/dev legacy SDK, you can install the latest SDK:
      1. npm i thirdweb
5. If you do not have a thirdweb Client ID, create one in your thirdweb dashboard settings.
6. Call your mint or purchase function using the Pay Transaction Flow
   1. Users with enough funds in their wallet to purchase will execute the transaction immediately.
   2. Users without enough funds will be prompted by thridweb Pay to onramp funds with a credit card. Once funds are onramped, users can execute the transaction within Pay's flow.

Replacing Checkout Links with thirdweb Pay

1. Note down the contract & mint or purchase function you are calling from your Checkout Link.
2. Remove references to your checkout link.
3. Install the thirdweb Connect SDK.
   1. If you're using the thirdweb/dev legacy SDK, we encourage you to upgrade to the latest SDK. You can follow this migration guide: https://portal.thirdweb.com/typescript/v5/migrate
   2. If you're not using the thirdweb/dev legacy SDK, you can install the latest SDK:
      1. npm i thirdweb
4. If you do not have a thirdweb Client ID, create one in your thirdweb dashboard settings.
5. Call your mint or purchase function using the Pay Transaction Flow
   1. Users with enough funds in their wallet to purchase will execute the transaction immediately.
   2. Users without enough funds will be prompted by thridweb Pay to onramp funds with a credit card. Once funds are onramped, users can execute the transaction within Pay's flow.

Frequently Asked Questions

What is Paper Deprecation?

Paper deprecation means that we are no longer maintaining Paper services in the process of shutting down the service for our NFT Checkouts and Embedded Wallets offerings. For each of these, this means:

NFT Checkouts - Payments will no longer be accepted and transactions will no longer be processed.

Embedded Wallets - Your users will no longer be able to access the private key and functionalities for their wallets using the thirdweb website

When is Paper going to shut down its services?

We will be shutting down Paper services on June 24, 2024.

Who does this affect?

Paper deprecation affects:

1) All developers who have implemented NFT Checkouts.

2) All developers who have generated at least one wallet through Paper's Embedded Wallet Service.

Will thirdweb Pay require KYC?

Pay currently requires KYC for first-time fiat purchases. Subsequent purchases will not require KYC.

What chains does thirdweb Pay support?

You can view a full list of supported chains in thirdweb's docs.

What jurisdictions does thirdweb Pay support?

As of today, thirdweb Pay supports payments in 130+ countries. We support all jurisdictions EXCEPT:

• Afghanistan
• Africa (All Countries)
• Belarus
• Bolivia
• China
• Cuba
• Colombia
• Haiti
• Honduras
• Iran
• Iraq
• Latvia
• Lebanon
• Myanmar
• Pakistan
• Qatar
• Russia
• Ukraine
• United Arab Emirates
• Venezuela
• Yemen