- [x] Provide data model and configuration toggle
- [x] Allow to delete individual test orders
- [x] Add tests
- [x] Add a prominent warning message to the backend if test mode orders exist (even though test mode is off), as this leads to wrong statistics
- [x] Decide if and how to generate invoices for test orders as invoice numbers cannot be repeated or should not have gaps.
- [x] Decide if and how we expose test orders through the API, since our difference pull mechanism relies on the fact that orders cannot be deleted.
- [x] Decide if and how we want to couple test modes of payment providers?
- [ ] pretix.eu: Ignore test orders for billing
- [ ] Adjust payment providers: Mollie, bitpay, cash, fakepayment, sepadebit
As discussed, this is a WIP for integrating Stripe's Payment Request Buttons (with also includes the ApplePay-Button on iOS-devices).
Todos:
- [x] Payment Request Button is still displayed, even when a card has already been tokenized (when going back in the order-flow)
- [x] The domains used need to be verified using the Stripe API to enable ApplePay: https://stripe.com/docs/stripe-js/elements/payment-request-button#verifying-your-domain-with-apple-pay
- [x] Migration: Get the account-country for existing Stripe Connect users
- [x] Migration: Verify the domains using the above mentioned API for existing users
- [x] Converting the chargeable amount is not right for non-decimal currencies like JPY
Other considerations:
- On iOS-devices using Safari (probably also on MacBooks, etc. - not tested), the [regular payment request button](https://user-images.githubusercontent.com/157270/38515749-f53f8392-3be9-11e8-8917-61ef78dd354a.png) is automatically replaced with a [buy with Apple Pay button](https://docs-assets.developer.apple.com/published/094d0eb90e/988c36a8-a43c-4ff9-85ef-beda16c4b7c9.png).
- On all other platforms, the generic payment request button is displayed. Even if the device supports a specific payment provider like Google Pay, Microsoft Wallet, Samsung Pay, etc., the generic button will first offer the cards saved within the webbrowser in addition to the other payment methods. Only upon selecting the specific payment provider like GPay, the corresponding payment flow is started.
- Right now, the rendering of the payment button is completely in the hands of Stripe. Once pretix takes on the task of doing this, we should try to detect if the browser supports well known payment methods like GPay in addition to the browser-saved cards. If that's the case, we should add the corresponding marks onto the "Pay Now"-Button (like [this](https://developers.google.com/pay/api/images/brand-guidelines/google-pay-mark.png), [this](https://assets.pcmag.com/media/images/490984-samsung-pay.png?width=1600&height=900), or [this](https://www.firstffcu.com/images/MS-Wallet_stacked_rgb_grey.png)), so the customer can identify the purpose of the button easier.
- [x] Also, all of this is still based against the pretix 1.x codebase ;-)
* [WIP] Fix#599 -- Add API to create orders
* Add more validation logic
* Add docs and some validation
* Fix test on MySQl
* Validation is fun, let's do more of it!
* Fix live_issues
* Add data shredders for PII
* First working shredder
* Add more shredders
* Add new shredders and download confirmation
* tmp
* PayPal, Stripe, banktransfer
* Add icon to logs
* Untested payment log shredders
* Add waiting list shredder
* First tests
* Add tests for shredders
* Improve templats, link to shredder
* Test payment info shredders
* More tests
* Documentation
* Fix enabled flag in payment provider overview
* Fix minor issues
* Refs #99 -- Fix stripe support for zero-decimal currencies
* Add new money formatting method
* Force decimal places in many places
* Locale-aware currency rendering
* Fix currencies in more places
* More currency fixes
* [WIP] Implement automatic spell-check for docs
fixes#663
The only thing unclear to me so far is how the output of `make spelling`
should be checked - is there a possibility to check for a file (i.e.
`_build/spelling/output.txt`) to be empty, and report a failed build
otherwise?
* fix typo in requirements.txt
* add enchant library
* travis should report errors, order spelling wordlist
* change travis.yml to easier troubleshoot build issues
* fixed more typos, added more words
* add more words, fix more typos
* added more words
* added more words
* revert changes to .travis.yml
* Data model
* little crud
* SubEventItemForm etc
* Drop SubEventItem.active, quota editor
* Fix failing tests
* First frontend stuff
* Addons form stuff
* Quota calculation
* net price display on EventIndex
* Add tests, solve some bugs
* Correct quota selection in more places, consolidate pricing logic
* Fix failing quota tests
* Fix TypeError
* Add tests for checkout
* Fixed a bug in QuotaForm
* Prevent immutable cart if a quota was removed from an item
* Add tests for pricing
* Handle waiting list
* Filter in check-in list
* Fixed import lost in rebase
* Fix waiting list widget
* Voucher management
* Voucher redemption
* Fix broken tests
* Add subevents to OrderChangeManager
* Create a subevent during event creation
* Fix bulk voucher creation
* Introduce subevent.active
* Copy from for subevents
* Show active in list
* ICal download for subevents
* Check start and end of presale
* Failing tests / show cart logic
* Test
* Rebase migrations
* REST API integration of sub-events
* Integrate quota calculation into the traditional quota form
* Make subevent argument to add_position optional
* Log-display foo
* pretixdroid and subevents
* Filter by subevent
* Add more tests
* Some mor tests
* Rebase fixes
* More tests
* Relative dates
* Restrict selection in relative datetime widgets
* Filter subevent list
* Re-label has_subevents
* Rebase fixes, subevents in calendar view
* Performance and caching issues
* Refactor calendar templates
* Permission tests
* Calendar fixes and month selection
* subevent selection
* Rename subevents to dates
* Add tests for calendar views
