Sandbox

The sandbox environment allows partners to test their Stable Mint Payments integration without processing real payments. This environment simulates the complete payment flow using test data and mock banking services.

Overview

The sandbox environment mirrors the production API but uses different base domains and allows testing with simulated payments.

Base URLs

Environment	Base Domain
Production	stablemint.io
Sandbox	stablemint.net

API Endpoints

Simply replace the domain in your API calls:

• Production: https://paymentinitiationservice-rest.stablemint.io/session/hosted
• Sandbox: https://paymentinitiationservice-rest.stablemint.net/session/hosted

Test Banking

The sandbox environment includes a mock banking system that simulates real payment flows without moving actual funds.

Features

• Fake Bank Integration: Use test bank accounts to simulate customer deposits
• No Real Money: All transactions are simulated - no actual funds are transferred
• Full API Coverage: Test all endpoints and payment flows
• Webhook Testing: Receive real webhook notifications for test transactions
• Error Simulation: Test error scenarios and edge cases

Test Credentials

Your sandbox API credentials are separate from production:

• Use sandbox API keys provided during onboarding
• Test with mock customer data
• Simulate various payment scenarios

Important Notes

1. Testing Only: The sandbox environment is strictly for testing and development
2. Data Isolation: Sandbox data is completely isolated from production
3. No Real Transactions: No actual money moves in the sandbox environment
4. Regular Resets: Test data may be periodically cleared
5. Feature Parity: Sandbox maintains the same features as production

Getting Started

1. Obtain sandbox API credentials from your account manager
2. Update your integration to use stablemint.net domains
3. Test your complete payment flow with mock data
4. Verify webhook handling with test events
5. Once testing is complete, switch to production domains

Best Practices

• Test all payment scenarios before going live
• Verify error handling with various failure cases
• Test webhook processing thoroughly
• Document any differences between sandbox and production behavior
• Keep sandbox and production credentials separate and secure