Confirmed users
324
edits
WebAPI/WebPayment: Difference between revisions
→Notifications: HTTPS is no longer required in Mozilla's payment provider
(Removing the warning that localizations aren't used yet as they will be live on the 18th) |
(→Notifications: HTTPS is no longer required in Mozilla's payment provider) |
||
| Line 133: | Line 133: | ||
=== Notifications === | === Notifications === | ||
The Application must only rely on server side notifications to determine the outcome of a purchase. The Payment Provider will POST a confirmation message (a JWT) to the '''postbackURL''' | The Application must only rely on server side notifications to determine the outcome of a purchase. The Payment Provider will POST a confirmation message (a JWT) to the '''postbackURL''' on success or the '''chargebackURL''' on error. The Application provides these URLs in the original JWT request. | ||
The POST request will have a content-type of <code>application/x-www-form-urlencoded</code> and the JWT will be in the '''notice''' form parameter. This JWT contains a copy of the original payment request plus a new response object that has a '''transactionID''' which identifies the Payment Provider's transaction. | The POST request will have a content-type of <code>application/x-www-form-urlencoded</code> and the JWT will be in the '''notice''' form parameter. This JWT contains a copy of the original payment request plus a new response object that has a '''transactionID''' which identifies the Payment Provider's transaction. | ||