anchor.diff:  The *payment* features let you connect with virtually any payment gateway and processor (Stripe, Braintree, PayPal, Adyen, CyberSource, etc.) to charge your customers (using credit or debit cards, ACH, wire transfers, Bitcoin, etc.) for their subscriptions or one-off payments (e.g. shopping cart-type websites like Amazon or Zappos).
   
   
  +== Overview
  +
   Check this video for a quick tour:
   
   https://www.youtube.com/watch?v=f2IHcz3OLYo[image:http://img.youtube.com/vi/f2IHcz3OLYo/0.jpg[align=center]]
  -
  -== Overview
   
   === Big Picture
   
  
positive.code: The flow diagram above highlights a couple of important aspects of the system:
  
  1. The creation of the subscription will generate a series of internal events that will lead to the generation of the _invoice_ and its associated _payment_. If needed such behavior can also be configured.
  2. Because of its plugin architecture, it is easy to extend the system by writing plugins. The diagrams above assume the plugins interact with 3rd party systems, but of course all the tax logic could for instnace be implemented in the plugin itself.
  3. Kill Bill offers well defined extension points for these plugins to be highly effective and modify the behavior of the system as needed.
  
  
  
negative.code: 
  So, in the diagram above, we can see that:
  
  * Customers interact with your website, which then issues REST API calls to Kill Bill. **You are responsible for designing and building that piece**.
  * Kill Bill, with its database, **manages all the state associated with the subscriptions, invoices, payments, etc.**
  * KAUI is the **Back-office UI for your teams**, and it includes role based access control to provide different priviledges for different teams/users:
    ** Your customer support team will use to access/modify consumer accounts data
    ** Your product team  will use to configure catalog information, billing rules, ..
    ** You finance/accounting team will access it for different types of reports
    ** Your engineering team will access it for running quick dev scenarios
  
  
  === Deployment
  
  Kill Bill is packaged as a WAR and is therefore executed within a web container (typically Tomcat). While you can deploy Kill Bill directly as a WAR inside a container, we also provide easier deployment options:
  
  