MaxiPay
Quick Start
- Sign up at maxipay.com and obtain API credentials
- Create a terminal in the Admin Console with the parameters below
- Start processing — the adapter is pre-built and ready to use
Overview
MaxiPay payment integration
| Provider ID | maxipay |
| Category | Card Processors |
| Website | maxipay.com |
Configuration
Required Parameters
| Parameter | Description |
|---|---|
token | Bearer token for authorization API-requests |
service_id | service identifier (by default: P0117) |
Example Configuration
{
"provider": "maxipay",
"env": "prod",
"token": "your_bearer_token_here",
"service_id": "P0117",
"channel": "default_channel"
}
Payment Flow
Payouts (two-phase):
Phase 1 - verify (check):
- Payout eligibility check via
/check - Sending data:
- serviceId, account (masked number cards)
- agentTransactionId (numeric_id from UUID, 18 characters)
- agentTransactionDate (NaiveDateTime truncated to seconds)
- amountTo/amountFrom (formatted amount with decimal point: "123.45")
- extras.ev_account1 - encrypted number cards (RSA public key)
- With success (result = 0) → status
new
Phase 2 - commit (pay):
- Payout execution via
/pay - Uses the same parameters, as check
- With success (result = 0) → status
charged - With processing (result in [1, 153, 220, 255]) → status
charging
Status check:
- Uses the same endpoint
/pay(not separate status endpoint) - Returns current status operations
Status Mapping
| Provider Status | 4pay Status | Description |
|---|---|---|
0 | new | |
0 | charged | |
1 | charging | |
153 | charging | |
220 | charging | |
255 | charging |