Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 390
- Log:
Initial import of Canvass, a donations-based poll application.
- Author:
- rool
- Date:
- Mon Mar 21 14:58:04 +0000 2011
- Size:
- 6394 Bytes
1 | # Payment gateway configuration |
2 | # ============================= |
3 | # |
4 | # Choose a payment gateway expressed as an Active Merchant class name, such as |
5 | # "PayflowGateway" or "BeanstreamGateway". Then configure a login ID, password |
6 | # and signature. The contents depend on your gateway and not all of the values |
7 | # may be needed. Extended notes for PayPal are given later as PayPal's range of |
8 | # products, the associated Active Merchant gateways and the names of all of |
9 | # these things can be particularly complicated and confusing. |
10 | # |
11 | # If a value isn't required, just leave the key name (e.g. "signature:") intact |
12 | # with the colon after it included, but have nothing else on that line. |
13 | # |
14 | # |
15 | # Configuration summary |
16 | # --------------------- |
17 | # |
18 | # Key Value |
19 | # =========================================================================== |
20 | # gateway Name of class of required Active Merchant gateway, such as |
21 | # "BeanstreamGateway". See the Active Merchant documentation |
22 | # for more information. |
23 | # |
24 | # login Login string to use for gateway (nearly always needed). |
25 | # |
26 | # password Password string to use for gateway (nearly always needed). |
27 | # |
28 | # signature Signature string to use for gateway (often not used, so just |
29 | # give no value at all on the "signature:" line). |
30 | # |
31 | # |
32 | # PayPal and choosing the correct gateway |
33 | # --------------------------------------- |
34 | # |
35 | # PayPal in the UK have an XML-based API which is provided to accounts |
36 | # that have "Website Payments Pro" enabled. This API has the name |
37 | # "Payflow". In the USA the equivalent product is called "Payflow Pro". |
38 | # Confusingly, American PayPal accounts can also choose something |
39 | # called "Website Payments Pro" but that's nothing to do with the |
40 | # same-named UK product! It is based on a different kind of API and can |
41 | # be ignored as far as ActiveMerchant is concerned in this discussion - |
42 | # there does seem to be an Active Merchant gateway for this specific API |
43 | # too ("PaypalGateway"), but I've never used it, it might not actually |
44 | # be for what I'm assuming as a result and I don't discuss it further |
45 | # below. |
46 | # |
47 | # When using Payments Pro (UK) or Payflow Pro (USA), the Active Merchant |
48 | # gateways with "Payflow" in their names must be used. There is a |
49 | # generic ("PayflowGateway") and a UK specific ("PayflowUkGateway") |
50 | # gateway; the correct one must be used as API parameters vary |
51 | # according to the location of the account you are targetting. There are |
52 | # also "Express" variants of each of these gateways, which manage the |
53 | # 'express checkout' option that is supported in addition to the |
54 | # on-site credit card payment system. These are usually not |
55 | # instantiated directly, but accessed via the main instantiated gateway |
56 | # object via "gateway.express.<ActiveMerchant call>". In theory Artisan |
57 | # does support use of just the 'express' version of the gateway for |
58 | # express-only checkout, but then you'll be ignoring most of the useful |
59 | # Payflow Pro features and paying a monthly fee needlessly (see later). |
60 | # |
61 | # When instantiating one of the "Payflow" gateways, only a login ID and |
62 | # password are required. These are the credentials you enter when you |
63 | # visit "manager.paypal.com". That won't mean anything to you unless |
64 | # you've set up an account with Website Payments Pro approved and |
65 | # enabled for that account. |
66 | # |
67 | # Payments Pro / Payflow Pro is time consuming to set up, needs PayPal |
68 | # to allow the application, and can involve lots of forms and even a |
69 | # telephone interview. If for some reason your application is refused, |
70 | # you probably won't be told why and you have to wait 90 days before you |
71 | # can apply again. There's also a monthly fee to use the service. Quite |
72 | # a lot of hassle just to allow someone to type in their card details on |
73 | # your web pages, rather than on PayPal's web pages! |
74 | # |
75 | # Fortunately, a no-fee, no-application option for PayPal business |
76 | # accounts exists: Express Checkout. This is not to be confused with the |
77 | # Express Checkout portion of Pay[flow/ments] Pro interface discussed |
78 | # above despite them having the same PayPal 'product name', since a |
79 | # different Active Merchant gateway must be used. |
80 | # |
81 | # When using the Express Checkout API, the Active Merchant gateway |
82 | # classes with "Paypal" in their name - note "Paypal" and *NOT* |
83 | # "Payflow" - are used. |
84 | # |
85 | # To set up Express Checkout, you have to dig around in your PayPal |
86 | # business account's "Profile" link and find the stuff about enabling |
87 | # "Express Checkout" and configuring "API access". You must create |
88 | # (again, follow your nose) API credentials, using a signature rather |
89 | # than a certificate when given the option. This results in a |
90 | # complicated looking login name, a long password and even longer |
91 | # signature string. These three values are supplied for the :login, |
92 | # :password and :signature keys when you instantiate your "Paypal" |
93 | # class gateway. In practice, whether in the UK or US, you'd always use |
94 | # the "PaypalExpressGateway" here. |
95 | # |
96 | # Unlike the "Payflow" gateways, Active Merchant has no UK specific |
97 | # variant as none is strictly needed by the API. It's nice to create one |
98 | # though, both for consistency with the set of "Payflow" classes and to |
99 | # set up a default currency of British Pounds as otherwise, the default |
100 | # is US Dollars. That's what "config/initializers/10_paypal_express_uk" |
101 | # does; if you have a UK account, specify the "PaypalExpressUkGateway" |
102 | # rather than "PaypalExpressGateway". |
103 | # |
104 | # Express Checkout supports only a single currency per cart, so when |
105 | # Artisan detects that this gateway or its superclass is in use, on-site |
106 | # checkout systems will be hidden and users will not be allowed to add |
107 | # multiple currency items to their cart. They can try, but they'll be |
108 | # given a warning that the cart already contains items in another |
109 | # currency and told that they must check out using those first. |
110 | |
111 | --- |
112 | production: |
113 | |
114 | gateway: "PaypalExpressUkGateway" # See "config/initializers/10_paypal_express_uk.rb" |
115 | login: "set-login-here" |
116 | password: "set-password-here" |
117 | signature: "set-signature-here" |
118 | |
119 | development: |
120 | |
121 | gateway: "PayflowGateway" |
122 | login: "set-login-here" |
123 | password: "set-signature-here" |
124 | signature: |
125 | |
126 | # You shouldn't need to change the settings for the 'test' environment. |
127 | |
128 | test: |
129 | |
130 | gateway: "BogusGateway" |
131 | login: "donotcare" |
132 | password: "donotcare" |
133 | signature: "donotcare" |