pay_fu 1.0.0

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2012 YOURNAME
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,54 @@
+# pay_fu
+
+a rails payment engine that supports both alipay and paypal.
+
+## Setup
+
+1) add to Gemfile
+
+```ruby
+gem "pay_fu"
+```
+
+2) install gem
+
+```bash
+bundle install
+```
+
+3) generate config file, route and migration file
+
+```bash
+rails generate pay_fu:install
+```
+
+4) update config file config/pay_fu.yml
+
+5) run migration
+
+```bash
+rake db:migrate
+```
+
+6) in controller file, after user clicking checkout, redirect him to
+   paypal gateway page.
+
+```ruby
+include PayFu::PaypalHelper
+def action
+  ...
+  redirect_to_paypal_gateway(:item_name => "subject", :amount => 123)
+  return
+end
+```
+
+7) similar for alipay
+
+```ruby
+include PayFu::AlipayHelper
+def action
+  ...
+  redirect_to_alipay_gateway(:subject => "donatecn", :body => "donatecn", :amount => @donate.amount, :out_trade_no => "123", :notify_url => pay_fu.alipay_transactions_notify_url)
+  return
+end
+```

data/Rakefile

@@ -0,0 +1,40 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'PayFu'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../test/dummy/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+
+
+Bundler::GemHelper.install_tasks
+
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = false
+end
+
+
+task :default => :test

data/app/assets/javascripts/pay_fu/application.js

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/app/assets/stylesheets/pay_fu/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+*/

data/app/controllers/pay_fu/alipay_transactions_controller.rb

@@ -0,0 +1,28 @@
+module PayFu
+  class AlipayTransactionsController < ApplicationController
+    include ActiveMerchant::Billing::Integrations
+
+    def notify
+      notify = Alipay::Notification.new(request.new_post)
+      if notify.acknowledge
+        if transaction = PayFu::AlipayTransaction.find_by_transaction_id(notify.trade_no)
+          transaction.update_attributes(transaction_attributes(notify))
+        else
+          PayFu::AlipayTransaction.create(transaction_attributes(notify))
+        end
+      end
+      render :nothing => true
+    end
+
+    def transaction_attributes(notify)
+      @transaction_attributes ||= {
+        :transaction_id => notify.trade_no,
+        :transaction_type => notify.payment_type,
+        :payment_status => notify.trade_status,
+        :payment_date => notify.notify_time,
+        :gross => notify.total_fee,
+        :raw_post => notify.raw
+      }
+    end
+  end
+end

data/app/controllers/pay_fu/application_controller.rb

@@ -0,0 +1,4 @@
+module PayFu
+  class ApplicationController < ActionController::Base
+  end
+end

data/app/controllers/pay_fu/paypal_transactions_controller.rb

@@ -0,0 +1,28 @@
+module PayFu
+  class PaypalTransactionsController < ApplicationController
+    include ActiveMerchant::Billing::Integrations
+
+    def notify
+      notify = Paypal::Notification.new(request.raw_post)
+      if notify.acknowledge
+        if transaction = PayFu::PaypalTransaction.find_by_transaction_id(notify.transaction_id)
+          transaction.update_attributes(transaction_attributes(notify))
+        else
+          PayFu::PaypalTransaction.create(transaction_attributes(notify))
+        end
+      end
+      render :nothing => true
+    end
+
+    def transaction_attributes(notify)
+      @transaction_attributes ||= {
+        :transaction_id => notify.transaction_id,
+        :transaction_type => notify.type,
+        :payment_status => notify.status,
+        :payment_date => notify.received_at,
+        :gross => notify.gross_cents,
+        :raw_post => notify.raw
+      }
+    end
+  end
+end

data/app/helpers/pay_fu/alipay_helper.rb

@@ -0,0 +1,24 @@
+require 'digest/md5'
+
+module PayFu
+  module AlipayHelper
+    def redirect_to_alipay_gateway(options={})
+      query_string = {
+        :partner => ActiveMerchant::Billing::Integrations::Alipay::ACCOUNT,
+        :out_trade_no => options[:out_trade_no],
+        :total_fee => options[:amount],
+        :seller_email => ActiveMerchant::Billing::Integrations::Alipay::EMAIL,
+        :notify_url => options[:notify_url],
+        :body => options[:body],
+        :"_input_charset" => 'utf-8',
+        :service => ActiveMerchant::Billing::Integrations::Alipay::Helper::CREATE_DIRECT_PAY_BY_USER,
+        :payment_type => "1",
+        :subject => options[:subject]
+      }.sort.map { |key, value| "#{key}=#{CGI.unescape(value)}" }.join("&")
+      sign = Digest::MD5.hexdigest(query_string + ActiveMerchant::Billing::Integrations::Alipay::KEY)
+      query_string += "&sign=#{sign}&sign_type=MD5"
+
+      redirect_to "https://www.alipay.com/cooperate/gateway.do?" + query_string
+    end
+  end
+end

data/app/helpers/pay_fu/application_helper.rb

@@ -0,0 +1,4 @@
+module PayFu
+  module ApplicationHelper
+  end
+end

data/app/helpers/pay_fu/paypal_helper.rb

@@ -0,0 +1,8 @@
+module PayFu
+  module PaypalHelper
+    def redirect_to_paypal_gateway(options={})
+      host = ActiveMerchant::Billing::Base.mode == "test" ? "www.sandbox.paypal.com" : "www.paypal.com"
+      redirect_to URI.encode("https://#{host}/cgi-bin/webscr?cmd=_ext-enter&redirect_cmd=_xclick&charset=utf-8&business=#{PayFu::CONFIGS["paypal"]["email"]}&currenct_code=USD&item_name=#{options[:item_name]}&amount=#{options[:amount]}")
+    end
+  end
+end

data/app/models/pay_fu/alipay_transaction.rb

@@ -0,0 +1,4 @@
+module PayFu
+  class AlipayTransaction < Transaction
+  end
+end

data/app/models/pay_fu/paypal_transaction.rb

@@ -0,0 +1,4 @@
+module PayFu
+  class PaypalTransaction < Transaction
+  end
+end

data/app/models/pay_fu/transaction.rb

@@ -0,0 +1,5 @@
+module PayFu
+  class Transaction < ActiveRecord::Base
+    attr_accessible :transaction_id, :transaction_type, :payment_status, :payment_date, :gross, :raw_post, :type
+  end
+end

data/app/views/layouts/pay_fu/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>PayFu</title>
+  <%= stylesheet_link_tag    "pay_fu/application", :media => "all" %>
+  <%= javascript_include_tag "pay_fu/application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>

data/config/routes.rb

@@ -0,0 +1,4 @@
+PayFu::Engine.routes.draw do
+  match '/paypal_transactions/notify' => 'paypal_transactions#notify'
+  match '/alipay_transactions/notify' => 'alipay_transactions#notify'
+end

data/lib/generators/pay_fu/install_generator.rb

@@ -0,0 +1,19 @@
+require 'rails/generators'
+require File.expand_path('../utils', __FILE__)
+
+module PayFu
+  class InstallGenerator < Rails::Generators::Base
+    source_root File.expand_path("../templates", __FILE__)
+    include Rails::Generators::Migration
+    include Generators::Utils::InstanceMethods
+    extend Generators::Utils::ClassMethods
+
+    desc "PayFu installation generator"
+    def install
+      migration_template 'migration.rb', 'db/migrate/create_pay_fu_transactions.rb' rescue display $!.message
+      route("mount PayFu::Engine => '/pay_fu', :as => 'pay_fu'")
+      template "config.yml", "config/pay_fu.yml"
+      display "PayFu engine is installed."
+    end
+  end
+end

data/lib/generators/pay_fu/templates/config.yml

@@ -0,0 +1,23 @@
+development:
+  paypal:
+    mode: "test"
+    email: ""
+    login: ""
+    password: ""
+    signature: ""
+  alipay:
+    key: ""
+    account: ""
+    email: ""
+
+production:
+  paypal:
+    mode: "production"
+    email: ""
+    login: ""
+    password: ""
+    signature: ""
+  alipay:
+    key: ""
+    account: ""
+    email: ""

data/lib/generators/pay_fu/templates/migration.rb

@@ -0,0 +1,15 @@
+class CreatePayFuTransactions < ActiveRecord::Migration
+  def change
+    create_table :pay_fu_transactions do |t|
+      t.string :type
+      t.string :transaction_id
+      t.string :transaction_type
+      t.string :payment_status
+      t.datetime :payment_date
+      t.integer :gross
+      t.string :raw_post
+
+      t.timestamps
+    end
+  end
+end

data/lib/generators/pay_fu/utils.rb

@@ -0,0 +1,29 @@
+module PayFu
+  module Generators
+    module Utils
+      module InstanceMethods
+        def display(output, color = :green)
+          say("           -  #{output}", color)
+        end
+
+        def ask_for(wording, default_value = nil, override_if_present_value = nil)
+          override_if_present_value.present? ?
+            display("Using [#{override_if_present_value}] for question '#{wording}'") && override_if_present_value :
+            ask("           ?  #{wording} Press <enter> for [#{default_value}] >", :yellow).presence || default_value
+        end
+      end
+
+      module ClassMethods
+        def next_migration_number(dirname)
+          if ActiveRecord::Base.timestamped_migrations
+            migration_number = Time.now.utc.strftime("%Y%m%d%H%M%S").to_i
+            migration_number += 1
+            migration_number.to_s
+          else
+            "%.3d" % (current_migration_number(dirname) + 1)
+          end
+        end
+      end
+    end
+  end
+end

data/lib/pay_fu.rb

@@ -0,0 +1,4 @@
+require "pay_fu/engine"
+
+module PayFu
+end

data/lib/pay_fu/engine.rb

@@ -0,0 +1,27 @@
+module PayFu
+  class Engine < ::Rails::Engine
+    isolate_namespace PayFu
+
+    initializer "pay_fu_engine.load_configs" do |app|
+      config_file = Rails.root.join("config/pay_fu.yml")
+      if config_file.file?
+        require 'active_merchant'
+        require 'activemerchant_patch_for_china'
+
+        PayFu::CONFIGS = YAML.load_file(config_file)[Rails.env]
+        paypal_config = PayFu::CONFIGS["paypal"]
+
+        ActiveMerchant::Billing::Base.mode = paypal_config["mode"].to_sym
+        ActiveMerchant::Billing::PaypalGateway.new(
+          :login => paypal_config["login"],
+          :password => paypal_config["password"],
+          :signature => paypal_config["signature"]
+        )
+
+        ActiveMerchant::Billing::Integrations::Alipay::KEY = PayFu::CONFIGS["alipay"]["key"]
+        ActiveMerchant::Billing::Integrations::Alipay::ACCOUNT = PayFu::CONFIGS["alipay"]["account"]
+        ActiveMerchant::Billing::Integrations::Alipay::EMAIL = PayFu::CONFIGS["alipay"]["email"]
+      end
+    end
+  end
+end

data/lib/pay_fu/version.rb

@@ -0,0 +1,3 @@
+module PayFu
+  VERSION = "1.0.0"
+end

data/lib/tasks/pay_fu_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :pay_fu do
+#   # Task goes here
+# end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.