WebAPI/WebPayment: Difference between revisions

Jump to navigation Jump to search
Line 320: Line 320:
where <code>aResult</code> and <code>aErrorMsg</code> are simple strings.
where <code>aResult</code> and <code>aErrorMsg</code> are simple strings.


These functions should be called by the payment provider to finish the payment flow. Both functions would close the payment flow window and trigger the <code>onsuccess</code> or <code>onerror</code> events over the <code>DOMRequest</code> returned with the <code>navigator.mozPay</code> call. The <code>aResult</code> and <code>aErrorMsg</code> strings passed by the payment provider would be available for the application as <code>DOMRequest.result</code> and <code>DOMRequest.error</code> values.
These functions should be called by the payment provider to finish the payment flow. Both functions would close the payment flow window and trigger the [https://developer.mozilla.org/en-US/docs/DOM/DOMRequest.onsuccess onsuccess] or [https://developer.mozilla.org/en-US/docs/DOM/DOMRequest.onerror onerror] events over the [https://developer.mozilla.org/en-US/docs/DOM/DOMRequest DOMRequest] returned by the <code>navigator.mozPay</code> call. The <code>aResult</code> and <code>aErrorMsg</code> strings passed by the payment provider would be available for the application as [https://developer.mozilla.org/en-US/docs/DOM/DOMRequest.result DOMRequest.result] and [https://developer.mozilla.org/en-US/docs/DOM/DOMRequest.error DOMRequest.error] values respectively.


== Online payments from other networks ==
== Online payments from other networks ==
Confirmed users
483

edits

Navigation menu