Skip to content

Payment orchestration for Armenia

Your payment providers.
One integration.

One API, one hosted checkout, one dashboard and one webhook system on top of the banks and wallets you contract with. Money goes straight from your customers to your provider — OneGate never holds it.

# Create a payment

curl https://api.onegate.am/v1/payments \
  -H "Authorization: Bearer sk_test_…" \
  -H "Idempotency-Key: ORD-1001" \
  -d '{"amount":12500,"currency":"AMD","order_id":"ORD-1001","locale":"en"}'

# Response

{
  "id": "pay_06GCWGE55HZ397…",
  "status": "created",
  "amount": 12500,
  "currency": "AMD",
  "checkout_url": "https://pay.onegate.am/cs_…"
}
OneGate — Modern payment orchestration

One integration instead of many

Every Armenian bank and wallet has its own protocol, signatures, callbacks and edge cases. OneGate implements them once and gives you one consistent API, so adding a provider is a dashboard setting, not a new project.

How a payment flows

You create a payment through the API. Your customer pays on OneGate's hosted checkout and your provider's own page. The provider settles to your account; OneGate confirms the result and notifies you with a signed webhook.

  1. Your server creates a payment
  2. Customer chooses a method on the hosted checkout
  3. Customer pays on the provider's page
  4. Provider settles to your account
  5. You receive a signed webhook

Non-custodial: OneGate never holds, pools or pays out funds.

What you get

  • One API for every provider

    Create a payment once. Checkout offers only the methods your connected providers actually support.

  • Hosted checkout in three languages

    Mobile-first checkout in Armenian, English and Russian, hosted by OneGate. Card details are entered only on your acquirer's page.

  • Signed, retried webhooks

    HMAC-SHA256 signed events, retried up to 8 times over about six days, with delivery logs and manual resend.

  • Reconciliation built in

    Callbacks are not the only source of truth: OneGate asks supported providers about stuck payments and applies only valid state changes.

  • Safe refunds

    Idempotent refund API with over-refund protection. An uncertain provider response is confirmed with the provider, never retried blindly.

  • A real sandbox

    Simulate approvals, declines, timeouts, duplicate and out-of-order callbacks and refunds — without provider contracts or credentials.

Payment methods and their status

We only switch real-money processing on for a provider after OneGate's integration has been certified with that provider. Until then it works in test mode only.

  • OneGate Sandbox (simulated card and wallet payments)Available
  • Bank cards through your acquiring bankAwaiting provider certification
  • Idram walletAwaiting provider certification
  • Telcell WalletAwaiting provider certification
  • Arca QRPlanned
  • Apple Pay and Google PayPlanned
  • Cryptocurrency through a licensed processorPlanned
  • e-HDM fiscal receiptsTest mode onlyA receipt simulation is available in test mode. Issuing official e-HDM receipts requires an official integration that is not available yet.

Provider and product names belong to their owners. Listing an integration does not imply a partnership or endorsement: you use your own agreement with each provider.

Built for developers

A documented REST API with an OpenAPI 3.1 specification, idempotency keys, request IDs, cursor pagination, and SDKs for Node.js/TypeScript and PHP.

Open the developer documentation
  • Test and Live keys are separate; test payments never move money.
  • The webhook, not the return URL, confirms a payment.
  • Every response carries a request ID for support.

Security you can verify

We describe exactly what OneGate protects, what it stores and what it never touches.

Read how OneGate handles security
  • Non-custodial: funds go directly to your provider
  • Card numbers and CVV are entered on your acquirer's page, never on OneGate
  • Provider credentials are encrypted at rest
  • Every webhook is signed with HMAC-SHA256
  • Test and Live environments are fully separated

Frequently asked questions

Does OneGate hold my money?

No. Your customers pay your provider directly, and the provider settles to your account under your contract. OneGate does not hold, pool or pay out funds.

Do I need my own contracts with banks and wallets?

Yes. OneGate connects to the providers you contract with, using credentials you configure. You can start in test mode without any contract.

Which methods can take real payments today?

See the status list above. Real-money processing for each provider is switched on only after that provider has certified OneGate's integration.

Does OneGate see or store card numbers?

No. Customers enter card numbers and CVV on the acquiring bank's hosted page. OneGate receives only the payment result and references.

Can OneGate issue e-HDM fiscal receipts?

Not yet. Test mode includes a receipt simulation; official e-HDM issuance needs an official integration and authorisation that are still in progress.

How much does it cost?

Test mode is free. For live usage, write to info@onegate.am and we will share current pricing.

Start in test mode today

Create an account, get a test API key and make your first sandbox payment in minutes.

Create an account

Support and contact

Questions about integration, pricing or going live? Write to us. Include the request ID from any API response so we can help faster.

Email: info@onegate.am