Integration Models
ADOPAY supports one shared capability platform with two integration models.
text
ADOPAY
│
┌────────────┴────────────┐
│ │
Merchant Partner
Direct Integration Partner Integration
│ │
│ ┌────┼────┐
│ │ │ │
│ M-A M-B M-C
│
Own Transactions
Own FundsMerchant Integration
Merchant directly integrates with ADOPAY and processes transactions for its own business.
| Aspect | Owner |
|---|---|
| API Credential | Merchant |
| Transaction Owner | Merchant |
| Fund Owner | Merchant |
| Webhook Receiver | Merchant |
| Settlement Owner | Merchant |
Typical onboarding:
text
Commercial contract
↓
ADOPAY back-office account setup
↓
Merchant receives API Credential
↓
Merchant calls Merchant APIMerchant API does not require a Create Merchant endpoint. Account opening is completed offline / via operations.
Partner Integration
Partner integrates with ADOPAY on behalf of multiple merchants.
| Aspect | Owner |
|---|---|
| API Credential | Partner |
| Transaction Owner | Merchant |
| API Caller | Partner |
| Webhook Receiver | Partner |
| Fund Owner | Configurable by partnership model |
| Settlement Owner | Configurable by partnership model |
Partner adds a merchant-dimension layer on top of the same transaction capabilities:
- Merchant Onboarding
- Merchant Management
- Transaction APIs scoped by
merchantId
Shared transaction core
Merchant and Partner Collection / Payout / Refund capabilities should reuse one Payment / Payout service — not two separate ledgers.
text
Merchant API ────────┐
│
▼
Payment / Payout Service
▲
│
Partner API ─────────┘