Production Launch
Follow this checklist to ensure you are ready for production launch with Embedded Checkout
From Staging to Production with Embedded Checkout
Embedded checkout in production requires enablement by the Customer Success Engineering team. Contact Crossmint’s team to get access.
Crossmint provides two developer environments: staging and production. It's recommended to test end-to-end on staging before moving to production.
General Launch Checklist
Complete the following general steps on each tab to launch your checkout in production:
Account Verification
To launch in production, you must verify your project account in the production console.
Additionally, if as a seller you choose to accept credit card payments, you are required to complete a fast KYC process (usually takes 2 minutes on average).
You only have to verify a project once, and can create as many collections as you wish within that project. New projects require additional verification.
For full details on the project and collection verification process, requirements, and troubleshooting, please read our account verification documentation.
Account Verification
To launch in production, you must verify your project account in the production console.
Additionally, if as a seller you choose to accept credit card payments, you are required to complete a fast KYC process (usually takes 2 minutes on average).
You only have to verify a project once, and can create as many collections as you wish within that project. New projects require additional verification.
For full details on the project and collection verification process, requirements, and troubleshooting, please read our account verification documentation.
Collection Verification
In the console, go to the collections page and click on "Verify Collection" on the collection you want to verify.
Collections sold using Crossmint's checkout or claims page must be verified to ensure compliance with our content policy.
For full details on the project and collection verification process, requirements, and troubleshooting, please read our account verification documentation.
Transaction Limits
The lower bound limit is USD $0.75 per purchase for primaries and secondaries, and the upper bound limit is USD $1,500 for primaries, and USD $7,000 per purchase for secondaries (marketplaces). Those limits are per purchase. Users can make multiple purchases with total amounts surpassing those thresholds.
If you require higher limits, contact sales.
Smart Contract Configuration (Optional - NFT only)
If you are using your own smart contract, please ensure that the following parameters and criteria are configured in your smart contract properly:
- Price per NFT - ensure that the value is configured correctly.
- If doing a claim - Conditions for claim - double check the starting time, closing time, recipient address, revenue split, and other claim conditions are in order.
- If limiting to accesslists - confirm that the accesslist is up-to-date and the appropriate permissions are set.
Launch Checklist
- Change your API keys to the production versions. Ensure your production API key has the appropriate scopes enabled, such as
orders.create. - Update your collection ID to the production one.
- As needed, change your passed-in props to be production ready (e.g. make
email,payment,lineItemsprogrammatically filled).
See Code Example
See Code Example
Production Launch
Follow this checklist to ensure you are ready for production launch with Embedded Checkout
From Staging to Production with Embedded Checkout
Embedded checkout in production requires enablement by the Customer Success Engineering team. Contact Crossmint’s team to get access.
Crossmint provides two developer environments: staging and production. It's recommended to test end-to-end on staging before moving to production.
General Launch Checklist
Complete the following general steps on each tab to launch your checkout in production:
Account Verification
To launch in production, you must verify your project account in the production console.
Additionally, if as a seller you choose to accept credit card payments, you are required to complete a fast KYC process (usually takes 2 minutes on average).
You only have to verify a project once, and can create as many collections as you wish within that project. New projects require additional verification.
For full details on the project and collection verification process, requirements, and troubleshooting, please read our account verification documentation.
Account Verification
To launch in production, you must verify your project account in the production console.
Additionally, if as a seller you choose to accept credit card payments, you are required to complete a fast KYC process (usually takes 2 minutes on average).
You only have to verify a project once, and can create as many collections as you wish within that project. New projects require additional verification.
For full details on the project and collection verification process, requirements, and troubleshooting, please read our account verification documentation.
Collection Verification
In the console, go to the collections page and click on "Verify Collection" on the collection you want to verify.
Collections sold using Crossmint's checkout or claims page must be verified to ensure compliance with our content policy.
For full details on the project and collection verification process, requirements, and troubleshooting, please read our account verification documentation.
Transaction Limits
The lower bound limit is USD $0.75 per purchase for primaries and secondaries, and the upper bound limit is USD $1,500 for primaries, and USD $7,000 per purchase for secondaries (marketplaces). Those limits are per purchase. Users can make multiple purchases with total amounts surpassing those thresholds.
If you require higher limits, contact sales.
Smart Contract Configuration (Optional - NFT only)
If you are using your own smart contract, please ensure that the following parameters and criteria are configured in your smart contract properly:
- Price per NFT - ensure that the value is configured correctly.
- If doing a claim - Conditions for claim - double check the starting time, closing time, recipient address, revenue split, and other claim conditions are in order.
- If limiting to accesslists - confirm that the accesslist is up-to-date and the appropriate permissions are set.
Launch Checklist
- Change your API keys to the production versions. Ensure your production API key has the appropriate scopes enabled, such as
orders.create. - Update your collection ID to the production one.
- As needed, change your passed-in props to be production ready (e.g. make
email,payment,lineItemsprogrammatically filled).
See Code Example
See Code Example