Yandex.Money API API for Apps

Transcription

1

2 .. Version 1.8 Document build date: This volume is a part of Yandex technical documentation. Yandex helpdesk site: Yandex LLC. All rights reserved. Copyright Disclaimer Yandex (and its applicable licensor) has exclusive rights for all results of intellectual activity and equated to them means of individualization, used for development, support, and usage of the service. It may include, but not limited to, computer programs (software), databases, images, texts, other works and inventions, utility models, trademarks, service marks, and commercial denominations. The copyright is protected under provision of Part 4 of the Russian Civil Code and international laws. You may use or its components only within credentials granted by the Terms of Use of or within an appropriate Agreement. Any infringements of exclusive rights of the copyright owner are punishable under civil, administrative or criminal Russian laws. Contact information Yandex LLC Phone: [email protected] Headquarters: 16 L'va Tolstogo St., Moscow, Russia

3 Contents... 4 Application authorization flow... 5 App registration... 7 Authorization Request... 7 Access token request... 9 Revoking a token Access token scope Protocol overview Request format Response format Data types Information about a user's account account-info method operation-history method operation-details method Payments from the Yandex.Money wallet request-payment method process-payment method incoming-transfer-accept method incoming-transfer-reject method Payments from bank cards without authorization instance-id method request-external-payment method process-external-payment method Notification of events Notification of incoming transfer Index... 60

4 4 The is a tool for using almost all of our service's functions. What you can do using the API: Accept payments both merchants and individual users. Money can be deducted from any bank card or Wallet. Get information about users check the balance and get the history and details of operations. Get HTTP notifications for automatically processing transfers. Perform direct debits. Made from the user's wallet by default, or from a bank card by agreement. How to get started 1. Register your app in the. 2. Read the documentation. 3. Add the new payment feature to the app. For a quick start, use our SDK PHP, Java, Android, ObjC, and ios. 4. Start accepting payments from bank cards or electronic wallets. About payments from bank cards The page where the user enters card data is on our side Yandex.Money has a PCI DSS certificate. How it works: 1. In your app, the user selects "bank card" as the payment method. 2. You send the user to the page for entering data (on our side). During the payment process, the bank may request additional confirmation (3-D Secure). In this case, we ask the user to enter the password. 3. After verification by the bank, you deduct the money, and the user returns to the app and sees a page with information about the payment. About payments from Wallets You only need to get the user's permission once to access the Wallet (standard OAuth). How it works: 1. The app requests the permissions you need. For example, to make recurring direct debits. 2. The user is sent to our site and confirms access for the app. 3. Everything is ready. You can deduct money and request data without the participation of the user. is used by AVITO.ru Mamba Xsolla Fotostrana Zen Money Any more questions? Send us at: [email protected]

5 5 Application authorization flow To begin working with a Yandex.Money user's account, an application must get authorized using the OAuth2 protocol, which makes authorization secure and convenient. With OAuth2 authorization, applications don't need to ask users for their Yandex login and password. Instead, a user grants permission for an application to access his account within the restrictions approved by the user. Application authorization in Yandex.Money conforms to the following specifications: The OAuth 2.0 Authorization Framework The OAuth 2.0 Authorization Framework: Bearer Token Usage Diagram illustrating how an application and a user interact with the Yandex.Money OAuth server: Developer steps 1. The developer registers the application in Yandex.Money. This is the Registration Request in the OAuth2 protocol. The Yandex.Money service issues the developer a client_id, which is a string type application ID. 2. The developer embeds this client_id in the application code, declaring it a constant. Then the application can be distributed using any method. The client_id remains constant during the entire application lifecycle.

6 6 How a user authorizes an application 1. The application initiates user authorization to access the user's account, by sending the Authorization Request to the Yandex.Money server. 2. Yandex.Money redirects the user to the Yandex.Money authentication page. 3. The user enters his login and password, reviews the list of requested permissions, and either approves or rejects the authorization request. 4. The application receives an Authorization Response in the form of an HTTP Redirect with either a temporary authorization code or an error code. 5. The application uses the temporary authorization code to get an access token (Access token request). 6. The response contains the permanent access_token. 7. The application informs the user of the authorization results. Verifying the application's authenticity using a secret word The Yandex.Money service provides an additional way to verify that the access token is coming from your application. To do this, when obtaining the access token (the /oauth/token call), the application passes a secret word (client_secret) that is only known to the application. Note: Security measures based on the secret word are effective only if the token request is sent from the application's server, bypassing the user's device or browser. Security requirements 1. All network interactions are transmitted only via HTTPS. 2. In order to prevent compromise of authorization data, the application must verify the validity of the server SSL certificate and abort the session immediately if validation fails. 3. Do not store the access token in unencrypted format, for example, as cookies. 4. Never use the access token in request parameters (GET, POST etc). 5. The secret word should never be transmitted through the user's device or browser. 6. The secret word should not be used in any requests other than the request to get a token.

7 7 App registration To register your application in Yandex.Money, follow these steps: 1. Go to the App registration page. To get access, you will need to enter your payment password. 2. Set the application parameters: description The name of your application, for example, "Mobile store". application_uri Link to the application's web page or the developer s web site. redirect_uri URI for returning the result of application authorization (see redirect_uri in the OAuth 2.0 Authorization Protocol). Use application authenticity verification Specify whether you want to use the secret word for verifying the authenticity of the application (see the description of client_secret in The OAuth 2.0 Authorization Framework). 3. Click the Confirm button. The App data page opens, where you will see the name of your application, its ID (client_id), and, if the corresponding option is selected, the secret word that was generated (client_secret). Caution! The application developer should never openly publish the application's client_id anywhere. Leaking the client_id might provoke "phishing attacks," where applications or sites are launched to get access tokens in your name. If this happens, Yandex.Money will assume that it is receiving requests from your application. To prevent this, you can use the secret word (client_secret), which is only known by the application developer. The application developer should ensure that the secret word (client_secret) is kept confidential. Authorization Request The application uses the OS browser to send an Authorization Request to the Yandex.Money server. Tip: To request a token, we recommend using the POST method (the equivalent of HTML "form submit"), and UTF-8 encoding. Request format: POST /oauth/authorize HTTP/1.1 Host: m.sp-money.yandex.ru (for mobile devices) or sp-money.yandex.ru (for all other devices) Content-Type: application/x-www-form-urlencoded Content-Length: <content-length> client_id=<client_id>&response_type=code &redirect_uri=<redirect_uri>&scope=<scope> Example of request parameters:

8 8 client_id= response_type=code redirect_uri= scope=account-info operation-history Request example: POST /oauth/authorize HTTP/1.1 Host: sp-money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 154 client_id= &response_type=code&redirect_uri=https%3a %2F%2Fclient%2Eexample%2Ecom%2Fcb&scope=account%2Dinfo%20operation%2Dhistory Request parameters: client_id string The client_id that was assigned to the application during registration. response_type string Constant value: code. redirect_uri string URI that the OAuth server sends the authorization result to. Must have a string value that exactly matches the redirect_uri parameter specified in the application registration data. Any additional parameters required for the application can be added at the end of the string. scope string A list of requested permissions. Items in the list are separated by a space. List items are case-sensitive. For the authorization request, the user is redirected to the Yandex.Money authorization page. The user enters his login and password, reviews the list of requested permissions and payment limits, and either approves or rejects the application's authorization request. The authorization result is returned as an HTTP 302 Redirect. The application must process the HTTP Redirect response. Attention! If a user repeats the application authorization with the same value for the client_id parameter, the previous authorization is canceled. HTTP Redirect callback parameters: code string Temporary token (authorization code); should be exchanged immediately for a permanent access token. Present if the user confirmed authorization of the application. error string Error code. Present if an error occurred or authorization was declined by the user. error_description string Additional text explanation of the error. Possible errors: Value of the error field System behavior

9 9 invalid_request invalid_scope unauthorized_client access_denied The request is missing required parameters, or parameters have unsupported or invalid values. The scope parameter is missing, or it has an invalid value or a contradiction in logic. The client_id value is invalid, or the application does not have rights to request authorization (for example, its client_id has been blocked by Yandex.Money). Authorization request was declined by the user. Example of the Yandex.Money response for successful authorization: Page with the error message text. Page with the error message text. Page with the error message text. Redirect to the application with the error code. HTTP/ Found Location: Response from Yandex.Money when authorization is declined: HTTP/ Found Location: Note: The temporary authorization code (the value from the code field in the response) must be immediately exchanged for an access token. The temporary code expires after one minute. The application must be able to receive and process the response from the Yandex.Money server and immediately exchange the temporary authorization code for the access token. If the application was not able to get a response from the server, or the temporary authorization code was lost or expired, the authorization process must be repeated. See also Access token request Revoking a token Application authorization flow App registration Access token request If authorization was completed successfully, the application should immediately exchange the temporary authorization code for an access token. To do this, a request containing the temporary authorization code must be sent to the Yandex.Money OAuth server. The request must be sent using the POST method. Request format: POST /oauth/token HTTP/1.1 Host: m.sp-money.yandex.ru (for mobile devices)or sp-money.yandex.ru (for all other devices) Content-Type: application/x-www-form-urlencoded Content-Length: <content-length> code=<code>&client_id=<client_id>&grant_type=authorization_code&redirect_uri=<re direct_uri> Request example without verifying authenticity:

10 10 POST /oauth/token HTTP/1.1 Host: sp-money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 145 code=i1wsrn1ub1ehfbb37&client_id= &grant_type=authoriz ation_code&redirect_uri=https%3a%2f%2fclient%2eexample%2ecom%2fcb Request example with authenticity verification using a secret word: POST /oauth/token HTTP/1.1 Host: sp-money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 179 code=i1wsrn1ub1ehfbb37&client_id= &grant_type=authoriz ation_code&redirect_uri=https%3a%2f%2fclient%2eexample%2ecom %2Fcb&client_secret=my_secret_word Request parameters: code string Temporary token (authorization code). client_id string The client_id that was assigned to the application during registration. grant_type string Constant value: authorization_code. redirect_uri string URI that the OAuth server sends the authorization result to. The value of this parameter must exactly match the redirect_uri value from the previous "authorize" call. client_secret string A secret word for verifying the application's authenticity. Specified if the service is registered with the option to verify authenticity. In response to the request, the Yandex.Money server returns access_token, which is a symmetric key for the application that authorizes operations using the user account. The token is returned in the format of a JSON document, which can contain one of the following fields (depending on the results): access_token string Access token. Present if successful. error string Error code. Present if an error occurred. Possible errors: Value of the error field invalid_request unauthorized_client invalid_grant Example response for successfully exchanging the temporary authorization code: The request is missing required parameters, or parameters have unsupported or invalid values. The client_id or client_secret value is invalid, or the application does not have rights to request authorization (for example, its client_id has been blocked by Yandex.Money). The access_token could not be issued. Either the temporary authorization code was not issued by Yandex.Money, or it has expired, or an access_token has already been issued for this temporary authorization code (a duplicate request for an access token using the same temporary authorization code).

11 11 HTTP/ OK Content-Type: application/json Content-Length: 102 Cache-Control: no-store "access_token":"slav32hkhjhkkefhkjghgsdcbndbjhfshdfhjdbfv...wfervnrjkg" Example of error response: HTTP/ Bad Request Content-Type: application/json Content-Length: 31 Cache-Control: no-store "error":"invalid_grant" Tip: The temporary authorization code can only be used once. If the application was not able to get a response from the server before the temporary authorization code expired, the entire authorization process must be repeated. Note: The access_token is a symmetric authorization key, so the application developer must secure it the token should be encrypted for storage, with access allowed only after the user authenticates within the application. For example, the token can be encrypted using the 3DES algorithm, where the encryption key is a 4-digit PIN code. Attention! The token is valid for three years. When the token expires, it is automatically revoked. See also Authorization Request Revoking a token Application authorization flow App registration Revoking a token The application can revoke an access token that was issued. This means that all permissions that were granted to this token will be revoked. Send a request to the Yandex.Money OAuth server with the HTTP Authorization header containing the token to be revoked. The request must be sent using the POST method. Request example:

12 12 POST /api/revoke HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF Content-Length: 0 In response, the Yandex.Money server returns one of the following HTTP codes: HTTP response code 200 OK The token was revoked successfully. 400 Bad Request HTTP request does not conform to protocol format. Possible reasons: the request can't be parsed; the HTTP Authorization header is missing or has an invalid value. 401 Unauthorized The specified token does not exist, or has already been revoked. Successful response example: HTTP/ OK Content-Length: 0 Example of error response: HTTP/ Bad Request Content-Length: 0 See also Authorization Request Access token request Application authorization flow App registration Access token scope When invoking a protocol operation, you must pass an access token that has the necessary permissions. The list of permissions is requested as the value of the scope parameter for an authorize call for OAuth2 authorization of the application by the user; permissions are separated by a space. The possible permissions are listed below: Permission account-info operation-history operation-details incoming-transfers payment payment-shop payment-p2p To get information about the account status (see the accountinfo method). To view the history of account operations (see the operationhistory method). To view details of a particular operation (see the operationdetails method). To accept/cancel incoming transfers with a secret code and held for pickup. To make payments to a particular merchant or transfer funds to a particular user account (see the request-payment and process-payment methods). To make payments to any merchant accessible via the API (see the request-payment and process-payment methods). To transfer funds to any accounts, phone numbers, or addresses of other users (see the request-payment and process-payment methods).

13 13 money-source Available payment methods (see the methods requestpayment and process-payment). For more information, see The money-source permission. Restriction: The following cannot be used simultaneously in "scope": payment-p2p permission and payment.to-account permission payment-shop permission and payment.to-pattern permission Tip: Some permissions require setting string values that may contain symbols that violate the scope syntax. For such symbols, use backslash escaping according to JSON format. For example: \" \\ Restrictions that apply to permissions Restrictions (limits) may be applied to the permissions granted. Limits are specified like this: permission_name.destination.limit Restrictions that can be applied to permissions: destination condition (the payment recipient) Applies to the permission: payment. Only one of the following conditions can be specified as a value: to-pattern(patternid) Restricts sending payments only using the specified patternid. to-account(to) Restricts transfers of funds only to the account of a specific user. For the recipient ID, you can use an account number, mobile phone number that is linked with the user's account, or the user's address. Limiting parameters: Parameter to The transfer recipient's account ID, phone number linked to the account, or . Mandatory parameter. Tip: Mobile phone number as the payee ID. If the user who is receiving the transfer has a mobile phone linked to the account, the linked phone number can be used as the payee ID instead of using the account number. The specified phone number must be in the format of the ITU-T E.164 Numbering plan of the international telephone service. For Russia, this is the full number starting from 7, without the '+' symbol. For example: Tip: format.

14 14 Acceptable ways of formatting addresses are described in Wikipedia. Keep in mind that addresses may contain symbols that violate the scope syntax, such as double quotes. For such symbols, use backslash escaping according to JSON format. For example: \" \\ Example for specifying the transfer recipient using an account number:.to-account("41001xxxxxxxx") Example for specifying the transfer recipient using a linked mobile phone number:.to-account(" ") Example of specifying the transfer recipient using .to-account("[email protected]") limit condition (payment limit) limit(duration,sum) Applies to these permissions: payment, payment-shop, payment-p2p. The limit is specified last. Format: limit(duration,sum) Limit to the total amount of payments over a period of time. limit(,sum) Delegation of rights to make a one-time payment for a fixed amount. Parameters: Parameter duration sum Value Period of time, in days. If omitted, payment can only be made once using the given permission. Total amount for all payments over the period in duration, in the currency used for the account. Tip: The limit condition can be used for delegating one-time payments. The expiration of the permission is the same as for the token. The user cannot change the payment amount. Restriction: In the context of a single scope, it is allowed to specify either only duration-restricted payments, or only one-time payments. Restriction: If scope is set for a one-time payment, then, in addition to the payment permission, only the moneysource and account-info permissions can be set; all other permissions are forbidden.

15 15 Restriction: Regardless of the value of the requested limits, payments can also be subject to restrictions set by Yandex.Money for various types of transactions. Example: payments restricted to 100 rubles, 50 kopecks per day, and the user can change the amount..limit(1,100.50) Example: one-time payment of 1000 rubles and the user cannot change the amount..limit(,1000) By default: limit(1,3000) 3000 rubles per day and the user can change the amount. The money-source permission Informs Yandex.Money which payment methods are supported by the application. Format: money-source(list_of_payment_methods) The requested method for making a payment: wallet Payments from a Yandex.Money account. cards With the user's bank cards that are linked to the account. Default: wallet. Restriction: Bank cards cannot be used for transferring funds to other users' accounts. Example of payment using both a linked bank card and an account: money-source("wallet","cards") Example of payment using only a linked bank card: money-source("cards") Example of payment using only an account: money-source("wallet") Examples of values for the scope parameter Permitted to view payment history: account-info operation-history operation-details Permitted to view the account balance and make payments to merchant 123 for up to 1000 rubles per week: account-info payment.to-pattern("123").limit(7,1000) Permitted to make transfers to account XXXX, but no more than 500 rubles over a two-week period: payment.to-account("xxxx").limit(14,500) Permitted to make a one-time transfer to the account linked to phone number ZZZ, in the amount of 500 rubles: payment.to-account("zzz","phone").limit(,500) Permitted to make payments from the linked bank card to merchant 123 up to a total of 1000 rubles per week: payment.to-pattern("123").limit(7,1000) money-source("wallet","cards")

16 16 Protocol overview Request format Response format Access token scope Data types Request format Requests are to be sent via HTTP 1.1 using SSL (HTTPS) to the following address: Requests are authorized in accordance with The OAuth 2.0 Authorization Framework: Bearer Token Usage. HTTP requests must have this header: Authorization: Bearer <access_token> Note: The token that is used must have the necessary permissions to execute the requested method with the specified set of parameters. Security requirements: 1. All network interactions are transmitted only via HTTPS. 2. The application should verify the validity of the server's SSL certificate. If the SSL certificate did not pass verification, the session must be aborted immediately to prevent compromising the authorization data. 3. Do not store the access token in unencrypted format, for example, as cookies. 4. Never use the access token in request parameters (GET, POST etc). Format for request parameters: Key/value pairs, packed as HTTP 1.1 POST request parameters. MIME type: application/x-www-form-urlencoded. Character encoding: UTF-8. Request example:

17 17 POST /api/request-payment HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Authorization: Bearer ABCDEF param1=value1&param2=value2&param3=value3 See also Response format Access token scope Data types Response format The response is a JSON document in UTF-8 encoding (see The application/json Media Type for JavaScript Object Notation (JSON) and the official JSON site). The contents depend on the request results. Successful response example: HTTP/ OK Content-Type: application/json Content-Length: 51 Expires: Thu, 01 Dec :00:00 GMT Cache-Control: no-cache "param1":"value1", "param2":"value2" The response has HTTP headers to forbid proxy servers and local browsers to cache the content. Tip: The response may contain extra fields not described in this protocol. The application is to ignore them. If authorization fails, the server responds with a 4xx HTTP code. Possible reasons for rejection: The request cannot be parsed. The request does not include the HTTP Authorization header. The Authorization header specifies a nonexistent, invalid or expired token. The token does not have permissions for the requested operation. The response contains the WWW-Authenticate header (in accordance with the standard The OAuth 2.0 Authorization Framework: Bearer Token Usage). When authorization of the request is denied, the following fields are present in the response: Field error error_description Codes for reasons for authorization refusal: Code of the reason for authorization refusal. Additional text description of the reason for refusal. HTTP response code Value of the error field 400 invalid_request HTTP request does not conform to protocol format. Unable to parse HTTP request, or the

18 18 Authorization header is missing or has an invalid value. 401 invalid_token Nonexistent, expired, or revoked token specified. 403 insufficient_scope The token does not have permissions for the requested operation. Response example for missing header: HTTP/ Bad Request WWW-Authenticate: Bearer error="invalid_request" Response example for expired token: HTTP/ Unauthorized WWW-Authenticate: Bearer error="invalid_token", error_description="the access token has expired" Response example for token without required permissions: HTTP/ Forbidden WWW-Authenticate: Bearer error="insufficient_scope", error_description="payment forbidden by application authorization parameters" If a technical error occurs, the server responds with the HTTP code 500 Internal Server Error. The application should repeat the request with the same parameters later. See also Request format Access token scope Data types Data types Type Corresponding JSON type string string Character string in UTF-8 encoding. amount number Amount. Fixed-point decimal number with 2-digit precision. boolean boolean Logical value, possible values are true or false. int number 32-bit signed integer number. long number 64-bit signed integer number. object object Embedded JSON object. array array Array of JSON objects. datetime string Timestamp value conforming to the specification RFC3339 in the format YYYY-MM-DDThh:mm:ss.fZZZZZ (see explanation below).

19 19 of the datetime format: YYYY Year, always 4 digits. MM Month, always 2 digits (01 for January, and so on). DD Day of the month, always 2 digits (from 01 to 31). T Uppercase letter "T". hh Hour, always 2 digits (24-hour format, from 00 to 23). mm Minute, always 2 digits (from 00 to 59). ss Second, always 2 digits (from 00 to 59). f Fraction of a second, from 1 to 6 digits; may be omitted, in which case the preceding dot separator (.) should be omitted as well. ZZZZZ Time Zone Offset, mandatory parameter. Can take the values: Z UTC, uppercase letter "Z". +hh:mm or -hh:mm UTC (GMT) offset (indicates that a local time is shown that is either ahead of or behind UTC by the specified number of hours and minutes). Example: T19:00: :00 7 p.m. on July 1, 2011 in the time zone Europe/ Moscow (UTC+04:00). See also Date and Time on the Internet: Timestamps Request format Response format Access token scope

20 20 Information about a user's account account-info method operation-history method operation-details method account-info method Getting information about the status of the user account. Required permissions: account-info Input parameters None Returns If successful, returns a JSON document containing the following: account string User's account number. balance amount User's account balance. currency string User's account currency code. Always 643 (ruble of the Russian Federation by the ISO 4217 standard). account_status string The user's status. Possible values: anonymous anonymous account named named account identified identified account account_type string User's account type. Possible values: personal user account in Yandex.Money professional professional business account in Yandex.Money avatar object Link to the user's avatar. If the user's avatar is not set, the parameter is omitted. balance_details object Detailed information about the balance. By default, this section is omitted. This section appears if there are now or ever have been: deferred deposits negative balance blocked funds Details. cards_linked array Information about bank cards linked to the account.

21 21 If the account does not have any cards linked to it, the parameter is omitted. If the account has at least one card linked to it, the parameter contains a list of information about the linked cards. services_additional array List of additional services that are enabled. link_alfabank if the "Bank Connection" service for Alfa- Click is enabled, the value "alfabank" is set in the user profile link_openbank if the "Bank Connection" service for Otkritie Bank is enabled, the value "open" is set in the user profile If none of the services are enabled, the parameter is omitted. Parameters for the avatar object: url string Link to the user's avatar. ts datetime Timestamp of the last change to the avatar. Parameters of the balance_details object: total amount Total account balance. available amount Amount available for payments. deposition_pending amount The amount of funds pending deposit. If there are no pending deposits, the parameter is omitted. blocked amount The amount of funds blocked by authorities. If there are no blocked funds, the parameter is omitted. debt amount The amount owed (the negative balance on the account). If the balance is positive, this parameter is omitted. Parameters for the cards_linked object: pan_fragment string Masked card number. type string Card type. May be omitted if unknown. Possible values: VISA MasterCard AmericanExpress JCB Request example: POST /api/account-info HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 0 Response example:

22 22 "account":" ", "balance": , "currency":"643", "account_status":"anonymous", "account_type":"personal", "avatar": "url":" normal", "ts":" t20:43: :00", "cards_linked":[ "pan_fragment":"510000******9999", "type" : "MasterCard" ], "services_additional":[ "link_alfabank" ] operation-history method This method allows viewing the full or partial history of operations in page mode. History records are displayed in reverse chronological order (from most recent to oldest). Required permissions: operation-history. Input parameters type string List of operation types to display (see the table). Types in the list are separated by a space. If omitted, all operations are displayed. label string Filtering payments by the label value. Payments are selected that have the specified value for the label parameter in the request-payment call. from datetime Output operations FROM a timestamp (operations that were later than or equal to the from value). If omitted, all operations are displayed. till datetime Output operations TO a timestamp (operations that were earlier than the till value). If omitted, all operations are displayed. start_record string If this parameter is present, displays all operations starting from the number start_record. Operations are numbered starting from 0 (see the note). records int Page size, number of history records in response. Accepted values: from 1 to 100; by default 30. details boolean Show operation details. By default, false. To display operation details, the operation-details permission is required. Operation types: Type deposition payment incoming-transfersunaccepted Deposits (income). Payments (expenditure). Unaccepted incoming P2P transfers of any type.

23 23 Tip: The logic used for filtering history records. History records are filtered by the conditions: type of operation payment label time period All the conditions are additive, meaning each condition adds further restriction. Rules for selecting data by time period: 1. If both the from and till conditions are set, records are selected for the time period equal to or greater than from and less than till. 2. If both the from and till conditions are set, records are selected for the time period equal to or greater than from and less than till. 3. If only the till condition is set, records are selected with a time less than till. 4. If both the from and till conditions are omitted, records are selected without time restrictions. If the operation history contains a large number of records, the list of operations is displayed in page mode. The first page of the history is displayed by default. If there are additional pages, the next_record parameter appears in the response (this parameter is omitted if there is only a single page). To display the next page of the history, repeat the request with the same parameters and add the start_record parameter, specifying the value from the next_record parameter of the previous response. To get a larger selection of records in the time period, form a request with the from and till conditions, get the first page of the history, then form requests for the subsequent pages of the history with the same values for the from and till parameters, as well as the start_record parameter with the value that was obtained from the next_record parameter in the response for the previous page of the history. Returns The method returns the following parameters: error string Error code. Present if an error occurred when executing the request. next_record string The number of the first history record on the next page. Present if there is another page in the history operations (see Notes). operations array List of operations. Operation parameters: operation_id string Operation ID. status string Status of the payment (transfer). Accepts the following values: success Payment completed successfully. refused Payment was declined by the recipient or canceled by the sender. in_progress Payment is not yet complete; the transfer has not been accepted by the recipient, or is waiting for the secret code to be entered. datetime datetime Operation timestamp (date and time).

24 24 title string Brief description of the operation (usually contains the merchant name or source of deposit). pattern_id string The ID of the pattern used for making the payment. Present only for payments. direction string Direction of financial transaction. Can take the values: in (income). out (expenditure). amount amount Operation amount. label string Payment label. Exists for incoming and outgoing transfers made by other Yandex.Money users that had the label parameter set for the requestpayment call. type string The type of operation. Possible types of operations: Type payment-shop outgoing-transfer deposition incoming-transfer incoming-transfer-protected Outgoing payment to a merchant Any type of outgoing P2P transfer Credit Incoming transfer or deferred transfer. The necessity of an incoming-transfer-accept/incomingtransfer-reject call is determined by the status=in_progress field. Incoming transfer with a secret code. The necessity of an incoming-transfer-accept/incomingtransfer-reject call is determined by the status=in_progress field. Tip: If the value of the details input parameter is set to true, the response will also contain operation-details output parameters for operations. Operation processing error codes: Code illegal_param_type illegal_param_start_record illegal_param_records illegal_param_label illegal_param_from illegal_param_till all other values Invalid value for the type parameter. Invalid value for the start_record parameter. Invalid value for the records parameter. Invalid value for the label parameter. Invalid value for the from parameter. Invalid value for the till parameter. Technical error; repeat the operation again later. Note: If the operation history contains a large number of records, the list of operations is displayed in page mode. The first page of the history is displayed by default. If there are additional pages, the next_record parameter appears in the response (this parameter is omitted if there is only a single page).

25 25 To display the next page of the history, repeat the request with the same parameters and add the start_record parameter, specifying the value from the next_record parameter of the previous response. Requesting complete history Example of requesting the complete history: POST /api/operation-history HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 9 records=3 Example request for the next pages of the payment history: POST /api/operation-history HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 40 type=payment&records=20&start_record=120 Example response for the complete history: "next_record" : "4", operations : [ "operation_id" : " ", "status" : "success", "pattern_id" : "2904", "direction" : "out", "amount" : , "datetime" : " T20:43: :00", "title" : "Payment for ADSL access to company XXX", "type" : "payment-shop", "operation_id" : " ", "status" : "success", "pattern_id" : "2901", "direction" : "out", "amount" : , "datetime" : " T20:43: :00", "title" : "Direct phone account top-up YYY", "type" : "payment-shop", "operation_id" : " ", "status" : "success", "direction" : "in", "amount" : , "datetime" : " T20:40: :00", "title" : "Bank ZZZ, deposit", "type" : "deposit" ] Example response with details on operations when paying a merchant:

26 26 "next_record" : "2", operations : [ "operation_id" : " ", "status" : "success", "pattern_id" : "2904", "direction" : "out", "amount" : , "datetime" : " T20:43: :00", "title" : "Payment for ADSL access to company XXX", "details" : "Prepayment of ADSL Internet access to company XXX\nCustomer account no.: \n /89\npayment amount: \nTransaction number: ", "type" : "payment-shop" ] Example response with details of the operation for an outgoing transfer to another user: "next_record" : "2", operations : [ "operation_id" : " ", "status" : "success", "pattern_id" : "p2p", "direction" : "out", "amount" : 50.25, "datetime" : " T20:43: :00", "title" : "Transfer to account ", "recipient" : " ", "recipient_type" : "account", "message" : "Buy donuts", "comment" : "Transfer to Yandex.Money user", "codepro" : false, "details" : "Recipient account:\n \namount: 50,00 rubles", "type" : "outgoing-transfer" ] Example response for invalid parameter: "error" : "illegal_param_type" operation-details method Provides detailed information about a particular operation from the history. Required permissions: operation-details. Input parameters operation_id string Operation ID. The value of the parameter should be set like the value of the operation_id parameter from the operation-history method response; if the buyer's account history is being requested, it should be like the payment_id value from the process-payment method response.

27 27 Returns The method returns the following parameters: error string Error code, present only if an error occurred. operation_id string Operation ID. The value of the parameter corresponds to either the value of the operation_id parameter from the operation-history response, or, if the buyer's account history is being requested, the value of the payment_id field from the process-payment response. status string Status of the payment (transfer). The parameter value matches the value of the status field in the response to the operation-history method. pattern_id string Payment Pattern ID. Present only for payments. direction string Direction of financial transaction. Can take the values: in (income). out (expenditure). amount amount Amount of the operation (amount deducted from the account). amount_due amount Amount to receive. Present for outgoing transfers to other users. fee amount Commission amount. Present for outgoing transfers to other users. datetime datetime Operation timestamp (date and time). title string Brief description of the operation (usually contains the merchant name or source of deposit). sender string Account number that funds were transferred from. Present for incoming transfers from other users. recipient string ID of the transfer recipient. Present for outgoing transfers to other users. recipient_type string Type of ID used for the transfer recipient. Present for outgoing transfers to other users. message string Message for the transfer recipient. Present for transfers from other users. comment string Comments on the transfer (for the sender). Present in the sender's transfer history. codepro boolean The transfer is protected by a secret code. Present for transfers from other users. protection_code string Secret code. Present for outgoing transfers to other users that have a secret code. expires datetime Date and time when the secret code expires. Present for incoming and outgoing transfers from/to other users that have a secret code. answer_datetime datetime Date and time when a transfer protected by a secret code was accepted or canceled. Present for incoming and outgoing transfers from/to other users that have a secret code. If the transfer has not yet been accepted or refused by the recipient, this field is omitted. label string Payment label. Exists for incoming and outgoing transfers made by other Yandex.Money users that had the label parameter set for the requestpayment call. details string Detailed payment description. String in any format that may contain any symbols or line feeds. type string The type of operation. For possible types of operations, see the description of the operation-history method. digital_goods object Data about a digital product (PIN codes and bonuses for games, itunes, XBox, etc). This field is present for a successful payment to merchants of digital goods. For a description of the format, see the section Digital goods. For outgoing transfers to other users, the ID type for the transfer recipient is present:

28 28 Code account phone If an error occurs, its code is returned: Code illegal_param_operation_id all other values Recipient's account number in Yandex.Money Recipient's linked mobile phone number Recipient's address Invalid value for the operation_id parameter. Technical error; call the method again later. Request example: POST /api/operation-details HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 20 operation_id= Response example for payment to a merchant: "operation_id" : " ", "status" : "success", "pattern_id" : "2904", "amount" : , "direction" : "out", "datetime" : " T20:43: :00", "title" : "Payment for ADSL access to My Provider Company", "details" : "Prepayment of ADSL Internet access to Company \"XYZ\"\nCustomer account no.: \n /89\npayment amount: \nTransaction number: ", "type" : "payment-shop" Example response for an outgoing transfer to another user: "operation_id" : " ", "status" : "success", "pattern_id" : "p2p", "direction" : "out", "amount" : 50.25, "datetime" : " T20:43: :00", "title" : "Transfer to account ", "recipient" : " ", "recipient_type" : "account", "message" : "Buy donuts", "comment" : "Transfer from Yandex.Money user", "codepro" : false, "details" : "Recipient account:\n \namount: 50,00 rubles", "type" : "payment-shop" Response example for nonexistent operation request: "error" : "illegal_param_operation_id"

29 29 Payments from the Yandex.Money wallet Payment flow in Yandex.Money: 1. Payments are processed based on the Payment Pattern with user parameters specified. Each merchant has its own set of user parameters. The application must show the user (buyer) a form requesting the payment parameters that are required by this merchant, such as the payment amount, phone number, contract number, and so on. 2. The application sends a payment request containing the Payment Pattern ID and the parameters entered by the user. The Yandex.Money server checks the payment parameters and verifies that payments can be made to the merchant, then returns the payment request ID and payment contract text. 3. The application shows the payment contract text to the buyer, and the buyer is to approve or reject the payment. 4. If the buyer confirmed the payment, the application sends a request to confirm payment specifying the ID of the request received earlier using the request-payment method. Note: 1. The funds are withdrawn from the buyer's account when the process-payment method is called. 2. If the process-payment call is repeated with the same parameters, the method returns the state of the previous call. 3. If the connection is lost or times out, or there are other network problems, the application must repeat the request with the same parameters. Possible types of payment: payment to a merchant transfer of funds to other users' accounts accepting incoming transfers (with a secret code or deferred transfers) refusing incoming transfers (with a secret code or deferred transfers) topping up a mobile phone account test payments for debugging your application request-payment method Creates a payment, checks parameters and verifies that the merchant can accept the payment, or that funds can be transferred to a Yandex.Money user account. Permissions required for making a payment to a merchant: payment.to-pattern (Payment Pattern) or paymentshop. Permissions required for transferring funds to the accounts of other users: payment.to-account ("payee ID," "ID type") or payment-p2p.

30 30 Arguments for making a payment to a merchant pattern_id string Payment Pattern ID. * string User parameters for the Payment Pattern that are required by the merchant. Arguments for transferring funds to the accounts of other users pattern_id string Constant value: p2p. to string ID of the transfer recipient (account number, phone number, or ). amount amount Amount to pay. amount_due amount Amount to receive. comment string Payment comment, displayed in the sender's history. message string Comments on the transfer (displayed to the recipient). label string Payment label. Optional parameter. codepro boolean The true value indicates that the transfer is protected by a secret code. Omitted by default (normal transfer). hold_for_pickup boolean Indicates that deferred transfer (sending a transfer and holding it until it can be credited) is allowed. If the parameter is present and is set to true, this is deferred transfer mode. expire_period int Number of days during which: a transfer recipient can enter the secret code and receive the transfer to the account a deferred transfer recipient can receive the transfer The parameter value must be between 1 and 365. Optional parameter. By default, 1. Tip: The transfer amount is credited to the recipient minus the transfer fee. The sender of the transfer can set only one of these parameters: amount payment amount that will be deducted from the sender's account amount_due received amount that will be credited to the recipient's account Tip: Any transfer can have a "payment label" assigned to it. A payment label is a type of ID that is assigned by the application. As a result, you can select transfers in the history using a certain label. For example, you can use a code or an item ID from your application as a payment label. Labels up to 64 symbols long are allowed. Label values are case-sensitive. Input parameters for mobile phone service payment pattern_id string Constant value: phone-topup.

31 31 phone-number string Phone number in ITU-T E.164 format: the full number, starting with 7. Only numbers from mobile service providers in Russia are supported. Example: amount amount Payment amount. A fee can be subtracted from this amount; the fee depends on the operator. Tip: The phone number in ITU-T E.164 format is a string of digits up to 15 symbols long representing the full international number of the user's phone, without the '+' sign. For example, the phone number +7(921) will be entered as: Test payment Use a test payment to check how your application works, without making real payments. In testing mode, you can make any type of payment by adding debugging parameters to the method parameters: test_payment boolean Indicates a test payment if the value of the field is true. test_card string Optional field. Indicates there is a test bank card if the value of the field is available. test_result string Desired result of the test payment; acceptable values: success Completed successfully. Error code from the table the method returns the specified error code. Other value the method returns the error illegal_params. Tip: The Yandex.Money server checks all the parameters of a method and can return an error if these parameters are invalid, regardless of the value of the test_result parameter. Returns The method returns the following parameters: status string Operation result code (see the table). error string Operation processing error code (additional description for the status field). Present only for errors. money_source object Payment methods available to the application (see Available payment methods). Present only on success. request_id string ID of the payment request. Present only on success. contract_amount amount The amount to deduct from the account, in the currency used on the payer's account. Present only on success.

32 32 balance amount Current balance on the user's account. Present if the following conditions are met: The method was executed successfully. The access token has the account-info permission. recipient_account_statu s string The user's status. Possible values: anonymous anonymous account named named account identified identified account recipient_account_type string User account type in Yandex.Money. This parameter is present if the method was successfully executed when transferring funds to another user account. protection_code string The secret code for this transfer. The parameter is present if the codepro=true input parameter was set. A string of 4 decimal digits that may include leading zeros. The parameter must be processed as a string. account_unblock_uri string The address to send the user to in order to unblock an account. This field is present if the account_blocked error occurred. ext_action_uri string The address to send the user to in order to complete necessary actions if the ext_action_required error occurs. Operation processing result codes: Code success refused Success. Payment refused; the reason is explained in the error field. Final state. If an error occurred while processing the transaction, the error code is returned: Code illegal_params illegal_param_label illegal_param_to illegal_param_amount illegal_param_amount_due illegal_param_comment illegal_param_message illegal_param_expire_period not_enough_funds payment_refused payee_not_found authorization_reject Required payment parameters are either missing or have invalid values. Invalid value for the label parameter. Invalid value for the to parameter. Invalid value for the amount parameter. Invalid value for the amount_due parameter. Invalid value for the comment parameter. Invalid value for the message parameter. Invalid value for the expire_period parameter. The payer's account does not have sufficient funds to make the payment. Additional funds should be credited to the account, and a new payment will need to be processed. The merchant refused to accept the payment (for example, the user tried to purchase an item that is not in stock). The transfer recipient was not found. The specified account does not exist, or a phone number or address was specified that is not linked to a user account or payee. Authorization of the payment was refused. Possible reasons: A transaction with the current parameters is forbidden for this user. The user did not accept the User Agreement for the Yandex.Money service.

33 33 Code limit_exceeded One of the operation limits was exceeded: For the total amount of operations for the access token granted. For the total amount of operations over a period of time for the access token granted. Yandex.Money restrictions for various types of operations. account_blocked ext_action_required The user's account has been blocked. In order to unblock the account, the user must be redirected to the address specified in the account_unblock_uri field. This type of payment cannot be made at this time. To be able to make these types of payments, the user must go to the page with the ext_action_uri address and follow the instructions on that page. This may be any of the following actions: entering identification data accepting the offer performing other actions according to the instructions all other values Technical error; repeat the operation again later. Note: When processing a payment, Yandex.Money normally connects to the merchant webserver, which is why the method response time may take up to 30 seconds. While the request-payment method is being processed, the application should display an informational message to the buyer, such as "waiting for a response from the merchant". Note: Successful execution of the request-payment method does not guarantee that the payment process will be completed successfully, since payment authorization is performed when calling the process-payment method. Available payment methods The money_source field in the response contains a list of methods available for making this payment. Each method contains a set of attributes. If none of the methods described below can be used for the payment, the money-source field will be empty. Possible payment methods: Code wallet cards Payment using funds on the user's account. Payment using bank cards that are linked to the account. Attributes of the method of payment from the user's account: Attribute Type allowed boolean Flag indicating whether this payment method is allowed by the user. Attributes of the method of payment with a bank card: Attribute Type allowed boolean Flag indicating whether this payment method is allowed by the user.

34 34 Attribute Type csc_required boolean Indicates whether the CVV2/CVC2 code is required for authorizing payment using a bank card. item object of the bank card linked to the account. Parameters for the bank card description: Attribute Type id string Identifier of the bank card linked to the account. It must be specified in the process-payment method in order to complete payment using the selected card. pan_fragment string A fragment of the bank card number. This field is only present for a linked bank card. May be omitted if unknown. type string Card type. May be omitted if unknown. Possible values: VISA MasterCard AmericanExpress JCB If the method is available for the given merchant and allowed by the user, the response will have the method name and the "allowed" flag set to "true". For example: "wallet": "allowed": true, "cards": "allowed": true, "csc_required": true, "items": [ "id": "card ", "pan_fragment": "5280****7918", "type": "MasterCard", "id": "card ", "pan_fragment": "4008****7919", "type": "Visa" ] If the method is available but is not allowed by the user, the response will have the method name and the "allowed" flag set to "false". For example: "wallet": "allowed": false, "cards": "allowed": false Tip: The application can request additional permissions for making payments. The request for additional permissions is made by repeating the request for user authorization of the application.

35 35 Transfer recipient data When a transfer to another user account is requested, the request-payment method returns the following fields: Code recipient_account_statu s recipient_account_type The user's status. Possible values: anonymous anonymous account named named account identified identified account Recipient's account type. Possible values: personal User account in Yandex.Money. professional Professional business account in Yandex.Money. Examples Request example for paying for mobile phone service: POST /api/request-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 61 pattern_id=phone-topup&phone-number= &amount= Request example for transferring funds to another user account: POST /api/request-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 234 pattern_id=p2p&to= &amount= &message=%d0%9d %D0%B0%D0%B7%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5%20%D0%BF%D0%BB %D0%B0%D1%82%D0%B5%D0%B6%D0%B0&comment=%D0%A1%D0%BE%D0%BE%D0%B1%D1%89%D0%B5%D0%BD %D0%B8%D0%B5%20%D0%BF%D0%BE%D0%BB%D1%83%D1%87%D0%B0%D1%82%D0%B5%D0%BB%D1%8E Request example for transferring funds to another user account using a linked phone number: POST /api/request-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 256 pattern_id=p2p&to= &identifier_type=phone&amount= &message=%d0%97%d0%b0+ %d0%b2%d0%ba%d1%83%d1%81%d0%bd%d1%8b%d0%b9+%d0%b1%d1%83%d0%b1%d0%bb%d0%b8%d0%ba&comment= %d0%ba%d1%83%d0%bf%d0%b8%d1%82%d0%b5+%d0%b1%d1%83%d0%b1%d0%bb%d0%b8%d0%ba%d0%b8! Successful payment response example: "status": "success", "wallet": "allowed": true, "cards": "allowed": true, "csc_required": true, "items": [ "id": "card ", "pan_fragment": "5280****7918", "type": "MasterCard",

36 36 "id": "card ", "pan_fragment": "4008****7919", "type": "Visa" ], "request_id": " ", "contract": "Payment for services to SuperPhone, number +7 9xx xxx xxxx, amount RUB", "balance": Response example for refusal: "status": "refused", "error": "payment_refused", "error_description": "Specified account number does not exist" See also process-payment method Access token scope process-payment method Confirms a payment that was created using the request-payment method. Specifies the method for making the payment. Input parameters request_id string Payment request ID assigned by Yandex.Money, copied from the requestpayment response. money_source string The requested method for making a payment: wallet using funds on the user's account ID linked to the card's account (value of the id field in the bank card description) Default: wallet csc string Card Security Code, the CVV2/CVC2 code of the user's linked bank card. This parameter should be set only if payment is being made using a linked bank card. ext_auth_success_ur i string Address of the page to return to when card payment has been successfully authorized using 3-D Secure technology. This parameter is specified if the application supports 3-D Secure authentication. It is a mandatory parameter when using 3-D Secure authentication. ext_auth_fail_uri string Address of the page to return to when authorization has been denied for card payment using 3-D Secure technology. This parameter is specified if the application supports 3-D Secure authentication. It is a mandatory parameter when using 3-D Secure authentication.

37 37 Test payment Use a test payment to check how your application works, without making real payments. In testing mode, you can make any type of payment by adding debugging parameters to the method parameters: test_payment boolean Indicates a test payment if the value of the field is true. test_card string Optional field. Indicates there is a test bank card if the value of the field is available. test_result string Desired result of the test payment; acceptable values: success Completed successfully. Error code from the table the method returns the specified error code. Other value the method returns the error authorization_reject Tip: The Yandex.Money server checks all the parameters of a method (regardless of the value of the test_result parameter) and can return an error if these parameters are invalid. Returns The method returns the following parameters: status string Operation result code (see the table). error string Operation processing error code (additional description for the status field). Present only for errors. payment_id string Processed payment ID. Present only on success. balance amount Balance left on the user account after processing the payment. Present only if the following conditions are met: The method was executed successfully. The access token has the account-info permission. invoice_id string The merchant's transaction number in Yandex.Money. Present when payment to the merchant has been completed successfully. payer string Payer's account number. Present when funds were successfully transferred to the account of another Yandex.Money user. payee string Account number of the user receiving the payment. Present when funds were successfully transferred to the account of another Yandex.Money user. credit_amount amount The payment amount received to the payee's account. Present when funds were successfully transferred to the account of another Yandex.Money user. account_unblock_uri string The address to send the user to in order to unblock an account. This field is present if the account_blocked error occurred hold_for_pickup_lin k string A link to the deferred transfer when sending it via Yandex.Mail. The field is present if the value is known. acs_uri string Address of the card-issuing bank's authentication page for 3-D Secure technology. This field is present if 3-D Secure authentication is required in order to complete a transaction using a bank card.

38 38 acs_params object Authentication parameters for 3-D Secure technology in the form of a name-value collection. This field is present if 3-D Secure authentication is required in order to complete a transaction using a bank card. next_retry long Recommended time interval to wait before repeating a request, in milliseconds. This field is present when status=in_progress digital_goods object Data about a digital product (PIN codes and bonuses for games, itunes, XBox, etc). This field is present for a successful payment to merchants of digital goods. Operation processing result codes: Code success refused in_progress Success (payment processed). Final state. Payment processing was refused. The reason for refusal is returned in the error field. Final state. Payment authorization was not completed. The application should repeat the request with the same parameters later. ext_auth_required In order to complete authorization of payment by card, additional authentication using 3- D Secure technology is required. all other values The payment status is unknown. The application should repeat the request with the same parameters later. If an error occurred while processing the transaction, the error code is returned: Code contract_not_found not_enough_funds limit_exceeded Invalid or non-existent request_id specified. The payer's account does not have sufficient funds to make the payment. Additional funds should be credited to the account, and a new payment will need to be processed. One of the operation limits was exceeded: For the total amount of operations for the access token granted. For the total amount of operations over a period of time for the access token granted. Yandex.Money restrictions for various types of operations. money_source_not_available illegal_param_csc payment_refused authorization_reject The requested payment method (money_source) is not available for this payment. The csc parameter has a missing or invalid value. For some reason, the merchant refused to accept the payment. Authorization of the payment was refused. Possible reasons: The bank card expired. The issuing bank refused to perform the transaction for the card. Exceeds the limit for this user. A transaction with the current parameters is forbidden for this user. The user did not accept the User Agreement for the Yandex.Money service. account_blocked illegal_param_ext_auth_succ ess_uri illegal_param_ext_auth_fail _uri The user's account has been blocked. In order to unblock the account, the user must be redirected to the address specified in the account_unblock_uri field. The ext_auth_success_uri parameter has a missing or invalid value. The ext_auth_fail_uri parameter has a missing or invalid value.

39 39 Code all other values Authorization of the payment was refused. The application should make a new payment request later. Note: The time required for processing a payment using a linked bank card (money_source=card) depends on how long it takes the card's issuing bank to handle the transaction. In addition, Yandex.Money may connect to the merchant's server, and the response time likewise affects the total time for authorizing the payment. If payment authorization continues for more than 1 minute, the process-payment method returns the results code of the in_progress operation. The application should repeat the process-payment method call with the same parameters once a minute, until the final response is received (status should have the value either success or refused). Caution! If no response was received, the payment status is unknown. It is just as likely that the payment was accepted as that it was refused. To determine the payment status, repeat the process-payment call with the same parameters. Tip: Conditions for processing a payment using a linked bank card: The user's Yandex.Money account has a bank card linked to it. The user granted permission for the application to use this bank card for payments. The payment is being made to a merchant. The merchant is able to accept payments using bank cards. Authorization of payment using a linked bank card with 3-D Secure technology If payment is being made using a bank card, additional 3-D Secure authentication may be required. Payment scenario with 3-D Secure authentication: request-payment is called with payment parameters process-payment is called with money-source=card, csc code, ext_auth_sucess_uri, and ext_auth_fail_uri process-payment returns status=ext_auth_required, acs_uri, and acs_params the application should open the browser and make a POST request to the acs_uri address that passes acs_params parameters as application/x-www-form-urlencoded, i.e. do the same as "HTML form submit" the client gets authenticated using methods specific to the card-issuing bank, and is sent by HTTP 302 Redirect to one of these addresses, depending on the result: ext_auth_sucess_uri or ext_auth_fail_uri the application should repeat the process-payment call, specifying only a single parameter, request_id process-payment returns status=success or refused.

40 40 Data about digital goods For a successful payment to a merchant of digital goods, the response contains the digital_goods field, which has a list of goods and a list of bonuses. Data about a digital product or bonus: merchantarticleid string Product identifier in the seller's system. Present only for products. serial string Serial number of the product (the open part of the PIN code, activation code, or login). secret string Secret for the digital product (the closed part of the PIN code, activation code, password, or download link). Example of digital goods: "digital_goods": "article":[ "merchantarticleid":" ", "serial":"eav ", "secret":"87actmdbsv", "merchantarticleid":" ", "serial":" ", "secret":"gjhkgjsuurtrghxchfhjkrwetuertrehtthh", "merchantarticleid":" ", "serial":" ", "secret":"77788sfs7fd89g89dfg77778dfgdjkert789" ], "bonus":[ "serial":"xxxx-xx-xx", "secret":" " ] Examples Request example for payment from a user's account: POST /api/process-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 18 request_id= Request example for payment with the user's linked bank card: POST /api/process-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 44 request_id= &money_source=card&csc=123 Response example if payment authorization was not completed: "status": "in_progress"

41 41 Request example for payment with a bank card by an application that supports 3-D Secure: POST /api/process-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 164 request_id= &money-source=card&csc=123&ext_auth_success_uri=http%3a%2f %2Fclient.example.com%2Fsuccess&ext_auth_fail_uri=http%3A%2F%2Fclient.example.com%2Ffail Request example when repeating the request for payment with a bank card by an application after passing 3-D Secure authentication: POST /api/process-payment HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 18 request_id= Response example for successful authorization of the payment: "status": "success", "payment_id": "2ABCDE ", "balance": Response example for refusal: "status": "refused", "error": "not_enough_funds" Response example if payment authorization was not completed: "status": "in_progress" Response example when 3-D Secure authentication is required. "status": "ext_auth_required", "acs_uri": " "acs_params": "MD":" F11492F4F2D0", "PaReq":"eJxVUl1T2zAQ/ CsZv8f6tCR7LmLSGiidJjAldMpTR7XVxAN2gmynSX59JeNAebu9O93u7QkuDvXzZG9dW22bWURiHE1sU2zLqlnPo ofv1vrffxpwg2dtfm+l3lknc9u2zm0nvtmlvvn9r7v5d/us/ukyt4b8tjibuigvxazicmesskmtwbmlhyw=" See also request-payment method Access token scope incoming-transfer-accept method Accepting incoming transfers with a secret code and deferred transfers. There is a limit on the number of attempts to accept an incoming transfer with a secret code. When the allowed number of attempts have been used up, the transfer is automatically rejected (the transfer is returned to the sender).

42 42 Required token permissions: incoming-transfers. Input parameters operation_id string Identifier of the operation; the value of the operation_id parameter in the response to the operation-history method. protection_code string Secret code. String of four decimal digits. Specified for an incoming transfer protected by a secret code. Omitted for deferred transfers. Returns The method returns the following parameters: status string Operation result code (see the table). error string Operation processing error code (additional description for the status field). Present only for errors. incoming-transferaccept int The remaining number of attempts to accept an incoming transfer that is protected by a secret code. Present only if the wrong secret code was entered. ext_action_uri string The address to send the user to in order to complete necessary actions if the ext_action_required error occurs. Operation processing result codes: Code success refused The incoming transfer was accepted successfully. Refusal to perform the operation. If an error occurred while processing the transaction, the error code is returned: Code illegal_param_protection_co de illegal_param_operation_id ext_action_required Omitted or has an invalid value for the protection_code parameter. Omitted or has an invalid value for the operation_id parameter. A transfer with this operation_id does not exist or has already been refused. Transfers cannot be accepted at this time. To be able to accept transfers, the user must go to the page with the ext_action_uri address and follow the instructions on that page. This may be any of the following actions: entering identification data accepting the offer performing other actions according to the instructions on the page Examples Accepting an incoming transfer protected by a secret code: POST /api/incoming-transfer-accept HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 41 operation_id= &protection_code=0123 Example response when successful:

43 43 "status":"success" Example response if an invalid secret code was entered: "status":"refused", "error":"illegal_param_protection_code", "protection_code_attempts_available":2 incoming-transfer-reject method Canceling incoming transfers with a secret code and deferred transfers. If the transfer is canceled, it is returned to the sender. Required token permissions: incoming-transfers. Input parameters operation_id string Identifier of the operation; the value of the operation_id parameter in the response to the operation-history method. Returns The method returns the following parameters: status string Operation result code (see the table). error string Operation processing error code (additional description for the status field). Present only for errors. Operation processing result codes: Code success refused The incoming transfer was refused successfully. Refusal to perform the operation. If an error occurred while processing the transaction, the error code is returned: Code illegal_param_operation_id Omitted or has an invalid value for the operation_id parameter. A transfer with this operation_id does not exist or has already been refused. Examples Request example: POST /api/incoming-transfer-reject HTTP/1.1 Host: money.yandex.ru Authorization: Bearer ABCDEF ABCDEF ABCDEF ABCDEF Content-Type: application/x-www-form-urlencoded Content-Length: 20 operation_id=

44 44 Example response when successful: "status":"success" Example response if an invalid secret code was entered: "status":"refused", "error":"illegal_param_operation_id"

45 45 Payments from bank cards without authorization General information The API is intended for: payment of goods and services using any bank card without user authorization in Yandex.Money saving information about bank cards for repeated payments without entering the complete card data usage on users' personal devices and embedding in various mobile apps The API allows you to: pay for goods and services in stores that are connected to Yandex.Money deposit funds to users' Yandex.Money accounts save information about one or more bank cards and use it for subsequent payments To get started: 1. Register your application and get a client_id (application identifier). 2. Connect to the system as a merchant. Usage scenarios Registering an instance of the application Before making the first payment, you need to register a copy of the application in Yandex.Money that is installed on a device and get an identifier for the instance of the application instance_id. To register an instance, call the instance-id method. What you should know about the identifier: it is only received once it is remembered in a secure location on the device (storing it on an SD card is not allowed; you should use KeyChain or SharedPreferences) it is passed as a parameter for all other functions it is deleted from the device when the application is deleted General payment scenario 1. Payments are processed based on the Payment Pattern with user parameters specified. Each merchant has its own set of these parameters, so the application must show the user a form requesting the information that is needed by a specific store. For example: the payment amount, phone number, contract number, and so on. 2. The application sends a payment request request-external-payment, which contains the Payment Pattern ID and the parameters entered by the user. The Yandex.Money server checks the payment parameters and returns the payment context ID (request_id). 3. If the user confirmed the payment, the application sends a request to make the payment (processexternal-payment) that specifies the payment context ID (request_id).

46 46 Note that the application may need a repeat call of the process-external-payment method. This method should be called until the payment process is complete. This may require additional user steps in WebView. Repeated calls are necessary if: bank card data must be entered on the Yandex.Money page in WebView the user must go to the issuing bank's page to confirm the transaction over 3-D Secure payment processing is not yet complete the internet connection was lost during the payment process Rules for payment processing: 1. Money is debited from the bank card when the process-external-payment method is called. 2. If the process-external-payment call is repeated, the method returns the state of the previous payment. 3. If the internet connection is lost, the server times out, or other network errors, the application should repeat the call with the same parameters. First payment

47 47 1. The application sends a payment request (request-external-payment), which contains the Payment Pattern ID and the user parameters. The Yandex.Money server checks the payment parameters and returns the payment context ID (request_id). 2. The application sends a request to make the payment (process-external-payment) that specifies the payment context ID (request_id). The Yandex.Money server responds with a request to open WebView at the link (status=ext_auth_required, acs_uri, acs_params). 3. The application opens WebView and goes to the acs_uri address. After this: 1. The user enters the bank card data on the Yandex.Money page. 2. If necessary, the user authenticates using 3-D Secure technology on the issuing bank's page. 3. The user returns to ext_auth_success_uri (if the bank card data was accepted for processing), or ext_auth_fail_uri (if the card data was refused by the payment gateway). 4. The application repeats process-external-payment calls until it gets the final payment status (success/ refused). 5. The application shows the user the payment result and asks permission to save the bank card data. 6. If the user agrees to save the card data, the application re-sends the process-external-payment request with the request_token=true parameter. After this: 1. The Yandex.Money server returns the bank card data and a token for repeated payments. 2. The application saves the bank card data and the token for repeated payments in a secure location on the device. Bank card data and token for repeated payments: are remembered in a secure location on the device (storing it on an SD card is not allowed; KeyChain and SharedPreferences are allowed) are deleted from the device when the application is deleted Payment with saved bank card data This type of payment may require authentication using 3-D Secure technology, depending on the issuing bank's policy and information about the user's device or a specific transaction.

48 48 Payment using saved bank card data without 3-D Secure authentication: 1. The application sends a payment request (request-external-payment), which contains the Payment Pattern ID and the user parameters. The Yandex.Money server checks the payment parameters and returns the payment context ID (request_id). 2. The application repeats payment requests (process-external-payment), specifying the payment context identifier (request_id), the token for repeated payments and the bank card's CVV2/CVC2 code until it gets the final payment status. Payment using saved bank card data with 3-D Secure authentication: 1. The application sends a payment request (request-external-payment), which contains the Payment Pattern ID and the user parameters. The Yandex.Money server checks the payment parameters and returns the payment context ID (request_id). 2. The application sends a payment requests (process-external-payment), specifying the payment context identifier (request_id), the token for repeated payments and the bank card's CVV2/CVC2 code. The Yandex.Money server responds with a request to open WebView at the link (status=ext_auth_required, acs_uri, acs_params). 3. The application opens WebView and goes to the acs_uri address. After this: 1. The user authenticates using 3-D Secure technology on the issuing bank's page. 2. The user returns to ext_auth_success_uri (if the transaction was accepted for processing) or ext_auth_fail_uri (if the transaction was refused). 4. The application repeats process-external-payment calls until it gets the final payment status (success/ refused).

49 49 List of methods instance-id request-external-payment process-external-payment instance-id method Registering an instance of the application. Request parameters: client_id string Application ID. Returns Response fields: status string Operation result code (see the table). error string Error code (explanation of the "status" field). Present only for errors (see the table). instance_id string Operation result code (see the table). Operation processing result codes: Code success refused Success. Refusal. The reason for refusal is returned in the error field. If an error occurred while processing the transaction, the error code is returned: Code illegal_param_client_id Invalid value for the client_id parameter (non-existing or blocked). The application cannot work with this client_id. Examples Request example: POST /api/instance-id HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 75 client_id= abcdef abcdef abcdef abcdef1 Example of a response document when successful: "status": "success", "instance_id": " ABCDEF ABCDEF ABCDEF ABCDEF1" Example of a response document for an error:

50 50 "status": "refused", "error": "illegal_param_client_id" See also Payments from bank cards without authorization request-external-payment method process-external-payment method request-external-payment method Creating a payment and checking its parameters. Request parameters for a payment to a merchant: pattern_id string Payment Pattern ID. instance_id string ID of the application instance. * * User parameters for the Payment Pattern ID that are specific to a particular merchant. Request parameters for making a deposit to a Yandex.Money user account: pattern_id string Constant value "p2p". instance_id string ID of the application instance. to string Account number to make the deposit to. amount amount Amount to deduct from the bank card (this amount minus the commission fee will be deposited to the account). amount_due amount Amount to deposit to the account (this amount plus the commission fee will be debited from the card). message string Comments on the deposit (displayed to the recipient). Note: Only one of the two fields may be set in the parameters: amount or amount_due. Returns Response fields: status string Operation result code (see the table). error string Error code (explanation of the "status" field). Present only for errors (see the table). request_id string Payment context ID. Present only on success. contract_amount amount Amount to debit from the bank card, in rubles. Present only on success. title string Payment title.

51 51 Operation processing result codes: Code success refused Success. Payment processing was refused. The reason for refusal is returned in the error field. Final state. If an error occurs, its code is returned: Code illegal_param_to illegal_param_amount illegal_param_amount_due illegal_param_message payee_not_found payment_refused illegal_params or any other value Invalid value for the to parameter. Invalid value for the amount parameter. Invalid value for the amount_due parameter. Invalid value for the message parameter. Recipient not found; the specified account does not exist. The merchant refused to accept the payment (for example, the user tried to pay for an item that is not in stock). Required payment parameters are either missing, have invalid values, or logically contradict each other. Examples Example of a request to make a payment: POST /api/request-external-payment HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 130 pattern_id=99999&instance_id= abcdef abcdef ABCDEF ABCDEF1&amount=100.00&merchantArticleId=123 Example of a request to make a deposit to an account: POST /api/request-external-payment HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 125 pattern_id=p2p&instance_id= abcdef abcdef ABCDEF ABCDEF1&to= &amount_due= Example of a response document when successful: "status": "success", "request_id": " f f ", "contract_amount": , "title": "Оплата услуг NNNN" Example of a response document for an error: "status": "refused", "error": "illegal_params" See also Payments from bank cards without authorization request-external-payment method process-external-payment method

52 52 process-external-payment method Making a payment. The application calls the method up until the final payment status is known (status=success/ refused). The recommended retry mode is determined by the "next_retry" response field (by default, 5 seconds). Request parameters Request parameters for: first payment or deposits repeated request after entering card data or authenticating using 3-D Secure request_id string Payment context ID obtained from the request-external-payment method response. instance_id string ID of the application instance. ext_auth_success_ur i string Address of the page to return to when the bank card was successfully authorized. ext_auth_fail_uri string Address of the page to return to when the bank card was refused authorization. request_token boolean If this parameter is present and has the value "true", the application requests a token for repeat payments. By default, the parameter is omitted (a token for repeat payments is not requested). Parameters for a repeated payment request using a token: without entering card data with a repeated request after authentication via 3-D Secure request_id string Payment context ID obtained from the request-external-payment method response. instance_id string ID of the application instance. ext_auth_success_ur i string Address of the page to return to when the bank card was successfully authorized. ext_auth_fail_uri string Address of the page to return to when the bank card was refused authorization. money_source_token string Token for repeated payments. csc string, 3 digits Card Security Code, CVV2/CVC2 code on the bank card. Returns Response fields: status string Operation result code (see the table). error string Error code (explanation of the "status" field). Present only for errors (see the table). acs_uri string Address of the authorization page. This field is present if authorization is needed in order to complete the transaction (entering card data or authentication via 3-D Secure).

53 53 acs_params object Authorization parameters as a collection of "name"-"value" pairs. This field is present if authorization is needed in order to complete the transaction (entering card data or authentication via 3-D Secure). money_source object Bank card data for repeated payments. This field is present if the request parameter request_token=true is set, the payment was completed successfully, and the server approved issuing a token for this operation. Note: If the server refused to issue a token, this field is omitted in the response. next_retry long The recommended length of time (in milliseconds) before repeating the request. This field is present when status=in_progress. invoice_id string The transaction number in Yandex.Money. Present when payment was successfully made to a merchant. Operation processing result codes: Code success refused in_progress ext_auth_required Payment processing completed successfully. Payment processing was refused. The reason for refusal is returned in the error field. Final state. Payment processing is not yet complete. The application should repeat the request with the same parameters after the amount of time in "next_retry" has passed. To complete payment processing using a bank card, additional authorization is needed (entering card data or verification via 3-D Secure). You should open WebView and use a POST request to send the client to the "acs_uri" address with the "acs_params" parameters. If an error occurred while processing the transaction, the error code is returned: Code illegal_param_request_id illegal_param_csc illegal_param_instance_id illegal_param_money_source_ token payment_refused authorization_reject Invalid value for request_id or missing context with the set request_id The csc parameter has a missing or invalid value. The instance_id parameter has a missing or invalid value. The money_source_token parameter has a missing or invalid value, the token was revoked or expired. The merchant refused to accept the payment (for example, the user tried to pay for an item that is not in stock). Authorization of the payment was refused. Possible reasons: the issuing bank refused to perform the transaction for the card transactions with the current parameters are forbidden for this user illegal_param_ext_auth_succ ess_uri illegal_param_ext_auth_fail _uri The ext_auth_success_uri parameter has a missing or invalid value. The ext_auth_fail_uri parameter has a missing or invalid value. Bank card data for repeated payments: type string Type of funding-source: payment-card bank card. payment_card_type string The type of card; may be omitted if unknown. Possible values: Visa, MasterCard, AmericanExpress, JCB. pan_fragment string Masked card number; the last four digits are visible. money_source_token string Generated token for repeated payments.

54 54 Examples Example of a request to make a payment: POST /api/process-external-payment HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 305 request_id= f f &instance_id= ABCDEF ABCDEF ABCDEF ABCDEF1&ext_auth_success_ur=yandexmoney app%3a%2f%2fsuccess&ext_auth_fail_uri=yandexmoneyapp%3a%2f%2ffail Example of a request to get a token: POST /api/process-external-payment HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 324 request_id= f f &instance_id= ABCDEF ABCDEF ABCDEF ABCDEF1&ext_auth_success_uri=yandexmoney app%3a%2f%2fsuccess&ext_auth_fail_uri=yandexmoneyapp%3a%2f%2ffail&request_token= true Example of a payment request with a token: POST /api/process-external-payment HTTP/1.1 Host: money.yandex.ru Content-Type: application/x-www-form-urlencoded Content-Length: 589 request_id= f f &instance_id= ABCDEF ABCDEF ABCDEF ABCDEF1&ext_auth_success_uri=yandexmoney app%3a%2f%2fsuccess&ext_auth_fail_uri=yandexmoneyapp%3a%2f%2ffail&money_source_t oken=b6ae719baf712404e08ef8a430b0f58cd8f2c592452ca5205f7e52b1fc72bd3d D60B4E75BD742F22E8120F0861ED99B69EC01C6194CF5D425C89598B959DE0E9EDB13AFD710CF 74ACE08DBFBE2A49F14F9792B32289CE2456EB50EF7DFE6D22E466D417ACD1BF8DE33B5C93BDA 9AAA8C4D693DCD2E9AA2A31A51C185&csc=123 Example of a response document for a successfully processed payment: "status": "success", "invoice_id": " " Example of a response document when additional authorization is requested (card data and/or 3-D Secure): "status": "ext_auth_required", "acs_uri": " "acs_params": "MD": " F11492F4F2D0", "PaReq": "ejxvul1t2zaq/cszv8f6tcr7lmlsgiidjjaldmptr7xvxa N2gmynSX59JeNAebu9O93u7QkuDvXzZG9dW22bWURiHE1sU2zLqlnPo ofv1vrffxpwg2dtfm+l3lknc9u2zm0nvtmlvvn9r7v5d/us/ukyt4b8 tjibuigvxazicmesskmtwbmlhyw=" Example of a response document if payment processing has not yet been completed: "status": "in_progress", "next_retry": "5000" Example of a response document if the payment was rejected: "status": "refused", "error": "payment_refused" Example of a response document when a token was successfully issued for repeated payments:

55 55 "status": "success", "invoice_id": " ", "money_source": "type": "payment-card", "payment_card_type": "VISA", "pan_fragment": "**** **** **** 0334", "money_source_token": "B6AE719BAF712404E08EF8A430B0F58CD8 F2C592452CA5205F7E52B1FC72BD3D D60B4E75BD742F22E8120F0861E D99B69EC01C6194CF5D425C89598B959DE0E9EDB13AFD710CF74ACE08DBFBE2A4 9F14F9792B32289CE2456EB50EF7DFE6D22E466D417ACD1BF8DE33B5C93BDA9AA A8C4D693DCD2E9AA2A31A51C185" Example of a response document when a token for repeated payments was not issued (refused): "status": "success", "invoice_id": " " See also Payments from bank cards without authorization instance-id method request-external-payment method

56 56 Notification of events The Yandex.Money service can send notification of incoming transfers from other users. You can set up notifications in account settings. By processing notifications, you can automate incoming transfer processing in your system. Notification of incoming transfer Notification of incoming transfer Notification is sent if: The user received a transfer from another Yandex.Money user. The user received funds via the multipurpose form, donation form, or button. Request format The notification is sent as an HTTP request to the address specified in the account settings, in the following format: POST method. Key/value pairs for each notification parameter, packed as HTTP 1.1 POST request parameters. MIME type: application/x-www-form-urlencoded. UTF-8 encoding. Yandex.Money makes three attempts to deliver the notification: immediately when the transfer is received, ten minutes later, and one hour later. We recommend using the HTTPS protocol to get notifications. Note that you cannot get the sender's contact information in notifications unless you are using this protocol. When using the HTTP protocol, contact data is not passed in notifications. If the notifications do not arrive, check your settings: make sure the correct server address is indicated, and your server is currently available (you can use the "Test" button). The record of the incoming transfer is saved in the wallet history. In this case, you can find a record of the incoming transfer in the History. Tip: We recommend using the HTTPS protocol to get notifications. Note that you cannot get the sender's contact information in notifications unless you are using this protocol. When using the HTTP protocol, contact data is not passed in notifications. Notification parameters HTTPS no notification_type string For transfers from a wallet p2p-incoming. For transfers from another card card-incoming. operation_id string Operation ID in the history of the account that is receiving the transfer.

57 57 HTTPS amount amount Operation amount. withdraw_amount amount The amount of money withdrawn from the sender's account. currency string User's account currency code. Always 643 (ruble of the Russian Federation conforming to ISO 4217). datetime datetime Transfer timestamp (date and time). sender string For transfers from a wallet, this is the sender's account number. For transfers from any other card, the parameter contains an empty string. codepro boolean For transfers from a wallet, the transfer has a protection code. For transfers from any other card, it is always false. yes label string Payment label. If the payment does not have a label, the parameter contains an empty string. sha1_hash string SHA-1 hash of notification parameters. test_notification boolean This flag means this is a test notification. By default, omitted. lastname firstname fathersname string string string Full name of the transfer's sender. If this information was not requested, these parameters contain an empty string. string address of the transfer's sender. If the address was not requested, this parameter contains an empty string. phone string Phone number of the transfer's sender. If the phone number was not requested, this parameter contains an empty string. city street building suite flat zip string string string string string string The address specified by the sender for delivery. If the address was not requested, these parameters contain an empty string. Response format A notification is considered delivered if the recipient responded to the request with an HTTP 200 OK code. Tip: To get the other payment parameters, including the "Payment comment", call operation-details and specify the operation_id parameter that you received in the notification. Verifying notification authenticity and integrity One of the notification parameters, sha1_hash, contains the SHA-1 hash function value from packing notification parameters together with the secret word.

58 58 Note: The secret word for verifying notification is like a secret shared between Yandex.Money and the application developer. This means that notifications can't be faked. You can get the secret word in the account settings. Always check the value of the sha1hash parameter. This is necessary to: Verify the integrity of the notification data. Make sure that the notification was sent by Yandex.Money. To check the integrity and authenticity of the notification, calculate the hash using the algorithm below. Compare the data obtained with the value of the sha1_hash parameter in the notification. 1. Create a UTF-8 string from the notification parameters (where notification_secret is the secret word for verifying notifications). String format: notification_type&operation_id&amount&currency&datetime&sender&codepro&notifi cation_secret&label Example of a parameter string: p2pincoming& &300.00&643& t09:00: :00&41001xxxxxxxx&false & ABCDEF & Example of a parameter string with a payment label: p2pincoming& &300.00&643& t09:00: :00&41001xxxxxxxx&false & ABCDEF &YM.label Calculate the value of the SHA-1 hash function from the resulting string. 3. Format the resulting value in HEX encoding. Example of a value calculated for the sha1_hash parameter: 090a8e7ebb6982a7ad76f4c0f0fa5665d741aafa Examples of parameters Notification for a transfer from a card with the sender's full name and address requested: operation_id = notification_type = p2p-incoming datetime = T16:31:28Z sha1_hash = 8693ddf402fe5dcc4c4744d466cabada c sender = codepro = false currency = 643 amount = 0.99 withdraw_amount = 1.00 label = lastname = Иванов

59 59 firstname = Иван fathersname = Иванович zip = city = street = building = suite = flat = phone = = [email protected] Example of the same notification when the HTTP protocol is used: operation_id = notification_type = p2p-incoming datetime = T16:31:28Z sha1_hash = 8693ddf402fe5dcc4c4744d466cabada c sender = codepro = false currency = 643 amount = 0.99 withdraw_amount = 1.00 label =

60 Index account-info 20 API 4 incoming-transfer-accept 41 incoming-transfer-reject 43 instance-id 49 OAuth 5 operation-details 26 operation-history 22 process-external-payment 51 process-payment 36 request-external-payment 50 request-payment 29 Yandex.Money 4

61