Routes

[drewroberts]

I'm stuck in a decision about the routes in this package. @pdbreen Could you help me?

I prefer using the following:

• /cart/create (for email address input)
• /cart (to see the cart details and choose payment method - only credit card with stripe in our payments pacakge now)
• /checkout (customer details and payment processing)
• /checkout/confirmation (confirmation page)

The problem I'm running into is if the application has different payment accounts (currently Stripe) for each location, then I need to either make these a location-based route or prevent cart items from different locations from being added and still use these same routes. The 3rd option is to figure out a way to divide the total into different payments for each location, but I don't like that solution as much. What do you think?

[pdbreen]

@drewroberts cart currently requires all items in the cart to be from the same location, so your preferred routes are fine (actually happen to be adding them right now).

[drewroberts]

Perfect! Thank you