Инструменты страницы



Request for receipt closure (closeOfdReceipt)

The request used for closing the receipt is closeOfdReceipt.

From July 1, 2019, owners of online cash registers must generate receipts for offset and refund of prepayment. The payment gateway allows you to register a second check (closing check) without creating a new order using a request closeOfdReceipt.

The request must contain either the orderNumber parameter or mdOrder parameter.

The content of the closing receipt depends on whether the order cart (orderBundle) has been passed

The cart was transferred The shopping cart will be transferred to the OFD in the form in which it was transferred to the gateway in the request to close the receipt.
The cart was not transferred

For a completed order

  • If the total amount is specified (amount parameter) and it matches the original order amount, then the cart from the order will be transferred to the OFD.
  • If the original order was registered without a cart or the order amount differs from the closing amount, a cart with one item set in the default settings will be sent to the OFD.
  • If the amount has not been transferred:
    • a cart was sent in the original order – the cart from the original order will be sent to the OFD;
    • in the original order, the cart was not transferred – a cart with one element set in the default settings will be sent to the OFD.

For a refund

Closing a check can only be done if a partial, not full refund has been made for the order.

  • Partial refund of a specific amount – to the OFD.
  • Partial refund for an item – the amount of the original item is recalculated and the modified cart is sent to the OFD.
  • A closing receipt can be sent multiple times for one order. There is no limit on the amount, that is, the amount indicated in the closing receipt may be less or greater than the order amount.
  • An exception is made for orders for which a refund has been made. For orders for which a refund was made, the closing of the check can only be done if the total of all refunds is less than the confirmed order amount (i.e., there was no full refund).

In this document, the following data type conventions are used when describing request and response parameters:

  • A<n> – a sequence of Latin letters of length <n>;
  • A..<n> – a sequence of Latin letters with a length not exceeding <n>;
  • N<n> – a sequence of digits of length <n>;
  • N..<n> – a sequence of digits with a length not exceeding <n>;
  • AN<n> – a sequence of Latin letters and numbers of fixed length <n>;
  • AN.. <n> – a sequence of Latin letters and numbers with a length not exceeding <n>;
  • ANS<n> – a sequence of Latin letters, numbers and characters of fixed length <n>
  • ANS.. <n> – a sequence of Latin letters, numbers and characters with a length not exceeding <n>;
  • UTC – date and time, in this case: the date must be passed without specifying the time zone, Moscow time, for the SOAP protocol, the standard encoding xs: dateTime is used.

Request parameters

The request parameters are given in table below.

Name Type Mandatory Description FFD version

mdOrder

ANS..36

Either mdOrder or merchantOrderNumber must be passed

Order number in the payment gateway. Unique within the payment gateway.

All versions.

merchantOrderNumber

ANS..32

Either mdOrder or merchantOrderNumber must be passed

Order identifier in the Store system.

All versions.

amount

N..12

No

Payment amount in minimum currency units.

All versions.

params

See column with the description.

No Currently not used

All versions.

additionalOfdParams

Data block for transferring additional parameters of the OFD

Yes

Some parameters of additionalOfdParams block duplicate parameters of cartItems.items.itemAttributes block. The additionalOfdParams block is included for all line items of the order, whereas cartItems.items.itemAttributes applies to individual items. If the additionalOfdParams and cartItems.items.itemAttributes and additionalOfdParams blocks pass different values, then the priority value will be the one that was passed in cartItems.items.itemAttributes, that is, for an individual position.

The transfer of this block is possible only when using the following OFDs:

  • ATOL;
  • Business.Ru;
  • Evotor.

(Go to description.)

orderBundle

Not applicable

Yes

Block containg the cart of items of the order. The description of the attributes is given below.

(Go to description.)

All versions.

orderBundle

orderBundle contains the following elements.

Name Type Mandatory Description FFD version

orderCreationDate

ANS..21

No

Order creation date in the format YYYY-MM-DDTHH:MM:SS.

All versions.

customerDetails

Not applicable

No

Block containing attributes with data about the customer. The description of the attributes is given below.

(Go to description.)

All versions.

cartItems

Not applicable

Yes

Block with the attributes of the items in the cart. The description of the attributes is given below.

(Go to description.)

All versions.

agent

array ANS..19

No Given below are the parameters of agent block.. (Go to description.)

All versions.

supplierPhones

array ANS..19

No

An array of supplier phone numbers in +N format.

All versions.

agent

Name Type Mandatory Description

agentType

N..2

Yes (if the block is present)

Agent type, the following values are available:

  • 1 – banking payment agent;
  • 2 – banking payment subagent;
  • 3 – payment agent;
  • 4 – paying subagent;
  • 5 – designated agent;
  • 6 – commercial agent;
  • 7 – other agent.

payingOperation

ANS..24

No

Name of the transaction of the paying agent.

payingPhones

array ANS..19

No

Phone numbers array of the payments agent in +N format.

paymentsOperatorPhones

array ANS..19

No

Array of phone numbers of the operator for receiving payments in the + N format.

MTOperatorPhones

array ANS..19

No

An array of Money Transfer operator phone numbers in +N format.

MTOperatorName

ANS..64

No

Money Transfer operator name.

MTOperatorAddress

ANS..256

No

Money Transfer operator address.

MTOperatorInn

N10..12

No

Money Transfer operator TIN.

customerDetails

customerDetails contains the following elements.

A parameter included in a block and indicated as mandatory is only mandatory within that block. If the section is optional and missing, then the parameters included in it should not be passed.

Name Type Mandatory Description FFD version

email

ANS..40

See note below.

Customer's email address. You can specify several comma separated (without spaces) email addresses – in this case the receipt will be delivered to all specified addresses.

All versions.

phone

NS..12

See note below.

Customer's phone number. It can be of the following format: ^((+7|7|8)?([0-9]){10})$. Examples:

  • +79000000000
  • 89000000000
  • 9000000000
  • 79000000000

If the number is passed in a separate parameter and in additional parameters, the number specified in this phone parameter will be used.

When using ATOL fiscalization, the phone parameter should be sent in the following format:

The phone number must be passed together with the country code without spaces and additional characters except for the quotation marks (the number «371 2 1234567» must be passed as «+37121234567»). If the phone number belongs to Russia (prefix «+7»), then the value can be passed without a prefix (the number «+79251234567» can be sent as «9251234567»). The maximum string length is 64 characters. One of the fields must be filled in the request: email or phone.

All versions.

contact

ANS..40

No

Customer's preferred way of communication.

All versions.

deliveryInfo

Not applicable

No

Block containing the attributes of the delivery address. The description of the attributes is given below.

(Go to description.)

All versions.

fullName

ANS..100

No

Payer's first name, last name, and patronymic.

1.05 and later versions.

passport

ANS..100

No

The series and number of the payer's passport in the following format: 2222888888.

1.05 and later versions.

inn

N..12

No

Taxpayer identification number. From 10 to 12 digits can be passed.

1.05 and later versions.

It is mandatory to pass one of the two parameters: email or phone.

deliveryInfo

deliveryInfo contains the following elements.

Name Type Mandatory Description FFD version

deliveryType

ANS..20

No

Delivery method.

All versions.

country

A..2

Yes

The two-letter country code for the delivery country.

All versions.

city

ANS..40

Yes

Delivery city.

All versions.

postAddress

ANS..255

Yes

Delivery address.

All versions.

A parameter included in a block and indicated as mandatory is only mandatory within that block. If the section is optional and missing, then the parameters included in it should not be passed.

cartItems

cartItems contains the following elements.

A parameter included in a block and indicated as mandatory is only mandatory within that block. If the section is optional and missing, then the parameters included in it should not be passed.

Name Type Mandatory Description FFD version

items

Not applicable

Yes

Tag containing the parameters with the data about one item from the cart .

Item number is specified as an attribute of the tag: positionId – Unique identifier of a product item inside the order cart.

A request must contain a separate items tag for each line item. The description of the tag parameters is given below.

(Go to description.)

All versions.

items

items« contains the following elements.

Name Type Mandatory Description FFD version

positionId

ANS..12

Yes

Unique identifier of a line item within the order cart.

All versions.

Name

name

Type

ANS..100

Description

REST

Name or the description of an item in any format.

Use
- to pass \ use \«- to pass »

REST Online Lending

For Online Lending functionality, it's necessary to specify a description of the line item in accordance with the Yandex.Market catalog, subject to the following requirements:

  • The following words and character sequences are not allowed: file, exec, insert, as, select, or, procedure, limit, order, and, or, by, asc, desc, delete, update, distinct, having, truncate, replace, handler, like, regex, tz_offset, to_timestamp_tz, bfilename, union, sql-command, abort, alter, analyze, begin, audit, checkpoint, close, cluster, comment, commit, copy, create, deallocate, declare, delete, drop, end, execute, explain, fetch, grant, insert, lock, move, noaudit, notify, prepare, reindex, rename, reset, revoke, rollback, savepoint, select, set, show, shutdown, start, truncate, unlisten, update, vacuum
  • The following special characters are not allowed: ' & – # % | ; =
WS

Name or the description of an item in any format.

Use
- to pass \ use \«- to pass »

WS Online Lending

For online crediting functionality it's necessary to specify a description of the good item in accordance with the Yandex.Market.

ANS..100

Yes

Name or the description of an item in any format.

Use
- to pass \ use \«- to pass »

All versions.

itemDetails

Not applicable

No

Additional block containing the parameters describing a line item. The description of the attributes is given below.

The field size limit is 1024 bytes.

(Go to description.)

All versions.

quantity

N..18

Yes

Element describing the total of items of one positionId and its unit of measurement The description of the attributes is given below.

(Go to description.)

All versions.

itemAmount

N..12

No

The sum of the cost of all line items of one positionId in minimum currency units. Passing itemAmount is mandatory only if the itemPrice parameter was not passed. Otherwise passing of itemAmount is not required. If both parameters – itemPrice and itemAmount – are passed. then itemAmount must be equal to itemPrice * quantity, otherwise, the request will result in an error.

When calculating itemAmount = itemPrice*quantity parameter, the result is rounded up to the second digit after the decimal point. For example, if the calculation result is 100.255, then final value will be 100.26.

All versions.

itemCurrency

N3

No

Currency code of a line item according to ISO 4217. If the parameter is not specified, it is considered to be equal to the order currency.

All versions.

itemCode

ANS..100

Yes

Number (identifier) of a line item in the store system.

All versions.

tax

Not applicable

Only for stores with enabled fiscalization settings

An additional tag with attributes describing the tax. Nested tags are described below.

(Go to description.)

All versions.

itemPrice

N..18

Only for stores with enabled fiscalization settings

The price of one line item of one positionId specified in minimum currency units. Mandatory for merchants using fiscalization.

  • itemPrice cannot be less than 0.
  • itemPrice may be either string or integer.

All versions.

itemAttributes

See description.

Only for stores with enabled fiscalization settings

Tag that serves to pass a set of attributes of the line item. Attributes must be specified as follows. 

<attributes  name="attribute_name_1">attribute_value_1</attributes>
<attributes  name="attribute_name_2">attribute_value_2</attributes>

See description below.

1.05 and later versions.

==== itemAttributes ==== itemAttributes contains the attributes array in which the attributes of a line item must be specified (see example and table below). <sxh JavaScript> «itemAttributes»:{«attributes»:[{«name»:«paymentMethod»,»value«:«1»},{«name»:«paymentObject»,»value«:«1»}]} </sxh>

Name Type Mandatory Description FFD version

paymentMethod

N..2

Yes

Payment type. Possible values:

  • 1 – full pre-payment before the delivery date of the payment subject;
  • 2 – partial pre-payment before the delivery date of the payment subject;
  • 3 – advance payment;
  • 4 – full payment on the delivery date of the payment subject;
  • 5 – partial payment for the payment subject on the delivery date followed by payment on credit;
  • 6 – delivery of the payment subject on the delivery date without payment followed by payment on credit;
  • 7 – payment for the payment subject after its delivery using payment on credit.

Values are passed in the following priority (indicated in descending order of priority):

  1. Shopping cart from API request.
  2. Fiscalization settings in your personal account.
  3. Default values.

For paymentMethod, the default value is 1 (full prepayment before the transfer of the payment item).

1.05 and later versions.

paymentObject

N..2

Yes

Type of item being paid for. Possible values:

  • 1 – product;
  • 2 – excisable product;
  • 3 – work;
  • 4 – service;
  • 5 – gambling bet;
  • 6 – gambling winnings;
  • 7 – lottery ticket;
  • 8 – lottery winnings;
  • 9 – intellectual property;
  • 10 – payment;
  • 11 – agent's fee;
  • 12 – several subjects;
  • 13 – other payment subject.
  • * 14 – property rights;
  • 15 – non-operating income;
  • 16 – insurance premiums: on the amount of expenses that reduce the amount of tax (advance payments) in accordance with paragraph 3.1 of Article 346.21 of the Tax Code of the Russian Federation;
  • 17 – sales tax;
  • 18 – resort tax.

Values are passed in the following priority (indicated in descending order of priority):

  1. Shopping cart from API request.
  2. Fiscalization settings in your personal account.
  3. Default values.

The default value for paymentObject is 1 (item).

1.05 and later versions.

nomenclature

ANS

yes (if markQuantity is passed)

Trade item code in text representation. Maximum length – 32 bytes.

1.05 and later versions.

markQuantity

(Go to description.)

No

Fractional quantity of the labeled item.

1.2 and later versions.

agent_info.type

N..2

Mandatory if agent_info object is passed.

Agent type. The following values are available:

  • 1 – banking payment agent;
  • 2 – banking payment subagent;
  • 3 – payment agent;
  • 4 – payment subagent;
  • 5 – attorney;
  • 6 – commission agent;
  • 7 – other agent.

1.05 and later versions.

agent_info.paying.operation

ANS..24

No

Name of the transaction of the paying agent.

1.05 and later versions.

agent_info.paying.phones

array ANS..19

No

Phone numbers array of the payments agent in +N format.

1.05 and later versions.

agent_info.paymentsOperator.phones

Array ANS..19

No

Phone numbers array of the payments operator in +N format.

1.05 and later versions.

agent_info.MTOperator.phones

array ANS..19

No

An array of Money Transfer operator phone numbers in +N format.

1.05 and later versions.

agent_info.MTOperator.name

ANS..64

No

Money Transfer operator name.

1.05 and later versions.

agent_info.MTOperator.address

ANS..256

No

Money Transfer operator address.

1.05 and later versions.

agent_info.MTOperator.inn

N10..12

No

Money Transfer operator TIN.

1.05 and later versions.

supplier_info.phones

Array ANS..19

No

An array of supplier phone numbers in +N format.

1.05 and later versions.

supplier_info.name

ANS..256

No

Supplier name.

1.05 and later versions.

supplier_info.inn

N10..12

No

Supplier TIN.

1.05 and later versions.

==== quantity ==== quantity contains the following elements.

Name Type Mandatory Description FFD version

value

N..18

Yes

Quantity of line items in given positionId. Use a decimal point as a separator in fractions.

All versions.

measure

ANS..20

Yes

The unit of measurement for the quantity of line item instances.

All versions.

If the FFD is version 1.2 or later, then the following parameters are passed here:

Name Type Mandatory Description FFD version

value

N1

Yes

Quantity of line items in given positionId. For FFD version 1.2+, the value is always 1.

1.2 and later versions.

measure

N..3

Yes

Unit of measurement for the quantity of the payment subject. In case of FFD version 1.2+, if the 'nomenclature' and 'markQuantity' parameters are passed, the value is always 0. In other cases, it can have some value.

1.2 and later versions.

Possible values of measure

Value Description
0 Used for payment subjects that can be sold individually or in units (as well as in the event that the payment subject is a product subject to mandatory labeling with an identification tool (which can be known from mark_code being passed))
10 Gram
11 Kilogram
12 Ton
20 Centimeter
21 Decimeter
22 Meter
30 Square centimeter
31 Square decimeter
32 Square meter
40 Milliliter
41 Liter
42 Cubic meter
50 Kilowatt hour
51 Gigacalorie
70 Day (24h)
71 Hour
72 Minute
73 Second
80 Kilobyte
81 Megabyte
82 Gigabyte
83 Terabyte
255 Applicable when using other units of measurement

==== markQuantity ====

Parameters of markQuantity tag:

A parameter included in a tag and indicated as mandatory is only mandatory within that tag. If the tag itself is not mandatory and is not passed, its included parameters should not be passed.

Name Type Mandatory Description

numerator

N..12

yes

The numerator of the fractional part of the payment subject.

denominator

N..12

yes

The denominator of the fractional part of the payment subject.

==== itemDetails ==== 'itemDetails contains the following elements.

A parameter included in a block and indicated as mandatory is only mandatory within that block. If the section is optional and missing, then the parameters included in it should not be passed.

Name Type Mandatory Description FFD version

itemDetailsParams

ANS..255

Yes

Parameter describing additional information regarding a line item. The description of the attributes is given below.

(Go to description.)

All versions.

itemDetailsParams

'itemDetailsParams contains the following elements.

Name Type Mandatory Description FFD version

value

ANS..255

Conditional. Mandatory if itemDetailsParams parameter is present.

Additional information on a line item.

All versions.

Name

name

Type

AN..255

Type2

ANS..255

Description

REST

Name of the parameter describing the details of a line item

WS

Name of the parameter describing the details of a line item

ANS..255

Conditional. Mandatory if itemDetailsParams parameter is present.

Name of the parameter describing the details of a line item

All versions.

==== tax ==== tax contains the following elements.

Name Type Mandatory Description FFD version

taxType

N..2

No

VAT rate. The following values are available:

  • 0 – without VAT;
  • 1 – VAT at rate of 0%;
  • 2 – receipt VAT at rate of 10%;
  • 4 – receipt VAT at calculated rate of 10/110;
  • 6 – receipt VAT at rate of 20%;
  • 7 – receipt VAT at calculated rate of 20/120.

If the cart and fiscalization data are not included in the request, then the default values specified in the personal account are passed to the Fiscal Data Operator (see User Manual for personal account).

All versions.

taxSum

N..18

No

Amount of the tax calculated by the merchant. The amount is specified in minimum currency units

All versions.

==== additionalOfdParams ==== additionalOfdParams contains the following elements.

Name Type Mandatory Description FFD version

agent_info.type

N..2

Mandatory if agent_info object is passed.

Agent type. The following values are available:

  • 1 – banking payment agent;
  • 2 – banking payment subagent;
  • 3 – payment agent;
  • 4 – payment subagent;
  • 5 – attorney;
  • 6 – commission agent;
  • 7 – other agent.

1.05 and later versions.

agent_info.paying.operation

ANS..24

No

Name of the transaction of the paying agent.

1.05 and later versions.

agent_info.paying.phones

array ANS..19

No

Phone numbers array of the payments agent in +N format.

1.05 and later versions.

agent_info.paymentsOperator.phones

Array ANS..19

No

Phone numbers array of the payments operator in +N format.

1.05 and later versions.

agent_info.MTOperator.address

ANS..256

No

Money Transfer operator address.

1.05 and later versions.

agent_info.MTOperator.inn

N10..12

No

Money Transfer operator TIN.

1.05 and later versions.

agent_info.MTOperator.name

ANS..64

No

Money Transfer operator name.

1.05 and later versions.

agent_info.MTOperator.phones

array ANS..19

No

An array of Money Transfer operator phone numbers in +N format.

1.05 and later versions.

supplier_info.phones

Array ANS..19

No

An array of supplier phone numbers in +N format.

1.05 and later versions.

cashier

A..256

No

Cashier full name

1.05 and later versions.

additional_check_props

ANS..16

No

Additional property of the receipt.

1.05 and later versions.

additional_user_props.name

ANS..24

No

Name of the additional property of the user.

1.05 and later versions.

additional_user_props.value

ANS..24

No

Value of the additional property of the user.

1.05 and later versions.

cashier_inn

N..12

No

Cashier's INN

1.2 and later versions.

client.address

ANS..256

No

Customer address.

1.2 and later versions.

client.birth_date

NS10

No

Customer birth date as dd.mm.yyyy

1.2 and later versions.

client.citizenship

N3

No

Country numeric code of the county of Customer's citizenship. The country code is specified according to All-Russian World Countries Classifier (OKSM)

1.2 and later versions.

client.document_code

N2

No

Identification document type numeric code (for example, 21 stands for Russian Passport).

1.2 and later versions.

client.passport_number

NS11

No

Series and number of the payer's passport: 1111 222222

1.2 and later versions.

client.email

ANS..64

No

Customer's email address. Exactly one of the two fields must be passed: email or phone.

1.2 and later versions.

client.phone

NS..19

No

Customer's phone number. Must be passed with the country code without spaces and additional characters (except for + character). For example, the number «+371 2 1234567» should be passed as «+37121234567»). Exactly one of the two fields must be passed: email or phone.

1.2 and later versions.

client.inn

N12

No

INN of the buyer.

1.2 and later versions.

client.name

ANS..256

No

Customer name.

1.2 and later versions.

operatingCheckProps.name

ANS

No

Operation ID The value is «0» until the value of Russia's Federal Tax Service attribute is determined.

1.2 and later versions.

operatingCheckProps.name

ANS

No

Operation ID The value is «0» until the value of Russia's Federal Tax Service attribute is determined.

1.2 and later versions.

operatingCheckProps.timestamp

NS19

No

Date and time of the operation in dd.mm.yyyy HH:MM:SS format

1.2 and later versions.

operatingCheckProps.value

ANS..64

No

Operation data.

1.2 and later versions.

sectoralCheckProps.date

NS10

No

Date of the legislative act of the federal body of executive power that sets forth the requirements for assigning the value of «sectoral attribute». Format: dd.mm.yyyy.

1.2 and later versions.

sectoralCheckProps.federalId

ANS

No

Identifier of federal body of executive power. Must be one of the values from directory of federal bodies of executive power

1.2 and later versions.

sectoralCheckProps.number

N..32

No

Number of the legislative act of the federal body of executive power that sets forth the requirements for assigning the value of «sectoral attribute».

1.2 and later versions.

sectoralCheckProps.value

ANS..256

No

A set of values defined by the legislative act of the federal body of executive power.

1.2 and later versions.

===== Response parameters ===== The response parameters are given in table below.

Name Type Mandatory Description FFD version

success

A..5

Yes

Designates a successful request. The following values are available:

  • true – request is processed successfully;
  • false – request failed.

All versions.

errorCode

ANS..3

No

Error code.

All versions.

errorMessage

AN..512

No

Error description in the language passed in the language parameter in the request.

All versions.

===== Error codes =====

Error code Error text
0

The request has been processed without system errors.

1

An order with this number has already been processed.

1

Wrong order number.

3

Unknown currency.

4

Order number is empty

4

Merchant name cannot be empty.

4

The amount is missing.

4

Empty return URL

4

Password cannot be empty.

5

Access denied.

5

The user is inactive.

7

System error.

8

[depositItems.totalAmount] the sum of items in the cart does not match the total.

8

Additional parameter amount_bonus is not allowed if the request contains a cart.

8

[orderBundle.cartItems.item.quantity.value] Too high or too low value.

===== Examples ==== ==== Example of a request with a shopping cart ==== <sxh xml> <soapenv:Envelope xmlns:soapenv=«http://schemas.xmlsoap.org/soap/envelope/» xmlns:mer=«http://engine.paymentgate.ru/webservices/merchant»> <soapenv:Header> <soapenv:Body> <mer:closeOfdReceipt> <request mdOrder=«09fddf4a-fd30-76ca-ad2e-36f50128092a» amount=«23500»/> <orderBundle> <customerDetails> <phone>+79123456789</phone> <inn>516974792202</inn> <passport>4507 443564</passport> </customerDetails> <!– Contents of the cart –> <cartItems> <!– Zero or more repetitions: –> <items positionId=«1»> <name>«SMALL»</name> <quantity measure=«0»>1</quantity> <itemCode>270_235.00</itemCode> <itemPrice>23500</itemPrice> <tax> <taxType>0</taxType> <taxSum>0</taxSum> </tax> <itemAttributes> <attributes name=«nomenclature»>010463003407001221CMK45BrhN0WLf</attributes> <attributes name=«paymentMethod»>1</attributes> <attributes name=«paymentObject»>30</attributes> <attributes name=«agent_info.type»>7</attributes> <attributes name=«agent_info.paying.operation»>testoperation</attributes> <attributes name=«agent_info.paying.phones»>+79123456789</attributes> <attributes name=«agent_info.paymentsOperator.phones»>+79123456789</attributes> <attributes name=«agent_info.MTOperator.phones»>+79123456789</attributes> <attributes name=«agent_info.MTOperator.name»>MT operator</attributes> <attributes name=«agent_info.MTOperator.address»>Moscow</attributes> <attributes name=«agent_info.MTOperator.inn»>8634330204</attributes> <attributes name=«supplier_info.phones»>+79123456789</attributes> <attributes name=«supplier_info.name»>Supplier</attributes> <attributes name=«supplier_info.inn»>287381373424</attributes> <attributes name=«excise»>10.0</attributes> <attributes name=«country_code»>810</attributes> <attributes name=«declaration_number»>12332234533</attributes> <attributes name=«userData»>user data</attributes> <attributes name=«markQuantity.numerator»>1</attributes> <attributes name=«markQuantity.denominator»>2</attributes> <attributes name=«sectoralItemProps[0].federalId»>001</attributes> <attributes name=«sectoralItemProps[0].date»>10.10.2021</attributes> <attributes name=«sectoralItemProps[0].number»>123/4567</attributes> <attributes name=«sectoralItemProps[0].value»>value1</attributes> <attributes name=«sectoralItemProps[1].federalId»>003</attributes> <attributes name=«sectoralItemProps[1].date»>10.10.2021</attributes> <attributes name=«sectoralItemProps[1].number»>321/4567</attributes> <attributes name=«sectoralItemProps[1].value»>value2</attributes> </itemAttributes> </items> </cartItems> </orderBundle> </mer:closeOfdReceipt> </soapenv:Body> </soapenv:Envelope> </sxh> ==== Example of a request without a shopping cart ==== <sxh xml> <soapenv:Envelope xmlns:soapenv=«http://schemas.xmlsoap.org/soap/envelope/» xmlns:mer=«http://engine.paymentgate.ru/webservices/merchant»> <soapenv:Header/> <soapenv:Body> <mer:closeOfdReceipt> <order merchantOrderNumber=«78ds901234567890» description=» « amount=«15000» currency=» « language=» « pageView=«DESKTOP» sessionTimeoutSecs=» « bindingId=» « expirationDate=«2014-09-08T14:14:14»> <params name=«param1» value=«valueParam1»/> <params name=«param2» value=«valueParam2»/> <orderId>666</orderId> </order> </mer:closeOfdReceipt> </soapenv:Body> </soapenv:Envelope> </sxh> ==== Пример ответа ==== <sxh xml> <soap:Envelope xmlns:soap=«http://schemas.xmlsoap.org/soap/envelope/»> <soap:Body> <ns1:closeOfdReceiptResponse xmlns:ns1=«http://engine.paymentgate.ru/webservices/merchant»> <return> <success>true</success> </return> </ns1:closeOfdReceiptResponse> </soap:Body> </soap:Envelope> </sxh>