EasyPay.ua

EasyPay.ua: Merchant Payment Gateway Overview

EasyPay.ua provides online payment acceptance for merchants in Ukraine through a documented REST MerchantAPI and a hosted payment page. This overview summarizes how EasyPay.ua works for businesses, covering supported payment methods, integration models, security, and operational features.

What Is EasyPay.ua

EasyPay.ua is a Ukrainian online payments service with consumer products (bill pay, transfers) and a business offering for online payments. The company’s public website links “For business → Connect online payment” to the merchant environment at merch.easypay.ua. Footer badges indicate card security programs and PCI DSS presence, and the site references a MerchantAPI for programmatic integration.

Payment Methods And Instruments

EasyPay.ua exposes multiple “instrument types” that can be enabled per merchant service. The MerchantAPI documentation lists the following payment instruments:

• Card (bank cards) and RCard (a card saved in EasyPay)

• Apple Pay and Google Pay

• Emoney (EasyPay wallet; available when a user is authorized in EasyPay)

• Mobile money for Ukrainian operators: Kyivstar, Lifecell, Vodafone

• Fishka (loyalty card)

These are returned in API responses and can be managed via the payment methods section of the MerchantAPI.

Bank Cards (Card, RCard)

Card payments are supported via the Card instrument. RCard denotes a payment using a previously saved card in the EasyPay system. The API describes status handling (e.g., Accepted/Pending/Declined) and 3-D Secure outcomes.

Apple Pay

EasyPay.ua provides Apple Pay in two primary ways:

• Hosted payment page: Apple Pay button is shown on EasyPay’s payment page without extra integration.

• App or website tokenization: merchants can obtain Apple Pay payment data and pass it to EasyPay in the userPaymentInstrument token when creating an order. Documentation outlines Apple Pay requirements, merchant ID registration, certificate exchange (CSR), domain verification, and references to Apple’s developer materials.

Google Pay

Google Pay is supported on the hosted payment page and via merchant-side tokenization. For tokenization, use tokenizationType: PAYMENT_GATEWAY with gateway: easypay and pass the gatewayMerchantId issued by Google; the resulting token is submitted in the MerchantAPI call.

EasyPay Wallet And Mobile Money

The Emoney instrument allows payment from the EasyPay wallet for authorized users. The API also describes mobile money instruments for Kyivstar, Lifecell, and Vodafone, which can appear in the instrument set for a user.

Loyalty: Fishka

The Fishka loyalty card can be used as an instrument per the “Possible payment instruments” section.

Integration Models

Hosted Payment Page

Merchants can redirect to EasyPay’s payment page and receive results via redirects and server notifications (callbacks). Success and fail URLs are set when an order is created; EasyPay also has a “back” URL option visible to the user on the final page. The documentation cautions that redirects alone are not a reliable indicator of success; merchants should rely on server notifications or status checks.

Direct API (MerchantAPI)

EasyPay.ua’s REST MerchantAPI underpins order creation and status handling. Key endpoints and concepts include:

• CreateApp / CreatePage: establish an AppId and PageId to start a session.

• CreateOrder: create an order (with or without passing a payment instrument token).

• OrderState: poll for final status when needed. The base production URL is https://merchantapi.easypay.ua. The API requires specific headers and a calculated Sign.

Request Signing

Requests are signed with Sign = base64(sha256(secretKey + requestBody)). Code snippets are provided in the docs.

Security And Compliance

PCI DSS

EasyPay states that payment acceptance security is guaranteed by certification to PCI DSS v3.2.1, and provides a link to verify the current certificate.

3-D Secure (2.x)

Because acquiring banks have moved to 3-D Secure 2.x, EasyPay requires passing device and browser parameters when a payment instrument is submitted in the order request (e.g., card, Apple Pay, Google Pay). The API defines the 3DS flow, action types such as FormRedirect and UrlRedirect, and status semantics (Need3Ds, WaitVerify, Done).

Tokenization And Saved Cards

EasyPay supports card tokenization and saved-card usage. Two approaches exist:

• Merchant handles raw PAN (server-to-server): prohibited unless the merchant is PCI DSS certified.

• EasyPay-hosted tokenization page: the cardholder enters card data on EasyPay’s page, so merchant PCI DSS certification is not required for tokenization.

Callbacks return a cardGuid (token) and associated masked PAN/expiry, and there are endpoints to list and delete tokens. The docs also describe operationType options for token reuse (e.g., SingleToken).

Conclusion

EasyPay.ua offers a documented MerchantAPI and hosted payment page that support bank cards, Apple Pay, Google Pay, an EasyPay wallet, mobile money from major Ukrainian operators, and a Fishka loyalty instrument. The platform implements PCI DSS controls and modern 3-D Secure 2.x flows, provides tokenization to enable saved cards and PCI-minimizing setups, and exposes operations for authorization/capture, refunds, recurring payments, split transactions, and card payouts. Merchants integrate by establishing an App/Page session, creating orders with appropriate instruments, and handling callbacks and status polling for reliable reconciliation. For compliance and integration specifics, especially wallets, tokenization options, and payouts refer to the MerchantAPI and the PCI DSS page