Create Hutko adapter
In Settings → Developers → Adapters choose Hutko and save merchant credentials as JSON.
Hutko is connected as a workspace payment-status adapter. The CRM does not process cards or hold funds: Hutko handles the payment, then sends a signed server callback to Obriym CRM. The adapter validates the merchant id and SHA1 signature before writing any payment record.
Callback flow
The adapter is intentionally narrow: receive, verify, record, and update the order.
Signed callback
Hutko posts the payment result to the generated adapter endpoint.
Merchant check
The callback merchant_id must match the configured Hutko merchant.
Payment record
The CRM creates or updates crm_order_payments with status, amount, currency and provider payment id.
Order status
A paid callback can move a pending order to confirmed through the shared order payment flow.
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
- 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
- Connection test validates credential JSON and local signature verification without creating payment rows
Connection test scope
Hutko setup validation is a safe local credential and signature self-check. Live readiness is confirmed by Hutko delivering a real signed callback to the generated endpoint.
Setup
Copy callback URL
Use the generated server callback URL in Hutko merchant settings or your checkout integration.
Run validation
Use Test connection and sandbox validation before sending a real customer payment.
Frequently asked questions
Is this the same Hutko integration used for Obriym subscriptions?
No. This adapter is for a workspace's own orders and buyers. Obriym's own SaaS billing provider is a separate billing subsystem.
Will recurring payments be managed here?
This adapter records payment callbacks. Full subscription management for a workspace's customers should be added as a separate product flow only after the business contract with Hutko is explicit.
What if Hutko does not send buyer email?
The payment is still recorded. The adapter stores buyer email or phone only when the signed callback contains them.
Connect Hutko payment statuses
Let the payment provider confirm the result and keep order payment history consistent.
Start for free