Skip to content

Logo

Utorg

Buy Bitcoin with card

Supports in this guide: Payments, Payouts

Provider website: utorg.pro

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from Utorg)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Utorg

Contact your Utorg account manager to get your account verified and receive the following credentials.

  • Login -> Corefy field login.
  • SID -> Corefy field sid.
  • API key -> Corefy field api_key.

EUR and other currencies via several local payment methods (Skrill, Neteller, Paysafecard, Giropay, Przelewy24, BLIK, online banking) for Payments; Skrill and Neteller for Payouts.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Utorg in the provider directory and press Connect at Utorg Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • Login
  • SID
  • API key
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Utorg Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to Utorg's hosted checkout.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "73a29122-66b3-4c9e-99b1-f388d5eeae37",
      "service": "skrill_eur_hpp",
      "currency": "EUR",
      "amount": 5
    }
  }
}

Important

  • customer.email and customer.address.country are the only customer fields actually used by this connector - if missing from the request, they fall back to the EMAIL/COUNTRY Constants (see below).
  • For the Giropay service specifically, enabling the Send Apm data Option also sends customer.email/.first_name/.last_name (or their Constants) to Utorg before redirecting - this has no effect for any other service.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7de7eebc-8cd8-4292-89f1-9efa2cd964b1",
      "service": "skrill_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "75db6f2f-dd7a-4768-bfdd-770088dfd9be",
        "name": "John Wick",
        "email": "name@example.com",
        "address": {
          "country": "GB"
        }
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

  • is_send_apm_data -> optional, boolean - for the Giropay service only, sends customer.email/.first_name/.last_name to Utorg before the redirect instead of collecting them on Utorg's own page.

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

  • EMAIL -> customer.email
  • COUNTRY -> customer.address.country
  • FIRST_NAME -> customer.first_name (Giropay only, requires is_send_apm_data)
  • LAST_NAME -> customer.last_name (Giropay only, requires is_send_apm_data)

Refunds

Utorg does not support refunds.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds via the selected method's wallet.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "1755286386",
      "service": "skrill_eur",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "1234567890",
        "email": "name@example.com"
      },
      "fields": {
        "email": "name@example.com"
      }
    }
  }
}

Important

  • fields.email is required - it is the wallet identifier Utorg pays out to.
  • If customer.email is missing, it falls back to the EMAIL Constant (see below).

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Include optional fields required by your specific flow

Constants (fallback fields)

  • EMAIL -> customer.email

Refunds

Utorg does not support refunds.

Additional info

  1. Active reconciliation is available - both Payments and Payouts support an active status request in addition to the asynchronous callback.
  2. Callbacks are signature-verified - both payment and payout callbacks from Utorg are signed; Corefy verifies the signature using your connected account's api_key as the RSA public key. A callback with a missing or invalid signature is rejected.
  3. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Login, SID, and API key for the selected environment (test_mode)
  • Currency or service is not supported -> confirm allowed currencies/features in your Utorg account and in Corefy
  • Payout rejected for missing wallet -> fields.email is required for every payout service
  • Callback rejected as invalid signature -> verify the connected account's API key matches what Utorg has on file
  • Refund fails -> Utorg does not support refunds through Corefy

Question

Still looking for help connecting your Utorg account? Please contact our support team!