Skip to main content
The sandbox mode is similar to that of real world usage in most regards, however there are some differences depending on the service being used.

​
Prices

The prices used in sandbox are generally based on real world asset prices, for assets which exist (conceptually) on both mainnet and testnet. However the DEXes used on testnets are generally not arbitraged to be the same price. This can lead to the application reporting unexpectedly large (or possibly negative) fees.

​
KYC

If the user does not have an existing MoonPay or Stripe account, a mock KYC form will be shown. This will not require a valid SSN or credit card, however the user will have to provide a valid email and phone number to get past security checks. See test credit card details that can be provided, depending on the service. The sandbox testing mode can be enabled in the application by setting sandbox to true. API keys can be obtained by contacting [email protected]. Below is an example using the Payments Widget. To learn more about the Halliday API and its options, please reach out to [email protected]:
copy
import { openHallidayPayments } from "@halliday-sdk/payments";

openHallidayPayments({
    apiKey: HALLIDAY_PUBLIC_API_KEY,
    // USDC on Base
    outputs: ["base:0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"],
    ...

    // If set to true, will use service sandboxes and testnet chains.
    sandbox: true
});

​
Stripe Onramp KYC Mock Values

For testing Stripe onramp, use the following mock values for KYC:
KYC RequirementMock Value
SSN000-00-0000
Credit Card Number4242 4242 4242 4242
Credit Card Expiration08/30 (any future date)
Email Verification Code000000 (all zeros)
CVC123

​
Transak Onramp KYC Mock Values

For testing Transak onramp, see the guidelines for testing, which includes additional fiat currency and location details. The following mock values will work for testing in the United States:
KYC RequirementMock Value
SSN123-45-6789
Credit Card Number4024 7644 4997 1519
Credit Card Expiration10/2033
Email Verification Codereceive from email
Checkout Confirmation Code000000
CVC123

​
Moonpay Onramp KYC Mock Values

For testing Moonpay onramp, see the guidelines for testing. The following mock values will work for testing in the United States:
KYC RequirementMock Value
SSN123-12-3123
Credit Card Number5385 3083 6013 5181
Credit Card Expiration12/2030
Email Verification Codereceive from email
Checkout Confirmation CodeCheckout1!
CVC123

​
Banxa Onramp KYC Mock Values

For testing Banxa onramp, see the testing information. The following mock values will work for testing:
FieldValue
Card NameUse the name that you provided as part of KYC
Card Number4111 1111 1111 1111
ExpiryAny expiry date in the future
Security CodeAny

​
Considerations when testing MoonPay

MoonPay has several security features in place to detect and prevent fraud; given the nature of testing, it is possible some activities may be incorrectly tagged as fraudulent. To that end, it is recommended to follow these best practices to test an integration:
  • Do not use test credit cards in real world environments or the account will automatically be blocked.
  • Do not use the same MoonPay account across sandbox and real world environments or the account will automatically be blocked.
  • Fraud alerts / issues may occur if MoonPay suspects a user has multiple MoonPay accounts. Ensure that each tester uses a unique identifier (email, phone number, etc.) that has not been previously associated with MoonPay.
  • Sandbox testing may have outdated code, so it is possible there are unexpected bugs. Creation of multiple accounts with new fictitious KYC data is permitted when testing in sandbox.