MODx payment gateway Armenia: external checkout, payment links, vPOS

Overview

MODx payment scenarios through VPOS.am: external checkout, payment links, payment forms, provider status check, webhooks, logs and CRM/ERP sync.

What VPOS.am connects

For MODx, external checkout or a server-side form handler is usually safest. The site sends the order to VPOS.am, and the final status returns through backend flow.

Bank vPOS, ArCa/Visa/Mastercard and Idram/Telcell can be connected when provider credentials and the scenario are suitable.

payment session or payment link creation
storage of order id, payment id and provider reference
amount, currency and terminal status verification before changing the order

Payment flow and capabilities

Typical flow: the site or backend creates an order, VPOS.am creates a payment attempt, the customer moves to hosted checkout or wallet flow, then the result is confirmed by callback, status lookup or reconciliation.

After confirmation, the event can be delivered to CMS, CRM, ERP, fiscal queue, notifications or an internal dashboard. Repeated webhooks and retries are handled idempotently.

created, pending, paid, failed, canceled, refunded and manual review statuses
callback/status lookup, signed events and audit trail
refund/void workflow only when provider and contract support it

Mandatory website requirements for VPOS

Before production approval, a bank or payment provider usually checks not only the technical checkout but also the public information on the merchant website. It is safer to prepare these items before the application review.

If the website has several languages, the same required information should be available in every language. For Armenia, the Armenian version is mandatory even when Russian, English or another language is also present.

Privacy policy and personal data processing policy
Cancellation and refund policy, including a clear statement when the product or service is non-refundable
Terms and Conditions: sale, delivery or service provision terms
Prices for goods or services before payment
Contact details: phone, e-mail, messengers or another working contact channel
Armenian website version is mandatory; if other languages exist, the same information is duplicated there

Who it fits and boundaries

Fits: MODx service and catalog sites; payment and prepayment forms; projects without a full e-commerce checkout.

VPOS.am is not a bank or acquirer. Fees, payment method availability, settlement timing, website requirements, Apple Pay, refunds and production credentials are confirmed separately with the bank or payment provider.

start with one provider and one business process
check legal pages, HTTPS, callback URLs and test payments
switch to production only after evidence and operator review

FAQ

What should be prepared before connecting VPOS?

Prepare an HTTPS website, public legal pages, prices, contacts, Armenian website version, selected bank or payment provider, test credentials, callback/return URLs and a clear order or service status map.

Can the integration go directly to production?

No. First verify test payment, callback/status lookup, declined payments, refund or cancel flow when the provider supports it, logs and manual review for disputed statuses.