From 074785cea106179cb3305637055ab0a009ca74f2 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 14:42:52 -0500 Subject: initial commit --- files/ru/web/api/payment_request_api/index.html | 126 ++++++++++++++++++++++++ 1 file changed, 126 insertions(+) create mode 100644 files/ru/web/api/payment_request_api/index.html (limited to 'files/ru/web/api/payment_request_api') diff --git a/files/ru/web/api/payment_request_api/index.html b/files/ru/web/api/payment_request_api/index.html new file mode 100644 index 0000000000..c59135cfe2 --- /dev/null +++ b/files/ru/web/api/payment_request_api/index.html @@ -0,0 +1,126 @@ +--- +title: Payment Request API +slug: Web/API/Payment_Request_API +translation_of: Web/API/Payment_Request_API +--- +
{{DefaultAPISidebar("Payment Request API")}}{{securecontext_header}}
+ +

Payment Request API предоставляет постоянный UX для продавцов и покупателей. Это не новый способ оплаты, а возможность пользователя выбрать предпочтительный способ оплаты и предоставить продавцу эту информацию.

+ +

Основы и использование Payment Request

+ +

Many problems related to online shopping-cart abandonment can be traced to checkout forms, which can be difficult and time consuming to fill out and often require multiple steps to complete. The Payment Request API is meant to reduce the number of steps needed to complete a payment online, potentially doing away with checkout forms. It aims to make the checkout process easier, by remembering a user's details, which are then passed along to a merchant hopefully without requiring a HTML form.

+ +

Advantages of using the Payment Request API with "basic-card" (card-based payments):

+ + + +

To request a payment, a web page creates a {{domxref("PaymentRequest")}} object in response to a user action that initiates a payment, such as clicking a "Purchase" button. The PaymentRequest allows the web page to exchange information with the user agent while the user provides input to complete the transaction.

+ +

You can find a complete guide in Using the Payment Request API.

+ +
+

Note: The API is available inside cross-origin {{htmlelement("iframe")}} elements only if they have had the {{htmlattrxref("allowpaymentrequest","iframe")}} attribute set on them.

+
+ +

Interfaces

+ +
+
{{domxref('PaymentAddress')}}
+
An object that contains address information; used for billing and shipping addresses, for example.
+
{{domxref('PaymentRequest')}}
+
An object that provides the API for creating and managing the {{Glossary("user agent", "user agent's")}} payment interface.
+
{{domxref('PaymentRequestEvent')}}
+
An event delivered to a payment handler when a {{domxref("PaymentRequest")}} is made.
+
{{domxref('PaymentRequestUpdateEvent')}}
+
Enables the web page to update the details of the payment request in response to a user action.
+
{{domxref('PaymentMethodChangeEvent')}}
+
Represents the user changing payment instrument (e.g., switching from a credit card to debit card).
+
{{domxref('PaymentResponse')}}
+
An object returned after the user selects a payment method and approves a payment request.
+
{{domxref('MerchantValidationEvent')}}
+
Represents the browser requiring the merchant (website) to validate themselves as allowed to use a particular payment handler (e.g., registered as allowed to use Apple Pay).
+
+ +
+
+ +

Dictionaries

+ +
+
{{domxref("AddressErrors")}}
+
A dictionary containing strings providing descriptive explanations of any errors in any {{domxref("PaymentAddress")}} entries which have errors.
+
{{domxref("PayerErrors")}}
+
A dictionary containing strings providing descriptive explanations of any errors in related to {{domxref("PaymentResponse")}}'s email, phone, and name attributes.
+
{{domxref("PaymentDetailsUpdate")}}
+
An object describing changes that need to be made to the payment details in the event that the server needs to update information following the instantiation of the payment interface but before the user begins to interact with it.
+
+ + + +
+
{{domxref("BasicCardChangeDetails")}}
+
An object providing redacted address information that is provided as the {{domxref("PaymentMethodChangeEvent.methodDetails", "methodDetails")}} on the {{event("paymentmethodchange")}} event sent to the {{domxref("PaymentRequest")}} when the user changes payment information.
+
{{domxref("BasicCardErrors")}}
+
An object providing any error messages associated with the fields in the {{domxref("BasicCardResponse")}} object that are not valid. This is used as the value of the {{domxref("PaymentValidationErrors.paymentMethod", "paymentMethod")}} property on the {{domxref("PaymentValidationErrors")}} object sent to the {{domxref("PaymentRequest")}} when an error occurs.
+
{{domxref('BasicCardRequest')}}
+
Defines an object structure for containing payment request details such as card type.
+
{{domxref('BasicCardResponse')}}
+
Defines an object structure for payment response details such as the number/expiry date of the card used to make the payment, and the billing address.
+
+ +

Specifications

+ + + + + + + + + + + + + + + + + + + + + + + + +
SpecificationStatusComment
{{SpecName('Payment')}}{{Spec2('Payment')}}Initial definition.
{{SpecName('Basic Card Payment')}}{{Spec2('Basic Card Payment')}}Defines {{domxref("BasicCardRequest")}} and {{domxref("BasicCardResponse")}}, among other things needed for handling credit card payment
{{SpecName('Payment Method Identifiers')}}{{Spec2('Payment Method Identifiers')}}Defines payment method identifiers and how they are validated, and, where applicable, minted and formally registered with the W3C.
+ +

Browser compatibility

+ +
+

PaymentRequest interface

+ +
+ + +

{{Compat("api.PaymentRequest", 0)}}

+
+
+ +

See also

+ + -- cgit v1.2.3-54-g00ecf