✕No card data
Cards are entered on a partner-hosted or partner-approved page. ArmaPay never receives card numbers, CVV or PIN.
✕No merchant funds
The partner settles to the merchant. ArmaPay does not hold or settle merchant money.
✕No self-approval
Live payments start only after partner approval and provisioning.
!Test mode today
Working prototype with simulated payments. No partner agreement signed yet.
1How a payment flows
Merchants deal with ArmaPay. Card details and money go straight to and from the licensed partner.
Parties
Merchant
Armenian business
- Website, app or subscription service
- Integrates once: API, hosted checkout, dashboard
- Its customer pays during checkout
ArmaPay
Developer & API layer
- API keys, payments API, hosted checkout
- Subscriptions, invoices, payment retries
- Signed webhooks, dashboard, reconciliation views
- Onboarding workspace: collects and forwards applications
No card data · no funds
Licensed partner
Acquirer / processor
- Approves merchants (underwriting)
- Card page; reusable card tokens where supported
- Authorization, clearing, network connectivity
- Settles funds to the merchant
Regulated functions
Payment rails
Card & local rails
- Cards: card networks · ArCa
- QR & wallets: ArcaQR · Idram · Telcell
⚠ QR/wallet provider agreements: to be agreed with licensed partner/CBA
Requests & status
Payment requests → · ← Status, callbacks & signed webhooks
Card details
Customer enters card
✕ Not via ArmaPay
Partner card page → card networks
Funds
Merchant's bank account
✕ Not via ArmaPay
Partner collects via the rails and settles to the merchant
2Who owns what
ArmaPay
Licensed partner
Shared
✓ Expected
⚠ To be agreed with licensed partner/CBA
3 of 8 owners expected · 5 of 8 to be agreed
| Function | Expected owner | ArmaPay does | Licensed partner does | Status |
|---|---|---|---|---|
| 1Merchant contracting | SharedPartner holds the acquiring agreement | Coordinates the merchant's acceptance of partner agreements inside onboarding and records it. | Acquiring agreement with the merchant. V1 assumption: signed directly with the merchant. | ⚠ To be agreed with licensed partner/CBADirect merchant–partner agreement or sponsored sub-merchant model; how far signing can be embedded in ArmaPay onboarding. |
| 2KYC / KYB | SharedArmaPay collects · partner decides | Collects the business data and documents the partner requires, in one flow; tracks review status. | Performs its required KYB/AML compliance checks and decides. | ⚠ To be agreed with licensed partner/CBAWhich KYB/AML data ArmaPay collects, which checks each side runs, whether the partner can rely on ArmaPay-collected data, hand-off channel. |
| 3Underwriting | Licensed partner | Submits the application and relays the decision. Does not approve merchants; live mode only after partner approval and provisioning. | Approves or declines each merchant. | ✓ ExpectedReserves, risk controls and ongoing transaction monitoring: to be agreed with licensed partner/CBA. |
| 4Transaction processing | Licensed partner | Creates payment requests, hosts checkout, routes to the partner, tracks status, sends signed webhooks. | Card page, authorization, clearing and card-network connectivity. | ✓ ExpectedWhich entity processes (acquirer or a separate processor) and 3-D Secure behavior: to be agreed with licensed partner/CBA. |
| 5Settlement | Licensed partner | Does not hold or settle merchant money. Shows payment status and reconciliation views. | Settles funds to the merchant's bank account. | ✓ ExpectedSettlement timing and settlement data for reconciliation: to be agreed with licensed partner/CBA. |
| 6Chargebacks / refunds | Refunds SharedChargebacks ⚠ To be agreed | Merchant requests refunds via the API; ArmaPay sends them to the partner and tracks the result. | Executes refunds where the payment method supports them. | ⚠ To be agreed with licensed partner/CBAWho handles chargebacks/disputes and carries liability; refund support and timing per payment method. |
| 7Recurring-payment credentials / tokens | Licensed partnerArmaPay holds a reference only | Stores only an opaque token reference; runs subscriptions, invoices and retries. | Captures the card and holds the reusable payment method; executes recurring charges. | ⚠ To be agreed with licensed partner/CBAWhether reusable tokens and off-session charges are offered; token storage/expiry and authentication rules. |
| 8Merchant support | ArmaPayFirst line · partner role open | First line: integration, API, checkout, dashboard and onboarding status. | Not yet defined. | ⚠ To be agreed with licensed partner/CBAPartner's support role, escalation path, when merchants contact the partner directly. |
Also to be agreed with licensed partner/CBA: how ArmaPay's role is classified. Until approved otherwise, V1 is designed as a software, onboarding, billing and payment-orchestration platform — not a bank, merchant of record, stored-value wallet, e-money issuer, custodian of merchant funds, independent card acquirer, unsponsored payment facilitator or settlement institution.