Skip to main content

Testing in Production

GStable operates exclusively on Mainnet to ensure access to real on-chain liquidity. We do not provide a Sandbox or Testnet environment.

This guide outlines how to verify your integration with minimal risk and cost using a "Left Pocket to Right Pocket" strategy.

Production Environment

All transactions on GStable involve Real Funds. There are no test assets. Please be careful when configuring amounts.

Why No Sandbox?

Our payment infrastructure is designed to operate in conditions that closely mirror real-world usage. In practice, testnet or sandbox environments introduce significant friction that makes meaningful integration and validation difficult:

  1. Limited Asset Availability
    Standard stablecoins and native gas tokens are often scarce or inconsistently distributed on testnets. Acquiring and maintaining these assets adds unnecessary overhead and slows down development and testing.

  2. Mismatch with Production Conditions
    Testnet environments differ substantially from mainnet in terms of performance, reliability, and user experience. These gaps make it hard to accurately evaluate behavior under realistic conditions, increasing uncertainty during integration.

  3. Higher Integration Complexity
    Because many ecosystem features and network capabilities are optimized or only fully available on mainnet, relying on a sandbox can introduce additional adaptation work rather than reducing it.

For these reasons, working directly in a production-like environment provides clearer signals, lower integration barriers, and a more representative end-to-end experience.

Testing Strategy: Left Pocket to Right Pocket

Since GStable uses a Non-custodial architecture, funds move directly from the Payer to the Merchant.

When you test a payment:

  1. You act as the Merchant: Funds arrive in your self-custodial wallet.
  2. You act as the Payer: You pay from your own crypto wallet.
  3. Result: The principal amount ($10) moves from your "Left Pocket" to your "Right Pocket".

Your only cost is the network fee and platform fee (~0.2%). You do not lose the principal amount.

Cost Estimate (Example)

ItemValueNote
Transaction Amount$10.00Principal (Returns to your wallet)
Platform Fee (0.2%)$0.02Cost
Gas Fee (Base/Arbitrum)~$0.01Cost
Total Cost~$0.03Very low cost for end-to-end verification

Integration Checklist

Follow this checklist to validate your integration safely.

1. Prerequisites

  • Minimum Amount: Ensure you are testing with at least $10 USD. The system minimum is $10 due to gas and routing constraints.
  • Test Network: We recommend using Base or Arbitrum for testing due to low gas fees.
  • Test Asset: Prepare USDC or USDT.

2. Create Test Product

  1. Go to Merchant Dashboard > Payment Links.
  2. Create a new Product:
    • Name: Integration Test Item
    • Price: $10.00 (Fixed Price)
  3. Generate a Payment Link.

To minimize fees and confirmation time, use the Same-Chain path.

  • Merchant Setting: Ensure your Collection Account supports Base USDC.
  • Payer Action: Use a wallet with Base USDC to complete the payment.
  • Path: Base USDC -> Base USDC.
    • Fee: 0.2%
    • Speed: ~ 30 seconds

4. Verify Success

  1. Frontend: Confirm the payment page shows "Payment Successful" or redirects correctly.
  2. Dashboard: Check that the Order Status updates to Paid.
  3. Webhook: Verify your server received the session.paid event.
  4. Wallet: Confirm $9.98 USDC (Principal - Fee) has arrived in your Merchant Wallet.

Once this flow is complete, your integration is fully verified for all supported chains and assets.