Այս էջը հասանելի է միայն անգլերենով։ Կոդը, API դաշտերը և նույնացուցիչները չեն թարգմանվում։

Payment methods, wallets & crypto

Methods are capabilities of your provider connections.

Code	Category	Through
`CARD`	CARD	Your acquiring bank / ARCA hosted page
`IDRAM`	WALLET	Idram
`TELCELL`	WALLET	Telcell
`ARCA_QR`	QR	Arca QR
`APPLE_PAY`	WALLET	An acquirer that officially supports Apple Pay
`GOOGLE_PAY`	WALLET	An acquirer that officially supports Google Pay
`CRYPTO`	CRYPTO	A licensed, non-custodial crypto processor

Real provider adapters are enabled only after OneGate implements them from the provider's official documentation. Until then they are marked Docs required and never appear in checkout.

Apple Pay & Google Pay

Wallets are not standalone processors: they run on top of your acquirer. A wallet button appears only when:

your connection's provider supports the wallet,
the required configuration exists (e.g. Apple merchant identifier, Google Pay gateway parameters defined by the acquirer adapter),
the connection is active,
environment requirements are met (e.g. Apple Pay domain verification for live), and
the customer's browser/device can actually use the wallet.

Two integration models are supported: provider-hosted (the acquirer's page runs the wallet) and direct token (OneGate Checkout runs the official Apple Pay JS / Google Pay API and forwards the encrypted token to the acquirer). OneGate never stores wallet tokens or card data. Wallet certificates are envelope-encrypted like all credentials.

Crypto

Crypto is non-custodial: the processor quotes, issues an address and settles to your wallet or settlement account. OneGate never holds keys, seed phrases or balances.

Quotes are immutable

For a 25,000 AMD order OneGate stores the asset, network, decimals, the quoted amount in integer base units, the rate, its source, the quote id and expiry. Historical quotes are never recalculated.

Networks are always explicit

Checkout shows USDT — Tron (TRC-20), never just “USDT”, with the exact amount, address, QR code, any required memo, and a countdown.

Statuses

Processor state	Payment status
`awaiting_payment`	`pending`
`payment_detected / confirming`	`processing`
`completed`	`completed`
`underpaid`	`requires_action`
`overpaid`	`completed` (flagged for review)
`expired`	`expired`

A broadcast transaction is not a completed payment: the processor's confirmation policy decides.

Crypto payments are disabled by default in production (CRYPTO_PAYMENTS_ENABLED=false) and require a separate compliance approval per organization before live use. Refunds follow the processor's capabilities; otherwise: “Refund must be processed through the crypto provider.”