Create the Hutko adapter
In Settings → Developers → Adapters choose Hutko, enter the merchant ID and payment key in separate fields, then select Create.
The Hutko integration synchronizes your business payment results with Obriym CRM. Card data and funds stay with Hutko: after payment, the service sends a protected server message and the CRM validates the Merchant ID and SHA1 signature before recording anything.
How a payment is recorded
The CRM verifies Hutko's message, stores the payment, and shows immediately whether it was matched to an order.
Signed callback
Hutko posts the payment result to the unique URL generated for your integration.
Merchant check
The callback merchant_id must match the configured Hutko merchant.
Payment record
The CRM stores the settled amount and currency in the payment journal and never invents an order from payment alone.
Reconciliation
An existing fully covered order can move to Confirmed; an unmatched payment remains in the journal.
Technical contract
Configured in Settings → Developers → Adapters.
- CRM endpoint
- POST /api/v1/adapters/hutko/{configId}
- Credentials
- {"merchantId":"1703986","password":"..."}
- Signature
- SHA1 over sorted non-empty callback fields with merchant password
- Stored data
- order, payment status, amount, currency, provider ids, optional buyer email/phone
Security model
- Rejects callbacks for a different merchant_id
- Rejects unsigned or incorrectly signed payloads
- Does not store PAN, CVV or raw card tokens
- Redacts sensitive Hutko metadata before saving diagnostics
- An optional local check validates saved details and the signature without creating a payment
The CRM records the result; it does not control payment
The CRM receives created, processing, approved, declined, expired and reversed statuses and records the settled amount and currency. If order_id matches an existing order, the payment attaches to it; without a match, it stays under Commerce → Payments for reconciliation. The integration does not create orders or payment links, charge or refund funds, or store PAN, CVV or card tokens.
Setup
Paste the URL in the Hutko portal
For all merchant payments: Merchant settings → Payment settings → Server callback URL. For one link: Payment solutions → Payment links → Advanced features → Server callback URL. The link value overrides the merchant default.
Or pass the URL through the API
If your website or backend creates checkout, pass the generated URL as server_callback_url in every request.
Run a control payment
The local connection check is optional. To verify your own Hutko portal setup, pay with a new order_id and check Commerce → Payments; to attach to an existing order, pass its externalId.
Frequently asked questions
Is this the same Hutko integration used for Obriym subscriptions?
No. This integration is for your customers' payments. Obriym subscription billing is separate and never mixes with your payment journal.
Will recurring payments be managed here?
No. The integration only records payment results. Checkout, charges, refunds and recurring payments remain in Hutko.
What if Hutko does not send buyer email?
The payment is still recorded. Buyer email or phone is stored only when Hutko actually sends it; safe diagnostics show only whether those fields were present, never their values.
Does a callback create an order?
No. If order_id matches an existing order externalId, the payment attaches to it. Otherwise it is stored separately for reconciliation.
Where is the callback field in the Hutko portal?
Globally: Merchant settings → Payment settings → Server callback URL. For one payment link, open its Advanced features; the URL there overrides the merchant-level value.
Connect Hutko payment statuses
Record confirmed Hutko payments and reconcile them with orders without creating duplicates.
Start for free