Skip to content

Logo

Onevision

Supports in this guide: Payments, Payouts

Provider website: onevision.kz

Choose account type

  • H2H Merchant account -> card Payments (UZS, KZT, AZN, KGS)
  • Provider account -> card Payouts

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

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

Prerequisites: get from Onevision

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

  • API key -> Corefy field api_key.
  • Secret key -> Corefy field secret_key.
  • API URL -> Corefy field api_url.
  • Merchant ID -> Corefy field merchant_id.
  • Service ID -> Corefy field service_id.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API key
  • Secret key
  • API URL
  • Merchant ID
  • Service ID
  • Currency / Features -> choose values available for your account (UZS, KZT, AZN, KGS)
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Onevision H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0a4a417a-5774-4ca8-9a40-319b3636c4e7",
      "service": "payment_card_uzs_hpp",
      "currency": "UZS",
      "amount": 100000
    }
  }
}

Important

  • CVV is required for all currencies except UZS - for UZS, if CVV is missing, Corefy generates and sends a random 3-digit CVV to Onevision instead of leaving it empty.
  • No customer fields are sent to Onevision by this connector - only card data and your merchant profile's company name are included in the request.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "c22e66d5-48fa-41b0-b322-55a985204e50",
      "service": "payment_card_uzs_hpp",
      "currency": "UZS",
      "amount": 100000
    }
  }
}

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

  • ignore_callback -> optional, boolean - for cascading to work correctly, ignores Onevision's asynchronous callback and relies only on an active status request to finalize the payment.
  • custom_finalization_logic -> optional, boolean - changes how the first asynchronous callback is handled: instead of using it directly to finalize the payment, Corefy performs an active status request upon receiving it.

Refunds

Onevision supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Onevision in the provider directory and press Connect at Onevision Provider Overview page in the New connection section, then choose the Provider account option.

Step 2 - Fill in fields and select settings

  • API key
  • Secret key
  • API URL
  • Merchant ID
  • Service ID
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Onevision Provider account!

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "payment_card_uzs",
      "currency": "UZS",
      "amount": 100000,
      "fields": {
        "card_number": "4111111111111111",
        "card_holder": "John Doe"
      }
    }
  }
}

Important

  • fields.card_number and fields.card_holder are required for all Payout services.
  • No customer fields are sent to Onevision by this connector.
  • The exact set of Payout currencies/services available depends on the routes configured for your account.

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1b2c3d4-5e6f-4789-8a02-5b6c7d8e9f0a",
      "service": "payment_card_uzs",
      "currency": "UZS",
      "amount": 100000,
      "fields": {
        "card_number": "4111111111111111",
        "card_holder": "John Doe"
      }
    }
  }
}

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

  • generate_random_expire -> optional, boolean, payment_card_uzs service only - when the card's expiry date isn't the current month/next year, generates and sends a random expiry date to Onevision instead of the card's real one.

Additional info

  1. Active reconciliation is available on both Payments and Payouts - both the asynchronous callback and an active status request can finalize the transaction, unless ignore_callback is enabled on Payments.
  2. No recurring - this connector does not support saving/charging a token through Corefy.
  3. Payouts do not support refunds (refunds only apply to Payments).

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the API key, Secret key, API URL, Merchant ID, and Service ID for the selected environment (test_mode)
  • Payment declined for missing CVV -> required for all currencies except UZS, where a random CVV is generated automatically
  • Currency or service is not supported -> confirm allowed currencies/features in your Onevision account and in Corefy - Payments are available for UZS, KZT, AZN, KGS
  • Refund fails with multiple attempts -> only one refund per payment is allowed
  • Payout rejected for missing fields -> fields.card_number and fields.card_holder are required for every payout

Question

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