Question about implementing an express checkout api about django-oscar-api

[specialunderwear]

Hi, maybe you can use some of the information we shared in #93

For the express checkout, I am wondering if you are settings this up for anonymous users or for loggedin users that have allready entered their addresses etc.

Either way I am not really seeing how you can gather all this information you need to send to your api with a single click on a button?

[mshamma]

Thanks for the info #93. I'm setting this up for anonymous users. I'll use the express checkout response to prepare the order and forward the request as a transaction to Cybersource.

However, I already see now that I have to correct this line

basket.add_product(product, quantity=quantity, options=options)

If the data is invalid, the basket remains open. When the data is corrected on the front-end, the total is thrown off and must be doubled. Should I simply flush the basket upon each request before calling add_product?

[Optional reading more background] We're using oscar for our university donations portal (give.berkeley.edu). The products are funds to which donors may give money. The quantity is always fixed as 1. We're working on an Ember front end that allows them to select the fund (e.g. via the products API) and the gift amount (e.g. total), name, address, phone, notes, etc and post it to the express checkout API.

We chose oscar because of its maturity and flexible pricing strategy. We're using Cybersource, so I'll borrow from django-payments which has a Cybersource provider. Unfortunately, django-oscar-cybersource requires postgres, so this is a non-starter for us.

[mshamma]

Thanks for the help. I realize I should probably ask this question on SO. http://stackoverflow.com/questions/43006599/can-i-use-existing-the-existing-oscar-oscar-api-object-model-to-implement-a-sing