Aggregator / PSP Overview
Payment Service Provider API for onboarding and managing merchants.
Aggregator / PSP API
The Aggregator (Payment Service Provider) API allows platforms with multiple merchants to onboard them, manage KYC documents, configure settlement, and update profiles — all programmatically.
The PSP API is available on request. Contact help@ipint.io for access and credentials.
Getting started as an Aggregator
Register and verify your PSP account
Complete registration at dashboard.ipint.io/register/. Once your PSP account is verified, you can onboard merchants.
Onboard a merchant
Call
POST /aggregator/merchantswith the merchant's business details, KYC confirmations, and fee structure.Submit merchant KYC documents
Call
GET /merchant/accountto get an AWS S3 presigned URL for each document, then upload the documents.Configure merchant settlement
Call
POST /preferenceswith the merchant's wallet address and settlement cycle.Integrate payments
Use POST /checkout with the
merchant_idparameter to create payments on behalf of your merchants.
Required merchant information
To onboard a merchant, you need:
- Merchant's confirmation that they agree with iPint's Terms of Service, Privacy Policy, and AML/CFT Policy
- Merchant's confirmation that the PSP can share their KYC details with iPint
- PSP's confirmation that KYC/AML check has been done on the merchant
- Merchant's KYC details (business info, beneficial owner info)
- Merchant fee (percentage) to be charged from the merchant
- Merchant's KYC documents:
- Proof of Business Entity (Certificate of Incorporation or business license)
- Proof of Business Address (utility bill or lease agreement)
- Photo ID of Beneficial Owner (Passport or National ID)
- Bank Statement (3 months)
- Tax ID documents (EIN, IRS letter, W9, or tax return — for US, Netherlands & German merchants)
Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /aggregator/merchants | Onboard a merchant |
GET | /merchant/account | Get S3 URL for KYC document upload |
POST | /preferences | Set merchant settlement info |
PUT | /settings | Update merchant profile |
Authentication
All aggregator endpoints require HMAC-SHA384 authentication
with apikey, signature, and nonce headers.
Next steps
- Onboard a Merchant — POST /aggregator/merchants
- Submit KYC Documents — GET /merchant/account
- Settlement Info — POST /preferences
- Update Merchant Profile — PUT /settings