Concept Pay
Quick Start
- Sign up at conceptpay.ru 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
Concept Pay payment integration
| Provider ID | concept_pay |
| Category | Card Processors |
| Website | conceptpay.ru |
Configuration
Required Parameters
| Parameter | Description |
|---|---|
merchant_id | merchant identifier |
merchant_secret | secret key merchant for authentication |
Example Configuration
{
"env": "prod",
"merchant_id": "merchant_123",
"merchant_secret": "secret_key",
"method": "TEST",
"need_auth": false
}
Payment Flow
Payments (one-phase):
Standard flow (need_auth=false):
-
auth - authentication via POST
/auth:- merchant, secret
- Retrieval access_token
-
invoice - invoice creation via POST
/invoices:- order_id (transaction ID), amount, currency, email
- method (TEST or TESTP2P), api_mode="h2h"
- callback_url
- Retrieval transaction token
- For P2P: token already in data.transaction.token
-
pay_or_confirm:
- For cards (TEST): POST
/invoices/{token}/paywith card_data and browser_data- Processing 3DS: next_action.redirect → GET redirect
- Immediate status with absence 3DS
- For P2P (TESTP2P): POST
/transactions/{token}/confirm- Confirmation only without card_data
- For cards (TEST): POST
With need_auth=true:
- get_additional_params_for_auth - creation invoice and refund parameters
- process_operation - uses existing outertxid, only pay/confirm
Payouts (one-phase):
-
auth - authentication
-
create_payout - payout creation via POST
/payouts:- order_id, amount (in rubles, not kopecks!), currency
- method (card), method_params (card number)
- description, callback_url
- Retrieval payout token and status
-
status - status check via GET
/payouts/{token}:- Parsing data.status.code
Status Mapping
| Provider Status | 4pay Status | Description |
|---|---|---|
3 | new | |
4 | charging | |
5 | charging | |
6 | charged | |
7 | rejected | |
8 | rejected | |
9 | rejected |