Instructions for Internet acquiring OneVision V2

What the add-on does

The add-on adds the OneVision V2 payment processor to CS-Cart. It creates a payment in OneVision from order data, redirects the customer to the payment page, receives the payment result and updates the payment information in the order.

The add-on supports test and production modes, OneVision payment methods, mapping payment statuses to order statuses, and payment operations after the order is placed: capture of held funds, hold cancellation and refund.

Where to find the add-on

Payment parameters are configured in the CS-Cart payment method that uses the One Vision V2 processor: Administration → Payment methods, then open the required payment method and select the OneVision V2 processor.

Status mapping is available in the add-on settings: Add-ons → Manage add-ons → Internet acquiring OneVision V2 → Statuses. In a multi-storefront installation, select a storefront first; otherwise the mapping fields may be disabled.

Payment method settings

Fill in the general payment parameters:

Operation mode — select test or production mode. The selected mode defines which API key and store password are used for OneVision API requests.

API host — OneVision API address. The default value is https://api.onevisionpay.com. If the address is entered without a protocol, the add-on adds https://.

Merchant ID — merchant_id provided by OneVision. It is sent in order item and shipping item data.

Service ID — service_id of the category or service in OneVision.

Merchant name — the merchant name that owns the product or service.

Currency — payment currency: KZT, RUR, EUR or USD.

Payment lifetime — how long the payment remains available in OneVision. The interface offers values from 15 minutes to 7 days; the current payment request logic sends 3600 seconds.

Payment method — select the OneVision scenario: acquiring, mobile commerce, e-wallets, card and mobile balance transfers, Google Pay or Apple Pay.

API keys and store password

In the Test mode settings and Work mode settings blocks, fill in:

API key — OneVision API access key for the selected mode.

Secret key — the store password used to sign the request. The add-on creates an HMAC-SHA512 signature from the base64-encoded JSON request.

For test payments, select test mode and enter test credentials. For real payments, select production mode and enter production credentials.

Webhook and callback

The add-on sends a callback URL to OneVision in the format payment_notification.callback?payment=ms_one_vision_v2&order_id=<order ID>. It also uses success and failure return URLs: payment_notification.success and payment_notification.fail.

After a callback or customer return, the add-on requests the current payment status via payment/status, parses the OneVision response and saves the data to the order payment information.

Order statuses

On the Statuses tab, map OneVision statuses to CS-Cart order statuses. The add-on has two basic payment result statuses:

Success — the payment was successful; the default order status is O.

Rejected — the payment was rejected; the default order status is F.

If a OneVision status is mapped, the add-on uses the selected order status. If no mapping is configured, it uses the default value from the add-on schema.

Capture, cancel and refund operations

In the Payment action statuses block, select order statuses that trigger OneVision actions:

Capture request — sends payment/capture when the payment is in hold and the order is moved to the selected status.

Payment cancellation — sends payment/cancel to cancel a payment when funds are held but not captured.

Payment refund — sends payment/refund to refund an already captured payment.

For these operations, the add-on takes the payment ID and amount from the order payment information. After a successful OneVision response, the order payment information is updated.

Receipts and fiscalization

The add-on sends order items and shipping to OneVision as payment items, but the add-on code does not include separate fiscal receipt settings, 54-FZ attributes or DigitalKassa integration. If fiscal receipts are required for the store, check whether they are configured on the OneVision side or through a separate cash register solution.

Logging

The add-on writes technical logs for callback exchange and payment system responses to var/ms_data/logs/ms_one_vision_v2/<company_id>/ inside the CS-Cart installation. Main files are payment_1.log and payment_2.log; the add-on switches between them when the size limit is reached.

How to test

1. Create a payment method with the OneVision V2 processor and select test mode.

2. Enter the test API key, store password, API host, merchant_id, service_id, merchant name, currency and payment method.

3. Place a test order on the storefront and choose this payment method.

4. Check that the customer is redirected to the OneVision payment page.

5. Complete the test payment or simulate a rejection and check that the order receives the expected status.

6. Open the order in the admin panel and check the payment information: payment status, amount, payment ID, card data or error text.

7. If hold operations are used, move the order to statuses configured for capture, cancel or refund and check the OneVision response and payment information update.

8. If an error occurs, check credentials, API host availability, external callback URL availability and the add-on technical log.