Testing overview

Exciting times! You have made it this far, you are almost ready to go live. All you have to do now is test your integration, complete a test transaction and then get ready to go live. Nice work! 🎉

Environments

Recommended way of testing

• If you're able to, we recommend you deploy your Onramper integration behind a feature flag or on a hidden page that allows you to do production testing.
• If you prefer to test locally, we recommend testing onramping with cards using Banxa for GBP/EUR. Banxa has the most mature sandbox environment.

Notes on environments

• When testing in sandbox use the https://buy.onramper.dev domain (ending with .dev)
• Sandbox API keys have the pk_test prefix. Production API keys have the pk_prod prefix.
• We generally recommend testing in production environments, as the sandboxes provided by onramps are non-standardized, and can often be janky.
• For onramps where no sandbox is available, we’ve made available the production environments of those onramps even in https://buy.onramper.dev. Therefore, be careful with testing with real card data in Onramper’s sandbox - you might be interacting with a production environment of an onramp.

Common pitfalls of onramp test-environments

• In some cases, testnet wallets used by onramps can be empty. If you run into this, feel free to notify us in the relevant support chat and we will pick this up with the onramp for you.
• Testing with APMs is generally not available. Instead, test cards should be used.
• Test cards differ per onramp, which you will see in the guide on the next page.
• Available assets (both fiat currencies and cryptocurrencies) might differ between sandbox environments and production environments.