API Overview
iPint REST API reference — base URLs, authentication, and versioning.
The iPint REST API lets you create payment sessions, generate invoices, check payment status, and manage settlement preferences.
Base URLs
| Environment | Base URL |
|---|---|
| Mainnet (Production) | https://api.ipint.io:8003 |
| Testnet (Development) | https://api.ipint.io:8002 |
API version
Current version: 1.0.0
Request format
- All endpoints return JSON objects or arrays
POSTrequests send JSON data in the request body- Set the
Content-Type: application/jsonheader on all POST requests
Authentication
Some endpoints require an HMAC signature in the request headers, generated using your API secret.
Never share your API secret in any API request. Use it only to generate the HMAC signature on your server. See Authentication.
API categories
The iPint API is divided into two categories:
Merchant API
Accept digital asset payments from your customers. This is the primary API for most businesses.
POST /checkout— create a hosted checkout sessionPOST /invoice— generate a QR code paymentGET /invoice— check payment statusPOST /confirm— mark invoice as paidGET /currencies— list supported currenciesGET /prices— conversion rates and limitsPOST /preferences— add settlement walletPUT /preferences— update settlement wallet
Payment Service Provider API
Allow your merchants to accept digital asset payments. For payment service providers and platforms with multiple merchants.
POST /aggregator/merchants— onboard a merchantGET /merchant/account— get S3 URL for KYC document uploadPOST /preferences— set merchant settlement info (withmerchant_id)PUT /settings— update merchant profile
→ Aggregator / PSP documentation
The PSP API is available on request. Contact help@ipint.io for access.
Interactive docs
For the full interactive API explorer (Swagger UI), visit https://ipint.io:8010/docs/.
Next steps
- Authentication — how to sign requests
- POST /checkout — create a payment session
- Webhooks — payment status callbacks