Confirmed users
28
edits
WebAPI/WebPayment: Difference between revisions
Jump to navigation
Jump to search
Removing the warning that localizations aren't used yet as they will be live on the 18th
(Update to show localization of payment products) |
(Removing the warning that localizations aren't used yet as they will be live on the 18th) |
||
| Line 110: | Line 110: | ||
** '''chargebackURL''' (mandatory): URL where the payment processor sends an HTTP POST message to whenever a refund associated with this transaction is done. | ** '''chargebackURL''' (mandatory): URL where the payment processor sends an HTTP POST message to whenever a refund associated with this transaction is done. | ||
** '''defaultLocale''' (mandatory if '''locales''' is defined, otherwise it is optional): Describes what language the '''name''' and '''description''' are in. | ** '''defaultLocale''' (mandatory if '''locales''' is defined, otherwise it is optional): Describes what language the '''name''' and '''description''' are in. | ||
** '''locales''' (optional): is a map of one or more locale-specific overrides of the data contained in the in-app product, which UIs use to provide localized views based on the accessing device's locale. For example, if you have Italian readers installing your app, you probably want to give them Italian UI text. Each locale entry is keyed on a language tag ([http://www.ietf.org/rfc/rfc4646.txt RFC 4646]) and contains the keys you want to replace. You can only override name and description. | ** '''locales''' (optional): is a map of one or more locale-specific overrides of the data contained in the in-app product, which UIs use to provide localized views based on the accessing device's locale. For example, if you have Italian readers installing your app, you probably want to give them Italian UI text. Each locale entry is keyed on a language tag ([http://www.ietf.org/rfc/rfc4646.txt RFC 4646]) and contains the keys you want to replace. You can only override name and description. | ||
* For a user to make a purchase, the Application must execute the Javascript method <code>navigator.mozPay()</code> with one or more signed payment requests (the JWTs). For example, the app might have a 'buy' button that triggers this method when clicked. Then <code>navigator.mozPay</code> method should take the signed payment JWT or an array of them. It will return a [https://developer.mozilla.org/en/DOM/DOMRequest DOMRequest] object that the developer can use to monitor the progress of the operation. | * For a user to make a purchase, the Application must execute the Javascript method <code>navigator.mozPay()</code> with one or more signed payment requests (the JWTs). For example, the app might have a 'buy' button that triggers this method when clicked. Then <code>navigator.mozPay</code> method should take the signed payment JWT or an array of them. It will return a [https://developer.mozilla.org/en/DOM/DOMRequest DOMRequest] object that the developer can use to monitor the progress of the operation. | ||