Confirmed users
483
edits
WebAPI/WebPayment: Difference between revisions
Jump to navigation
Jump to search
→In-app payment
No edit summary |
|||
| Line 125: | Line 125: | ||
* The user confirms the purchase or cancels it. | * The user confirms the purchase or cancels it. | ||
* If the user cancels, the flow returns to the <code>DOMRequest.onerror</code> callback. | * If the user cancels, the flow returns to the <code>DOMRequest.onerror</code> callback. | ||
* If the user confirms, the Payment Provider should send a POST confirmation message (a JWT) to the postback URL of the seller provided within the JWT request. The postback URL is optional, but strongly recommended. The Payment Processor (also via Mozilla Marketplace) could optionally store a default postback URL as part of his application sign-up process. If a different postback URL is provided within the JWT request, this one would override the default one stored as default in the Payment Provider. This confirmation message contains all the payment request fields plus a transaction identifier, and is signed with the seller's application secret. | * If the user confirms, the Payment Provider should send a POST confirmation message (a JWT) to the postback URL of the seller provided within the JWT request. The postback URL is optional, but strongly recommended. The Payment Processor (also via Mozilla Marketplace) could optionally store a default postback URL as part of his application sign-up process. If a different postback URL is provided within the JWT request, this one would override the default one stored as default in the Payment Provider. This confirmation message contains all the payment request fields plus a transaction identifier, and is signed with the seller's application secret. In the following example, the ''transactionID'' field is specific to the BlueVia payment provider. | ||
<code> | <code> | ||