anchor.diff:  * Upon success/failure, the user is redirected to a landing page
   
   
  -image::payments_gateway.png[Payment Gateway, align="center"]
  -
  +image::https://drive.google.com/uc?export=download&id=0Bw8rymjWckBHV25qNDljU3h4Umc&w=960&amp;h=480[Payment Gateway, align="center"]
   
   The flow below shows a 3D Secure variation of the previous flow. We are showing an authorization call, that is split in two phases:
   
  
positive.code: 
  
  
  image::payments_gateway_3ds.png[Payment Gateway 3D Secure variation, align="center"]
  
negative.code: 
  
  
  image::https://drive.google.com/uc?export=download&id=0Bw8rymjWckBHWXhkbmcxUVJnWlU&w=960&amp;h=480[Hosted Payment Page, align="center"]
  
  
  The flow below shows a 3D Secure variation of the previous flow. The main difference is that prior redirecting the browser to the landing page, it is first redirected to the access control server where the user can enter custom information.
  
  image::https://drive.google.com/uc?export=download&id=0Bw8rymjWckBHbW1IQlNFeVBmUXM&w=960&amp;h=480[Hosted Payment Page 3D Secure variation, align="center"]
  
  === Gateway Integration Flows
  
  