iPintiPint Docs
Aggregator / PSP

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

  1. Register and verify your PSP account

    Complete registration at dashboard.ipint.io/register/. Once your PSP account is verified, you can onboard merchants.

  2. Onboard a merchant

    Call POST /aggregator/merchants with the merchant's business details, KYC confirmations, and fee structure.

  3. Submit merchant KYC documents

    Call GET /merchant/account to get an AWS S3 presigned URL for each document, then upload the documents.

  4. Configure merchant settlement

    Call POST /preferences with the merchant's wallet address and settlement cycle.

  5. Integrate payments

    Use POST /checkout with the merchant_id parameter to create payments on behalf of your merchants.

Required merchant information

To onboard a merchant, you need:

  1. Merchant's confirmation that they agree with iPint's Terms of Service, Privacy Policy, and AML/CFT Policy
  2. Merchant's confirmation that the PSP can share their KYC details with iPint
  3. PSP's confirmation that KYC/AML check has been done on the merchant
  4. Merchant's KYC details (business info, beneficial owner info)
  5. Merchant fee (percentage) to be charged from the merchant
  6. 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

MethodEndpointDescription
POST/aggregator/merchantsOnboard a merchant
GET/merchant/accountGet S3 URL for KYC document upload
POST/preferencesSet merchant settlement info
PUT/settingsUpdate merchant profile

Authentication

All aggregator endpoints require HMAC-SHA384 authentication with apikey, signature, and nonce headers.

Next steps

On this page