Payment process
This is an old version of the API. Switch to the YooMoney API.
On the store’s website, you must show the payment form with the order data (in some cases, you can also show the form in the catalog of products and services on the YooMoney website).
There are two payment scenarios: choosing the payment method on the store’s website, or in YooMoney. How they differ:
| Choosing the payment method in YooMoney | Choosing the payment method in the online store |
|---|---|
Ranking options:
| The order for showing the payment methods is at the merchant’s discretion, and dynamic ranking is not available. |
| New payment methods are added automatically. | Any new payment methods are added to the payment form by the store. |
| This scenario will work if the store uses 3 or more payment methods. |
From the user’s viewpoint
The user chooses the payment method and goes to the confirmation page in the YooMoney service. If necessary, the user enters additional information and confirms the payment.
Here is an example of what the process looks like for a user paying with a bank card.
Scenario for choosing the payment method in YooMoney
- The user clicks the payment button (such as Pay in YooMoney on your website).
- The user goes to the YooMoney webpage and sees the available payment options. If this user has previously paid for something in your store or using YooMoney, the user’s preferred payment methods are shown. This might be the user’s bank card, YooMoney for Shopping wallet, or internet banking service. Other payment methods are available in a popup window.
- The user chooses a bank card that was used previously, and confirms the payment with passwords.
- When the bank has verified the payment, money is deducted from the card, and the user sees a page with payment information.
Scenario for choosing the payment method in the store
- The user chooses the bank card payment method on your website.
- The user then sees the page for entering information in YooMoney. During the payment process, the bank may request additional security (3‑D Secure). In this case, the user confirms the payment with a special password.
- When the bank has verified the payment, money is deducted from the card, and the user sees a page with payment information.
The page where the user enters the card information and confirms the payment belongs to YooMoney and is protected using the PCI DSS standard.
If the user chooses a different payment method, the payment scenario is slightly different. You can download instructions on the YooMoney website. These instructions describe all the available payment methods in detail.
From the merchant’s viewpoint
The main scenario is a payment using a YooMoney for Shopping wallet or a bank card. The flows for payments via Mir Pay, with cash, using external payment services (online banks and so on), or using a mobile terminal are described separately. They differ slightly from the main payment scenario.
If a store sends data for creating the receipts to its online sales register with our assistance, the payment scenario adds extra steps. See Sending details for the receipt
Payment process
HTTP protocol
Step 1. The user selects the payment method (on the store’s website or in YooMoney) and clicks Pay.
Step 2. The information that the user enters in the store’s interface is transmitted to YooMoney.
Step 3. The user ends up on the YooMoney payment data for the payment method and parameters they selected.
Step 4. The user enters additional information (i.e. logs in to their wallet or enters bank card data).
Step 5. YooMoney sends an Order verification request to the store’s information system.
Step 6. The merchant confirms the order’s validity, or refuses to process the payment.
Step 7. YooMoney sends the user a payment confirmation request. For wallet payments, the user must enter an SMS code; for bank card payments the user is sent to a 3‑D Secure authentication page (if the issuing bank supports it).
Step 8. The user confirms payment (enters the SMS code or passes the 3‑D Secure authentication process).
Step 9. If the merchant responds positively to the Order verification request, the money is debited.
Step 10. The user sees the result — a page with a message about successful payment, or a page with an error message.
Step 11. The results page displays a Back to store link. The user can click it to go to the page that you specified the address for in the settings.
Step 12. After successful payment, the merchant gets a Payment notification request.
Step 13. If the merchant responds positively to the Payment notification request, the payment is considered successful.
When a store gets the Order verification request, the order has not been paid yet. The user might not confirm the payment.
Email Protocol
Steps 1 through 4 and 7 are the same as when working with the HTTP protocol. Steps 5 and 6 are omitted.
Step 8. The money is debited.
Steps 9 and 10 are the same as when working with the HTTP protocol.
Step 10. After successful payment, you receive an email notification of payment.
See also