API Resources
API Resources
The API Resources section contains common platform configuration details and shared integration resources used across Elite Neo Bank APIs. Use this page as a quick reference for:- Base URLs
- API environments
- Request formats
- Response formats
- Supported currencies
- Transfer modes
- API versioning
- Developer utilities
API Environments
Elite Neo Bank provides separate environments for testing and production usage.Base URLs
Sandbox
- Integration testing
- UAT validation
- Mock transaction flows
- Webhook testing
Production
- Live customer payments
- Real payout processing
- Production banking operations
API Versioning
Current API version:Request Format
All API requests should use:- Use valid JSON
- Follow endpoint-specific schemas
- Include required parameters
Response Format
All API responses are returned in JSON format. Example response structure:Character Encoding
Supported encoding:Timezone Standard
Recommended timezone handling:- UNIX timestamps (seconds)
- Server-side generation
Supported Currencies
Elite Neo Bank supports multi-currency processing for global payment and banking workflows. Supported currencies may vary depending on:- Merchant category
- Settlement region
- Banking partner support
- Regulatory requirements
- Cross-border enablement
Important Notes
- Currency availability may vary by merchant account
- Cross-border payouts may require additional approval
- Certain currencies may support payments only
- Settlement currencies may differ from transaction currencies
- FX conversion rates may apply for international transactions
Supported Transfer Modes
Authentication Method
Elite Neo Bank APIs use:- API Key authentication
- HMAC SHA256 request signing
- UNIX timestamp validation
➡️ Authentication → Timestamp
➡️ Authentication → Signature
HTTP Methods
Supported API methods:Common HTTP Status Codes
Elite Neo Bank APIs use standard HTTP status codes along with structured API responses to indicate request status, authentication results, validation errors, transaction states, and server-side processing outcomes. Merchants should always validate:- HTTP status codes
- API response body
- Transaction status values
- Error messages
Example Success Response
API Rate Limits
API rate limits may apply depending on:- Merchant category
- Environment
- Transaction volume
- Risk profile
Postman Collection
Elite Neo Bank Postman collections help developers:- Test APIs quickly
- Validate authentication
- Simulate transaction flows
- Sandbox testing
- UAT validation
- Webhook testing
SDK Support
Official SDKs may be available for:- PHP
- Node.js
- Python
- Java
- .NET
- Go
Webhook Resources
Webhook integration references: ➡️ Webhooks → Webhook Setup➡️ Webhooks → Signature Verification
➡️ Retry Handling
Production Resources
Production readiness references: ➡️ Going Live➡️ Production Checklist
➡️ Security Checks
➡️ IP Whitelisting
Support
For:- API onboarding
- Production activation
- Payout enablement
- Sandbox access
- Integration support
