Payment integration for EV charging apps in Armenia

How each provider is connected

Provider	How the driver pays	How the result is confirmed	Notes
Idram	Redirect to the Idram payment page	Idram calls the server twice: a pre-check of the order and amount, then the payment result with an MD5 checksum, which the server verifies	Idram has no status query, so unfinished payments are closed after a set time without crediting
Bank cards, IDBank (ArCa-compatible gateway)	Redirect to the bank’s card page	The server asks the gateway for the order status and amount instead of trusting the browser	The platform supports two-stage payments (hold, capture, release) for guest charging where the bank has enabled them for the merchant. On the EV Armenia network the card is charged at once and the unused part is refunded
Fastshift	Redirect to the Fastshift vPOS page	The webhook is only a hint: the server queries the gateway with its own key for the final status and amount	Whole drams only

Each integration needs your own merchant account and credentials from the provider. We do not issue them.

Scroll sideways to see the whole table

Safety rules we follow

• A payment is credited only after the provider’s server-to-server confirmation, never because a browser says so.
• Amounts are checked exactly. A mismatch rejects the callback.
• Signatures are compared in constant time. A forged callback cannot mark someone else’s payment as failed.
• You can restrict callbacks to the provider’s IP addresses.
• Sensitive values are masked in logs. Card data never touches your server, because cards are entered on the bank’s page.

Reconciliation: settling unclear payments

Networks fail at awkward moments: the driver closes the browser after paying, a webhook is lost, a bank answers late. A background reconciler polls pending payments on a schedule, credits those the provider confirms, expires those that never completed, and, where two-stage payments are enabled, releases or flags card holds that no session claimed. Windows differ by provider (24 hours by default for Idram and cards, 7 hours for Fastshift) and are configurable.

Wallet and ledger

Money moves through a double-entry ledger: top-ups, charges, refunds, promotional credit and corporate invoices are entries that must balance, so the finance screen can be reconciled with the provider’s statements. Guest charging, without registration, uses a prepayment with refund of the unused part or a prepayment with the remainder as credit; where the bank enables two-stage payments it can also use a card hold. The EV Armenia network itself does not use holds today.

The market in short

Idram runs the largest QR payment network in the country; in January 2026 WeChat Pay users became able to pay by scanning Idram QR codes. In June 2026 the two QR systems, IdramNet and ArcaQR, were reported to be working on interoperability. This is why local wallets matter for tourists and residents alike. Details for drivers: payment methods at EV Armenia.

Not supported yet

• Telcell. Needs a contract and the merchant API specification from Telcell.
• Apple Pay and Google Pay.
• Saved cards and automatic top-up. Built, off by default until the bank confirms recurring payments for the merchant.
• Fiscal receipts. Whether charging requires an e-CRM receipt is an open question; see licence, tax and e-CRM.

Write to us below and tell us which providers you already have contracts with; we will plan the connection around them.