Confirmed users
1,158
edits
Marketplace/BokuPayments: Difference between revisions
→Payment
| Line 77: | Line 77: | ||
* Add in API to call Boku to start a payment, passing through app, customer id and price. | * Add in API to call Boku to start a payment, passing through app, customer id and price. | ||
** Call https://api2.boku.com/billing/request, fields: | |||
{| | |||
| merchant-id || is this one for all mozilla calls? | |||
|- | |||
| password || one for all mozilla calls? | |||
|- | |||
| service-id || is this the developer id? | |||
|- | |||
| currency || - | |||
|- | |||
| price-inc-salestax || - | |||
|- | |||
| consumer-id || hashed persona id/firefox accounts id | |||
|- | |||
| callback-url || is the front end or back end one? | |||
|} | |||
Note: I think server side calls are set in the merchant account setup. | |||
* Add in APIs to token check to ensure Boku responses are valid. | * Add in APIs to token check to ensure Boku responses are valid. | ||
** Call https://api2.boku.com/billing/request | |||
{| | |||
| merchant-id || is this one for all mozilla calls? | |||
|- | |||
| password || one for all mozilla calls? | |||
|- | |||
| trx-id || this is pay-uuid (to check this is populated correctly) | |||
|} | |||
* Add in the end point for Boku server to server responses and update solitude and zamboni transaction records appropriately. | * Add in the end point for Boku server to server responses and update solitude and zamboni transaction records appropriately. | ||
** Merchant callback URL, see page 40 of PDF | |||
In webpay: | In webpay: | ||