A comprehensive, global payment processing solution by CREDVAULT LIMITED designed to meet all modern payment needs with enterprise-grade security and scalability.
- Global coverage, multi-currency, and local payment support
- Instant payouts and real-time settlements
- PCI DSS Level 1, HSM integration, advanced fraud detection
- Developer-friendly APIs, SDKs, and documentation
- Responsive admin dashboard and analytics
- Support for subscriptions, marketplaces, and more
- Rust Core: High-performance payment processing
- Go API Gateway: Efficient API handling
- TypeScript/React Admin Dashboard: Modern UI
- Multi-cloud, Kubernetes, Terraform, zero-downtime deployments
See the workspace for detailed folder layout and code organization.
- Run the setup script to download DeepSeek Coder models:
bash scripts/setup-deepseek-coder.sh
- Run the setup script to download DeepSeek R1 and Companion models:
bash scripts/download-deepseek-r1.sh
- Verify models are stored in both
src/ai/deepseek-coder/models
andsrc/ai/deepseek-companion/models
.- Both directories must be present and populated for full migration or advanced features.
- Ensure folder structure matches what the scripts expect.
To load a model locally:
await modelManager.loadLocalModel('deepseek-coder-33b-instruct');
await modelManager.loadLocalModel('deepseek-coder-6.7b-instruct');
await modelManager.loadLocalModel('deepseek-coder-33b-base');
// For DeepSeek R1/Companion, see src/ai/deepseek-companion/README.md for usage examples.
- Models are stored locally for full control.
- GPU requirements: Large models (e.g., 33B, 70B, 671B) require significant GPU memory (e.g., 33B needs ~45GB, 70B/671B much more).
- Fine-tuning: Use
setupTrainingEnvironment
inModelManager.js
. - If you encounter issues, check that all model directories exist and are populated as expected.
- After migration or adding new models/services, run the security test script:
node scripts/run-security-test.js
- Review and update your security configuration as needed. See
docs/SECURITY_CHECKLIST.md
for best practices.
- Clone the repository:
git clone https://github.com/yourusername/sunny.git cd sunny
- Install dependencies:
npm install
- Set up environment variables:
cp .env.example .env # Edit .env with your configuration
- Start the development server:
npm run dev
- Access the dashboard at http://localhost:3000
- Sign up at dashboard.sunnypayments.com
- Get your API keys from the dashboard
- Install the SDK:
npm install sunny-payment-gateway
- Initialize the SDK in your app:
import SunnySDK from 'sunny-payment-gateway'; const sunny = new SunnySDK({ apiKey: 'your_api_key', environment: 'sandbox' });
- Process a payment (see docs for details)
You can run the Sunny Payment Gateway in a real production environment on your local machine for safe preview and testing.
-
Install dependencies:
npm install --legacy-peer-deps
-
Run the production build locally:
ENV_FILE=.env.local-production node scripts/deploy-production.js --local-production
- This uses
.env.local-production
for all environment variables. - The app will be available at http://localhost:3000
- This uses
-
Stop the app:
docker-compose -f docker/production/docker-compose.yml down
You can edit
.env.local-production
to test different settings. For real production, use.env.production
and your live domain.
See CONTRIBUTING.md for guidelines.
MIT License. See LICENSE.
- Check the documentation
- Open an issue on GitHub
- Contact support at [email protected]