Confirmed users
324
edits
WebAPI/WebPaymentProvider: Difference between revisions
m
→Notifications
m (→Invocation) |
m (→Notifications) |
||
| Line 55: | Line 55: | ||
* When the payment processing is finished, the payment provider must send a POST to either a postback URL or chargeback URL of the app. The app developer must register these URLs with the payment provider before making calls to <code>navigator.mozPay()</code> or it can specify the callback URLs in the JWT that is passed into <code>navigator.mozPay()</code>. | * When the payment processing is finished, the payment provider must send a POST to either a postback URL or chargeback URL of the app. The app developer must register these URLs with the payment provider before making calls to <code>navigator.mozPay()</code> or it can specify the callback URLs in the JWT that is passed into <code>navigator.mozPay()</code>. | ||
* The payment provider signs a JWT with the same shared secret as with invocation and POSTs this to either the postback or chargeback URL. The POST | * The payment provider signs a JWT with the same shared secret as with invocation and POSTs this to either the postback or chargeback URL. The POST must only include the JWT in its payload. | ||
* The JWT must include the original request as well as an additional response object that specifies the payment provider’s transaction ID. | * The JWT must include the original request as well as an additional response object that specifies the payment provider’s transaction ID. | ||
* When a payment is successful, the notification is sent to the postback URL. | * When a payment is successful, the notification is sent to the postback URL. | ||