Getting Started
Welcome to the Nusio Saka Payment Gateway developer documentation. This reference covers everything you need to integrate payment collection, wallet disbursement, and settlement reporting into your application.
Two API Families
We offer two API surfaces depending on your integration history:
| Merchant API V1 | Legacy API (UTpay) | |
|---|---|---|
| Recommended for | New integrations | Existing UTpay merchants |
| Base path | /v1/ | /api/ |
| Authentication | X-API-Key header | SHA-512 signature (orders) / RSA X-SIGNATURE (disbursements) |
| Amount units | Minor units (100 = IDR 1) | Full IDR integers |
| Response format | {"success": true, "data": {...}} | {"code": 200, "message": "...", "data": {...}} |
| Webhooks | JSON with event field | UTpay compact format |
If you are already live with UTpay credentials, you do not need to change anything. Your existing integration will continue to work against the Legacy API endpoints. When you are ready to migrate, see the Migration Guide.
Base URLs
| Environment | Nusio Saka | Flypay (Whitelabel) |
|---|---|---|
| Production | https://api.nusio-saka.com | https://api.flypay.asia |
There is no separate public sandbox. Use your production credentials with small test amounts, or request test credentials from your account manager.
Amount Units
This is the most important difference between V1 and Legacy:
-
V1 API — all amounts are in minor units. 1 IDR = 100 minor units.
An order for IDR 50,000 →"amount_minor": 5000000 -
Legacy API — all amounts are full IDR integers.
An order for IDR 50,000 →"totalAmount": 50000
Do not send amount_minor: 50000 to V1 — that is only IDR 500. Always multiply by 100.
Getting Your Credentials
Your credentials are managed in the merchant dashboard:
- Nusio Saka merchants: app.nusio-saka.com
- Flypay merchants: app.flypay.asia
Navigate to Settings → API Credentials to find your:
- API Key — used for V1 API authentication
- API Secret — used to generate request signatures (optional but recommended)
- Webhook Secret — used to verify incoming webhook payloads
For Legacy API (UTpay migration), your platform administrator sets your legacy_client_id, legacy_client_secret, and uploads your RSA public key via the Admin Dashboard.
Next Steps
- New integration? → 5-minute Quick Start
- Migrating from UTpay? → Migration Guide
- V1 API reference → Merchant API Overview
- Legacy API reference → Legacy API Overview