Genesis Card
Quick Start
- Sign up at genesis.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
Genesis Card payment integration
| Provider ID | genesis_card |
| Category | Card Processors |
| Website | genesis.com |
Configuration
Required Parameters
| Parameter | Description |
|---|---|
merchant | merchant identifier |
api_key | API key for HMAC-SHA signatures |
currency | currency code (for example: RUB) |
callback_url | URL for callback notifications from provider |
Example Configuration
{
"env": "prod",
"merchant": "merchant123",
"api_key": "hmac_secret_key",
"currency": "RUB",
"callback_url": "https://api.merchant.com/callback"
}
Payment Flow
Payments (one-phase and two-phase):
One-phase:
- start_tx - payment creation via POST
/payment:- Sending data cards (pan, cvc2, exp_month, exp_year)
- customer_ip, amount, currency, success_url, fail_url, callback_url
- HMAC-SHA signature all parameters (alphabetical order)
- Retrieval transaction_id, status, optional 3DS parameters (pareq, md, term_url)
Two-phase:
- verify = one_phase (initiation payment)
- commit not implemented (used only verify)
Payouts (one-phase):
- start_tx - payout creation via POST
/payout:- Sending destination_card, beneficiary_first_name, beneficiary_last_name
- amount, currency, order_id
- HMAC-SHA signature payload
- RSA signature for X-Signature header (MD5 hash cards + amount + currency + order_id)
- Retrieval transaction_id and status
Status check:
- POST
/payment/statusor POST/payout/status - Parameters: merchant, order_id, timestamp
- HMAC-SHA signature parameters
- Refund status_code and status_text
Status Mapping
| Provider Status | 4pay Status | Description |
|---|---|---|
1 | charging | |
2 | charged | |
6 | rejected | |
-6 | failed |