Русский
Українська
Հայերեն
ქართული
Қазақша
Español
Français
Deutsch
Italiano
فارسی
Article focus
The buyer goes straight to bank-hosted checkout
Version 0.2.5 removes the extra intermediary screen: after session creation, CS-Cart redirects the buyer to the hosted checkout URL issued by the bank.
The add-on targets CS-Cart and Multi-Vendor 4.14.1–4.20.1 according to its manifest. This is a declared compatibility range, not a claim that every intermediate build has passed separate certification. The exact licensed-store installation still needs a pilot.
For setup, an administrator creates a one-time setup token in VPOS.am Console and pastes it into the payment method. Merchant token, webhook secret and reconciliation secret are imported server-side; bank Client ID, username and password do not need to be stored or entered in the CMS.
- no extra intermediary page before bank-hosted checkout;
- stable link between order id, payment id, amount, currency and storefront;
- separate test and live bindings with no automatic live activation;
- add-on updates without re-entering bank secrets.
Order status changes only after server-side verification
The browser return explains the result to the buyer, but it is not payment evidence for CS-Cart.
VPOS.am sends a signed notification, and the add-on validates it and prevents duplicate processing. A webhook retry must not reduce stock again, change the order twice or send another email. If an event is missed, reconciliation queries the server-side status and restores the consistent state.
ArCa iPay and SmartVista EPG routes, including scenarios for Ameriabank, Evocabank, ACBA and other Armenian banks, are enabled only with the merchant agreement, bank-issued endpoint and credentials, and a completed pilot. Naming a bank describes the supported route architecture; it does not imply a partnership or automatic readiness of every terminal.
- signed webhook and duplicate-processing protection;
- payment id, order reference, amount and currency validation;
- reconciliation for missed or delayed notifications;
- separate states for success, decline, cancellation and refund.
What 0.2.5 includes and what needs separate integration
The add-on covers hosted checkout and verified order statuses without promising bank capabilities outside the current contract.
The current version does not initiate refunds from CS-Cart, execute recurring charges or split settlements among Multi-Vendor sellers. A confirmed provider refund status can be reflected in the order flow, but initiating the refund remains a separate banking or operational process.
Package 0.2.5 is prepared for controlled pilots and publication. On the announcement date, public package delivery in CS-Cart Marketplace is not active, so we do not publish a broken download link. Once the public listing opens, the integration page will carry it; until then, the VPOS.am team reviews connections by request.
- a bank agreement and valid test/production credentials are required before live;
- success, decline, cancellation, webhook retry and reconciliation are tested on the target store;
- refund initiation, recurring and split settlements are outside 0.2.5;
- production activation is performed separately for each merchant route.
FAQ
Which CS-Cart versions does the module support?
The manifest declares a target range of CS-Cart and Multi-Vendor 4.14.1–4.20.1. Before production, the exact version, PHP runtime, theme and installed add-ons must be checked on a licensed store.
Do I enter the bank password in CS-Cart?
No. CS-Cart receives a one-time setup token from VPOS.am Console. It imports the installation binding server-side, while bank credentials remain in the protected VPOS.am environment.
Can I download the module from CS-Cart Marketplace now?
Public package delivery is not active on the publication date, so we do not expose a Marketplace link yet. Use the integration page to request a pilot and receive the current release status.
Sources and documentation
- VPOS.am module for CS-Cart: capabilities and connection requirementsCurrent integration page, constraints and pilot path
- VPOS.am API DocsPayment lifecycle and server-side contracts
