View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007392 | Taler | merchant backend API (HTTP specification) | public | 2022-10-11 13:16 | 2023-02-21 16:39 |
| Reporter | sebasjm | Assigned To | Priscilla Huang | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.9.2 | Fixed in Version | 0.9.2 | ||
| Summary | 0007392: Support for "Buy Now" button | ||||
| Description | Features: * user should be able to register a new shop * user should provide email for PW reset * merchant backend should support a new endpoint that use this information to create a new order and redirect to it after success Similar as other payments provider does, like Paypal. Docs: https://developer.paypal.com/api/nvp-soap/paypal-payments-standard/integration-guide/formbasics/ https://developer.paypal.com/api/nvp-soap/paypal-payments-standard/integration-guide/html-example-buy-now/ Example: <form target="merchant_id" action="https://backend.url/instances/merchant_id/paynow" method="post"> <!-- Identify your business so that you can collect the payments. --> <input type="hidden" name="mechant" value="merchant_id"> <!-- Specify details about the item that buyers will purchase. --> <input type="hidden" name="summary" value="Cool Product"> <input type="hidden" name="amount" value="29.00"> <input type="hidden" name="currency_code" value="USD"> <!-- Display the payment button. --> <label> <input type="button" name="submit" src="images/checkout-btn.png" alt="Pay now" class="pp-btn"> Cool Product $29 </label> </form> | ||||
| Tags | No tags attached. | ||||
|
|
I think this is very similar to the 'static QR code' feature we discussed for NetzBon, and we can likely to BOTH in the same API. I think we should call this feature a "template", where the merchant backend has a public API to create orders based on certain templates. The template endpoint (/template/$TEMPLATE_ID) would accept some arguments from the client (like the price for the static QR code) and add others based on the template (like the summary, and maybe a fulfillment URL). The resulting order would be returned to the customer/wallet for payment as described above. |
|
|
I believe the simple template mechanism is working now, too. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-11 13:16 | sebasjm | New Issue | |
| 2022-10-11 13:16 | sebasjm | Status | new => assigned |
| 2022-10-11 13:16 | sebasjm | Assigned To | => sebasjm |
| 2022-10-20 11:47 | Christian Grothoff | Target Version | 0.9.1 => |
| 2022-11-11 10:25 | Christian Grothoff | Assigned To | sebasjm => Priscilla Huang |
| 2022-11-11 10:28 | Christian Grothoff | Note Added: 0019400 | |
| 2023-02-19 10:39 | Christian Grothoff | Status | assigned => resolved |
| 2023-02-19 10:39 | Christian Grothoff | Resolution | open => fixed |
| 2023-02-19 10:39 | Christian Grothoff | Fixed in Version | => 0.9.2 |
| 2023-02-19 10:39 | Christian Grothoff | Note Added: 0019876 | |
| 2023-02-19 10:39 | Christian Grothoff | Product Version | => git (master) |
| 2023-02-19 10:39 | Christian Grothoff | Target Version | => 0.9.2 |
| 2023-02-21 16:39 | Christian Grothoff | Status | resolved => closed |
